Slashdot Mirror
Linus Torvalds Speaks Out on Future of Linux
SlinkySausage writes "Linus Torvalds has laid out his plans for the future of Linux, including the 3.0 kernel [there probably won't be one], problems with the Linux release cycles and which distro he personally runs on his home PC. '"Compile everything by hand" ones simply weren't interesting to me,' Torvalds says."
The development of something like a kernel NEEDS a dictator, and if Linus walks away, who is going to have the credibility and/or authority to keep a handle on it? I worry that an advisory 'board' or 'panel' would be the death by a thousand cuts that could really mess up kernel development for linux.
This is a sig. It is like every other sig in the world, except that it is mine, and it is different.
Personally, my favorite aspect of this interview is that Linus himself basically considers the core OS now stable enough that anything new is likely to be incremental instead of ground-shakingly different, at least on the x86 platforms.
Which would imply a stability that leads to dependability which leads to usability which leads to widespread use. At least that is my hope in the enterprise, that the combination of commodity hardware with a commodity, high powered and stable OS can be coupled with increasingly powerful database engines such as mySQL, Veritas, etc. Oracle on Linux is now considered stable as well.
At home? stability leading to dependability leading to integration leading to crossover applications that will no longer depend on a proprietary OS stack to function. The only thing missing from my desired tool set on Linux right now is basically an easy to use, high powered MIDI to music recording and notation system -- and the pieces for all of that is already there -- it's my time to research and integrate the pieces that is in short supply.
I guess my point is that stability and upgradeability cause me to buy (several Linuxes and Win2K). Give me yet a large bulkier OS that doesn't really do much but add coolness (Vista or even XP) and I yawn.
...Open Source isn't the only answer -- but it's almost always a better value than the alternatives...
are you *sure* it was the compile flags that did that, and not some disk fragmenting or cache issues, or whatever else might have screwed your 'test'. Loading openoffice isn't exactly CPU intensive is it, and the compiled versions only have the CPU-specific extras enabled, so I can't see that having SSE3 etc enabled in your OO build v the pre-built one will cause that much of a slowdown.