| |||||||||||||
SELF: Anatomy of an (alleged) failureSELF: Anatomy of an (alleged) failurePosted Jun 24, 2010 5:01 UTC (Thu) by bronson (subscriber, #4806)In reply to: SELF: Anatomy of an (alleged) failure by ccurtis Parent article: SELF: Anatomy of an (alleged) failure
IF that day comes (I'm skeptical -- architectural diversity seems to be increasing), I expect kernel devs will be more receptive to it.
Until then, it seems like you're trying to merge the solution before the problem even exists.
(Log in to post comments)
SELF: Anatomy of an (alleged) failure Posted Jun 24, 2010 13:37 UTC (Thu) by ccurtis (guest, #49713) [Link]
I'm not necessarily arguing for FatELF, but isn't anticipating the market and having a solution before something becomes a problem the very definition of innovation?
Personally, I like the idea of having solutions rather than problems.
SELF: Anatomy of an (alleged) failure Posted Jun 24, 2010 17:11 UTC (Thu) by chad.netzer (✭ supporter ✭, #4257) [Link]
Except when you guess wrong, and burden everyone with a worse problem. (Many examples exist, though RAMBUS jumps to mind)
|
|||||||||||||