Linux needs to do more for programmers
|
|
|
Comments (13)
Quoting:Phew, being Linux must be the hardest task on this planet!
It probably is!
But Linux is strong and Flexible and resourceful, that's ok
SJVN also had an article last month, "Is Linux Graying?" http://blogs.computerworld.com/15936/is_linux_graying
I think it makes an interesting tie-in, in that the old-school developers, who are content with old-school tools (and which keep well to the KISS principle), need to make room for younger developers, newer tools, and more sophisticated project tracking. The old-school devs don't necessarily need to step aside, but the "big tent" needs to get bigger.
And, let's face it, the Linux kernel itself hasn't exactly held to the same size, or the KISS principle. (Go ahead, call me a heretic.) Because Linux is open, anyone can tack on anything they wish, and many have. Tinker here, try this there.
One of the side projects in the kernel, is an ongoing effort to hunt down and remove dead code. From what I've read in the Lions book, a thorough code review could have accomplished this in the Unix kernel in a week or two. I seriously doubt this would be the case with Linux, even with many eyes all over the world.
So, if the Linux kernel can grow, so can Linux development tools. And perhaps the tools should grow, with an eye towards broad project management.
I think it makes an interesting tie-in, in that the old-school developers, who are content with old-school tools (and which keep well to the KISS principle), need to make room for younger developers, newer tools, and more sophisticated project tracking. The old-school devs don't necessarily need to step aside, but the "big tent" needs to get bigger.
And, let's face it, the Linux kernel itself hasn't exactly held to the same size, or the KISS principle. (Go ahead, call me a heretic.) Because Linux is open, anyone can tack on anything they wish, and many have. Tinker here, try this there.
One of the side projects in the kernel, is an ongoing effort to hunt down and remove dead code. From what I've read in the Lions book, a thorough code review could have accomplished this in the Unix kernel in a week or two. I seriously doubt this would be the case with Linux, even with many eyes all over the world.
So, if the Linux kernel can grow, so can Linux development tools. And perhaps the tools should grow, with an eye towards broad project management.
What's interesting to note, is a 'big part' of Linux-environments (excluding Firefox and probably KDE) can run on a Minix3-kernel as well.
What in Firefox keeps it from running on Minix3?
The whole "bloated Kernel" thing...? From an end user's point of view, it's fine. I'm sure there is code in there that should be removed but my point is simple. When I install a Linux distro to a computer, the drivers for most everything I need are there. Most of my printers work, even the dreaded Lexmarks are coming aboard. The restricted drivers for my ATI, Nvidia or even Matrox cards are a click away, I don't have to futz with webcam drivers, my 24 inch gateway widescreen works out of the box, as opposed to specialized drivers needed by Windoze and an old legacy Turtle Beach sound card works. Windows used to give me fits with that card. Again, I wouldn't know Kernel code if it smacked me in the backside but what I do know is that "bloated Kernel" saves me about 3 hours as opposed to installing Windows on a bare metal machine.
The KDE team has substantial experience redoing a large code base. Maybe we should turn the kernel over to them now that KDE 4 has been perfected. They also have detailed knowledge of what is best for users, so they could get rid of some of the bloat that comes from supporting hardware that users should not be using.
Bigg...almost got me.
The KDE team has substantial experience redoing a large code base. Maybe we should turn the kernel over to them now that KDE 4 has been perfected. They also have detailed knowledge of what is best for users, so they could get rid of some of the bloat that comes from supporting hardware that users should not be using.
Shame there isn't really anything as a sarcasm tag.
The KDE team has substantial experience redoing a large code base. Maybe we should turn the kernel over to them now that KDE 4 has been perfected. They also have detailed knowledge of what is best for users, so they could get rid of some of the bloat that comes from supporting hardware that users should not be using.
Shame there isn't really anything as a sarcasm tag.
> The KDE team...
Now you've done it. :)
Now you've done it. :)
LOL @bigg
Kernel Developers and Enhancers.
What did you think "KDE" stood for?
What did you think "KDE" stood for?
Quoting:What in Firefox keeps it from running on Minix3?
Something with 'threads' I believe. Not sure, but Andrew mentioned it, which obviously shows they contemplated it.
Quoting:From an end user's point of view, it's fine.
Yes, Linux is fine. But it 'could exist' something is even better. Something which aims for simplicity, and if you inject 1000 faulty drivers (randomly screwed by some script), it doesn't even crash.
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help
Sign up and post (it is free) or Log in and post

Now, Linux needs to do more for programmers.
Phew, being Linux must be the hardest task on this planet!