Let me put it another way. Its my contention creation of software boils down to:
A. Visionary, what should software do and when is the right time to do it.
B. Architect, how do you best implement visionary's vision.
C. Project Manager, how put together the nuts and bolts to build the architects plan
D. Usability people to layout how the code will interact with the user.
E. Coder, hacks code
F. Document writers
G. QA, and users to make sure the software works right
Maybe the problem in the open source world is that it has lots of C and E, sometimes has B, is really short of A and D.
Chill out friend. You wouldn't want to look like a posterboy for Linux developer who doesn't get out enough. Its a free world. You can wander off in to the weeds and invent Linux Window Manager #438 and Editor #512. About all me and Mrchaotica were saying was maybe its not always the wisest thing in the world, unless you are REEEALLLLY sure you have a better way or if not you are really just doing it for yourself. Doing serious software takes a lot of effort so the wisdom part of it is to figure out if what you want to do is worth it before you waste your time and potentially that of others on a fizzle.
If you are developing software for you then do whatever floats your boat. But I wager most software developers tend to want to develop software lots of people use, the more the merrier. Which would you rather do, sink a huge effort in a project with a team leader and 1 programmer, usually the same person, and 12 users, or software used by millions of people that is a lasting benefit to the world.
"I'm sure that would work even better than complaining on/."
I'm pretty sure most of the developers are here and this is as good a forum as any. My solution is to use KDE, be happy, and watch GNOME continue down the current road where everyone seems to be getting pissed off and starting splinters. The best way to unify the Linux desktop is for GNOME to shoot itself in the foot which is what this thread is all about. There isn't a snowball's chance in hell of getting the two factions to voluntarily unify at this point so, unfortunately you have to hope for one to fail, and my money is on GNOME based on this thread, don't recall seein g the same kind of angst in KDE though maybe I missed it.
Its a conundrum. I hate seeing new splinter groups form as is the case here, but if it helps an existing splinter fail and go away then thats kind of a plus.
Slashdot Mirror
Let me put it another way. Its my contention creation of software boils down to: A. Visionary, what should software do and when is the right time to do it. B. Architect, how do you best implement visionary's vision. C. Project Manager, how put together the nuts and bolts to build the architects plan D. Usability people to layout how the code will interact with the user. E. Coder, hacks code F. Document writers G. QA, and users to make sure the software works right Maybe the problem in the open source world is that it has lots of C and E, sometimes has B, is really short of A and D.
Chill out friend. You wouldn't want to look like a posterboy for Linux developer who doesn't get out enough. Its a free world. You can wander off in to the weeds and invent Linux Window Manager #438 and Editor #512. About all me and Mrchaotica were saying was maybe its not always the wisest thing in the world, unless you are REEEALLLLY sure you have a better way or if not you are really just doing it for yourself. Doing serious software takes a lot of effort so the wisdom part of it is to figure out if what you want to do is worth it before you waste your time and potentially that of others on a fizzle. If you are developing software for you then do whatever floats your boat. But I wager most software developers tend to want to develop software lots of people use, the more the merrier. Which would you rather do, sink a huge effort in a project with a team leader and 1 programmer, usually the same person, and 12 users, or software used by millions of people that is a lasting benefit to the world. "I'm sure that would work even better than complaining on /."
I'm pretty sure most of the developers are here and this is as good a forum as any. My solution is to use KDE, be happy, and watch GNOME continue down the current road where everyone seems to be getting pissed off and starting splinters. The best way to unify the Linux desktop is for GNOME to shoot itself in the foot which is what this thread is all about. There isn't a snowball's chance in hell of getting the two factions to voluntarily unify at this point so, unfortunately you have to hope for one to fail, and my money is on GNOME based on this thread, don't recall seein g the same kind of angst in KDE though maybe I missed it.
Its a conundrum. I hate seeing new splinter groups form as is the case here, but if it helps an existing splinter fail and go away then thats kind of a plus.