mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ed Vance <EdV@macrolink.com>
To: "'jeff millar'" <wa1hco@adelphia.net>
Cc: Shane Helms <shanehelms@eircom.net>, linux-kernel@vger.kernel.org
Subject: RE: is KERNEL developement finished, yet ???
Date: Wed, 4 Dec 2002 18:00:55 -0800	[thread overview]
Message-ID: <11E89240C407D311958800A0C9ACF7D1A33CD5@EXCHANGE> (raw)

On Wed, December 04, 2002 at 4:28 PM, jeff millar wrote:
> My opinion...
> 
> Kernels are getting mature in the sense the there's not that 
> many ways to do tasking and hardware interface.  It no 
> longer a game of invention but a game of polishing.  The 
> amount of total work available probably continues to go
> up because kernels are becoming as common as screws.
> 
> It's like the guy who invented interchangable hardware in the
> 1700's...really cool and creates plenty of work but it's no 
> longer bleeding edge to design the next screw thread in the 
> next material.
> 
> So, do you want to push the edge and discover new principles 
> and go where no one has gone before?  Or do you want to make 
> the existing implementations better than anyone else ever has 
> before?
> 
> [ ... VHDL ... FPGA ]

Oh, ye of little imagination. 

It's only polishing because the new work must merge into the 
framework imposed by the old work (un*x legacy environment). 

If you assume nothing about OS architecture, there are still 
huge vistas of unexplored solution space, where no one has gone
before. It's just really hard for engineers to let go of the 
stuff that works and start climbing from the bottom of the 
mountain. 

cheers,

---------------------------------------------------------------- 
Ed Vance              edv (at) macrolink (dot) com
Macrolink, Inc.       1500 N. Kellogg Dr  Anaheim, CA  92807
----------------------------------------------------------------

             reply	other threads:[~2002-12-05  1:53 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-05  2:00 Ed Vance [this message]
2002-12-05 12:24 ` Shane Helms
2002-12-05 12:54   ` Joseph D. Wagner
2002-12-05 13:15     ` Andreas Schwab
2002-12-05 18:07     ` Linus Torvalds
2002-12-05 19:52       ` Shane Helms
2002-12-05 20:03         ` Linus Torvalds
2002-12-05 20:09       ` is KERNEL developement finished, yet ??? (ACLs) Tupshin Harper
2002-12-06 10:38         ` Jakob Oestergaard
2002-12-15  5:29         ` Tracy R Reed
2002-12-07 20:34       ` is KERNEL developement finished, yet ??? Kai Henningsen
2002-12-05 18:09     ` Alan Cox
2002-12-05 17:47       ` yodaiken
2002-12-05 19:08       ` John Bradford
2002-12-06  6:15       ` Joseph D. Wagner
2002-12-06  6:30         ` John Alvord
2002-12-06  9:48         ` Alvaro Lopes
2002-12-07 20:43           ` Kai Henningsen
2002-12-07 20:39       ` Kai Henningsen
2002-12-09 14:08         ` Jesse Pollard
2002-12-10  0:26           ` H. Peter Anvin
2002-12-05 14:33   ` Mikael Pettersson
     [not found] <sdef301b.011@mail-01.med.umich.edu>
2002-12-05 16:36 ` Joseph D. Wagner
2002-12-06  3:29   ` Keith Adamson
     [not found] <sdef2367.029@mail-02.med.umich.edu>
2002-12-05 15:17 ` Joseph D. Wagner
2002-12-05 15:38   ` Dave Jones
2002-12-05 15:44   ` Eric Weigle
  -- strict thread matches above, loose matches on Subject: below --
2002-12-05 14:58 Nicholas Berry
2002-12-03 13:03 cs driver SANTHOSH K
2002-12-04 15:26 ` is KERNEL developement finished, yet ??? Shane Helms
2002-12-04 17:01   ` Joseph D. Wagner
2002-12-04 18:38     ` Alan Cox
2002-12-04 18:07       ` Richard B. Tilley  (Brad)
2002-12-04 18:21         ` Richard B. Johnson
2002-12-04 18:39           ` Erik Andersen
2002-12-05 16:59           ` Bill Davidsen
2002-12-05  0:27   ` jeff millar
2002-12-05 23:55     ` Frank van Maarseveen
2002-12-06  0:24       ` Shane Helms
2002-12-06  3:00       ` jeff millar
2002-12-06  3:36         ` Miles Bader
2002-12-06  8:55         ` Helge Hafting

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=11E89240C407D311958800A0C9ACF7D1A33CD5@EXCHANGE \
    --to=edv@macrolink.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shanehelms@eircom.net \
    --cc=wa1hco@adelphia.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®