I am new to programming, so please understand these are sincere questions.
Wouldn't it make sense if all GRAPHICAL programs used the same library as a STANDARD for the Linux platform? Why not just EXTEND the STANDARD library and work on the code frame work as a community like it should be? Instead of bitching at each other and dividing ourselves, try to find a solution that will handle these problems. Why doesn't someone talk to individuals at KDE and GNOME and see if a middle ground can be agreed upon to where the code could be shared and become seemless in any Linux environment. Why should programmers write code twice to use specific features in both desktops? The Micro$oft syndrome---the over-bloating of code...what could of been optimised, never was.
Some will say, "Well, MicroSoft is already here, why don't we just accept it. The software is easy to use and understand." True, but at what cost does this kind of attitude change? Microsoft, as we know, is poorly written, bloated code that any college hack can create. Hell, even a highschool hack using Visual Buttocks 6 can create. Oops, I mean Visual Basic. This code is like a angry fat lady chasing some poor sap down for the last box of Twinkies in the snack isle...pretty damn scary if you don't turn them Twinkies over I might add. That's like how Microsoft software works...if it doesn't like its environment at that specific time, better get ready to reboot. People like Microsoft so they don't have to learn anything and everything is easy and in a cute little package. Once again, at what cost? How many license fees are you willing to pay? How much more will Microsoft own what you do? These are types of questions that these Microsoft users need to be asked. "Oh, I can't use that because it's not Microsoft compatable." I think that says it all.
Slashdot Mirror
I am new to programming, so please understand these are sincere questions.
Wouldn't it make sense if all GRAPHICAL programs used the same library as a STANDARD for the Linux platform? Why not just EXTEND the STANDARD library and work on the code frame work as a community like it should be? Instead of bitching at each other and dividing ourselves, try to find a solution that will handle these problems. Why doesn't someone talk to individuals at KDE and GNOME and see if a middle ground can be agreed upon to where the code could be shared and become seemless in any Linux environment. Why should programmers write code twice to use specific features in both desktops? The Micro$oft syndrome---the over-bloating of code...what could of been optimised, never was.
Devin
Some will say, "Well, MicroSoft is already here, why don't we just accept it. The software is easy to use and understand." True, but at what cost does this kind of attitude change? Microsoft, as we know, is poorly written, bloated code that any college hack can create. Hell, even a highschool hack using Visual Buttocks 6 can create. Oops, I mean Visual Basic. This code is like a angry fat lady chasing some poor sap down for the last box of Twinkies in the snack isle...pretty damn scary if you don't turn them Twinkies over I might add. That's like how Microsoft software works...if it doesn't like its environment at that specific time, better get ready to reboot. People like Microsoft so they don't have to learn anything and everything is easy and in a cute little package. Once again, at what cost? How many license fees are you willing to pay? How much more will Microsoft own what you do? These are types of questions that these Microsoft users need to be asked. "Oh, I can't use that because it's not Microsoft compatable." I think that says it all.