Comments on: Back in Time: Changing Linux http://www.mikesplanet.net/2007/03/back-in-time-changing-linux/?utm_source=rss&utm_medium=rss&utm_campaign=back-in-time-changing-linux Just a Big Ball of Gas Wed, 11 Aug 2010 02:48:00 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Alaa http://www.mikesplanet.net/2007/03/back-in-time-changing-linux/comment-page-1/#comment-1802 Alaa Wed, 28 Mar 2007 12:22:58 +0000 http://www.mikesplanet.net/2007/03/back-in-time-changing-linux/#comment-1802 I don't think that a Code of Conduct would stop people from behaving this way anymore than the law actually stops criminals from committing crime. I too have faced such issues in the past. So now i make sure that anybody who asks me any question gets a proper and polite answer. Even if i want to tell him that he should read the manual, i tell him so politely and direct him if possible. People who give "RTFM" as an answer to any question do not belong to the free software world. I don’t think that a Code of Conduct would stop people from behaving this way anymore than the law actually stops criminals from committing crime.

I too have faced such issues in the past. So now i make sure that anybody who asks me any question gets a proper and polite answer. Even if i want to tell him that he should read the manual, i tell him so politely and direct him if possible.

People who give “RTFM” as an answer to any question do not belong to the free software world.

]]> By: Mike http://www.mikesplanet.net/2007/03/back-in-time-changing-linux/comment-page-1/#comment-1801 Mike Tue, 27 Mar 2007 20:15:59 +0000 http://www.mikesplanet.net/2007/03/back-in-time-changing-linux/#comment-1801 Just a mental glitch between my brain and fingers:). Too err is human, to proofread divine. Just a mental glitch between my brain and fingers:). Too err is human, to proofread divine.

]]> By: Steve http://www.mikesplanet.net/2007/03/back-in-time-changing-linux/comment-page-1/#comment-1800 Steve Tue, 27 Mar 2007 19:05:29 +0000 http://www.mikesplanet.net/2007/03/back-in-time-changing-linux/#comment-1800 It might be something really obvious, but why do you consistently call it the code of conduit instead of conduct? It might be something really obvious, but why do you consistently call it the code of conduit instead of conduct?

]]> By: frando http://www.mikesplanet.net/2007/03/back-in-time-changing-linux/comment-page-1/#comment-1799 frando Tue, 27 Mar 2007 18:34:25 +0000 http://www.mikesplanet.net/2007/03/back-in-time-changing-linux/#comment-1799 If I could go back and choose, i would definitely undo the creation of two desktop/widget APIs (Qt/GTK). Having one single, solid widget API would avoid many pains on the linux desktop and speed up the adoption of linux on the desktop enourmously. It's just a pain in the arse to start up the GIMP while you're running KDE and being presented a totally different theme. I know, there's QtGTK and metatheme and everything, but IMO, so much of developer's energy is wasted on all this. All this would not be required if everyone would have sticked to KDE/Qt in the beginning, and we'd have the same world class GUI applications by now, but they'd all be based on the same API. How cool would that be? ;) And just to not start a flame war or to give food to the trolls ;) : I'm talking about the underlying APIs here, not about the desktop experience. I would totally support two desktop system (the gnome-like with simple administration and a focus on a great default usability, and a kde-like with heaps of great widgets and lots of things to customize ... think beryl and compiz, which are about to merge), but these desktop systems should be based on the same underlying basic API(s), so that no application had to be either Gnome- or KDE-specific. Oh yes, it would be good fun to travel back in time ;) When not thinking of hypothetical changes in history, however, I of course support all the freedesktop initiatives and DBUS and QtGTK and everything ... ;) but still, the whole Gnome project should just port to Qt4 and the KDE 4 APIs :P If I could go back and choose, i would definitely undo the creation of two desktop/widget APIs (Qt/GTK). Having one single, solid widget API would avoid many pains on the linux desktop and speed up the adoption of linux on the desktop enourmously.

It’s just a pain in the arse to start up the GIMP while you’re running KDE and being presented a totally different theme.

I know, there’s QtGTK and metatheme and everything, but IMO, so much of developer’s energy is wasted on all this. All this would not be required if everyone would have sticked to KDE/Qt in the beginning, and we’d have the same world class GUI applications by now, but they’d all be based on the same API. How cool would that be? ;)

And just to not start a flame war or to give food to the trolls ;) : I’m talking about the underlying APIs here, not about the desktop experience. I would totally support two desktop system (the gnome-like with simple administration and a focus on a great default usability, and a kde-like with heaps of great widgets and lots of things to customize … think beryl and compiz, which are about to merge), but these desktop systems should be based on the same underlying basic API(s), so that no application had to be either Gnome- or KDE-specific.

Oh yes, it would be good fun to travel back in time ;)

When not thinking of hypothetical changes in history, however, I of course support all the freedesktop initiatives and DBUS and QtGTK and everything … ;)

but still, the whole Gnome project should just port to Qt4 and the KDE 4 APIs :P

]]> By: Jameson http://www.mikesplanet.net/2007/03/back-in-time-changing-linux/comment-page-1/#comment-1798 Jameson Tue, 27 Mar 2007 17:45:33 +0000 http://www.mikesplanet.net/2007/03/back-in-time-changing-linux/#comment-1798 Good point, but I think you mean "Code of Conduct", not "Code of Conduit". Good point, but I think you mean “Code of Conduct”, not “Code of Conduit”.

]]>