dude....i believe no one can change u from using KDE...but we never asked u too...but performance wise let me tell u....KDE cannot beat GNOME...this is what i have to say....
""KDE is written in C++. While this is not necessarily a problem, it can be when Visual Basic reject programmers (which the KDE project is overrun with) do not know enough to avoid important pitfalls that plague C++ software projects; KDE suffers badly from stupid use of autoincrementing operators and iteration with C++ objects and masses of unnecessary allocations and deallocations of memory -- two of the most comon problems in C++ software.
Perhaps the most cretinous of all problems is blaming the extremely slow startup times of KDE apps on GCC. The GNOME 1.x releases were hardly svelt (2.x fixes many of these issues), but GNOME is a fashion cat-walk superwaif when compared to KDE's 500lb fat-momma cheese-burger scoffing trailer trash.
One need only look at the recent fuss over ugly KDE hacks (such as prelinking) used to bandage up the design and coding flaws in the decrepit KDE architecture to see the truth. ""
and lets not get too much abt this...ha ha...there is some thing that i have for you here to cheer u up....
Allen VS Peter...web fight....KDE VS GNOME
About this entry
Youre currently reading Allen VS Peter...web fight....KDE VS GNOME.
- Published:
- at 7:37 PM on Monday, October 10, 2005
- Previous:
- Older Post
- Next:
- Newer Post
-
8:00 PM
Repeat. It was a not bad code. But bad compiler. The gcc's c++ compiler is not as efficient as Intels or MS c++ compiler. KDE's code uses objects only when necessory and is based on runtime allocation. Not compile time. See the 3.4 code. Aslo what do you mean by "balming slow startup times of KDE apps on GCC". KDE uses the c++ compiler (of gcc) not the C-compiler. Autoincrement operators problem is not KDE or C++ pitfall. Its a GCC pitfall. And its been proved. Not just kde all c++ code have subclassing underoptimization in gcc's c++ compiler.
Take a look at the developer page of KDE. They aren't VB rejects. QT is not VB. Its just because of the QTDesigner many make the comparision.
Besides talking abt objects. Gnome is going the oops way with C# and GTK# too. But since the mono compiler does not have the same problem like the gcc compiler it wont be affected. - 8:03 PM
-
8:08 PM
hey pete....
read the mailing list of KDE for the list of problems it has before even u start talking about the performance...check on the security issues.....
plus Qt is nothin like VB...but falls on the same frequency....and u cannot blame the compiler...its always been a pitfall of c++ which has never been accepted by the c++ hackers - 8:14 PM
-
8:41 PM
I've upgraded without probs. No slowdown. Am using nvidia drivers too (in reply to the previous post) No hangups. No crashes. It also depends on the sys config.
incidently the intel c++ compiler gives better object code than the gcc one. gcc was designed more for sys programming and then extens were added to it. (fortran, java and c++) - 8:42 PM
- 8:37 PM
- 12:58 AM
-
8:10 AM
take a look at nice site -
[url=http://www.young-dro.com/profiles/blogs/buy-cheap-tramadol-tramadol-1] buy tramadol online [/url]
http://www.young-dro.com/profiles/blogs/buy-cheap-tramadol-tramadol-1
[url=http://www.young-dro.com/profiles/blogs/buy-cheap-tramadol-tramadol-1] cheep tramadol paris france [/url] - 8:03 PM
- 11:27 PM
11 comments: