Linked by Amjith Ramanujam on Fri 15th Aug 2008 05:18 UTC
InformationWeek is speculating on how Linux will change in the next four years. "By 2012 the OS will have matured into three basic usage models. Web-based apps rule, virtualization is a breeze, and command-line hacking for basic system configuration is a thing of the past."
Thread beginning with comment 326982
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Linux will be great of course!
by darknexus on Fri 15th Aug 2008 08:48
in reply to "RE: Linux will be great of course!"
Member since:2008-07-15
For anything to become unifiedd the majority of the foss community would have to do something it's so far shown itself incapable of doing. It would have to sit down, collaborate and, here's the big one, actually agree on standards. By collaborating I do not mean they sit down and begin to discuss standards, only to have some of the developers leave the discussion because they think they could do it better. I mean put aside their pride and preconceptions, sit down together (figuratively or literally), and actually come up with something that pleases the majority of both the developer and user communities. Don't take away the user's choices, but at least set down a common base.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2006-02-06
I truly wish I could be as optimistic as you guys. I'll keep on wishing you guys luck with your projections for 2012 Linux.
I just wish we had a great set of common base software activities API that could be used (although slightly differently to integrate with the possibilities) with most common languages and toolkits.
Things like configuration files API using a single config framework (no, it doesn't need to be registry like, or even to have unified config format, just unified config abstract concepts that we could map to different file formats as each project sees fit);
Common package naming conventions with versioning information sane between all distributions, flags for packages that inform which features or pieces of it are included in some binary package, so that package writers could make packages portable across systems and only re-do the work on those who are incompatible due to distribution choices on different configurations / versions of libraries;
Hmmm I can't think of anything else right now, but I'm sure I could come up with lots of other infrastructure stuff I'd love to have on Linux and that I just can't remember now being almost 4AM.
Getting back to work... I hate freaky deadlines.