Linked by Thom Holwerda on Thu 7th Jul 2005 14:41 UTC
Gnome The second point release of the stable 2.10.x branch of GNOME is now officially released. This release has seen continued work to eliminate memory leaks, plain bugs and in general improve and polish the stable series of GNOME. Source: bindings, desktop, platform.
Thread beginning with comment 1400
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Gnome bloat and is slow
by Mystilleef on Fri 8th Jul 2005 14:55 UTC in reply to "RE[4]: Gnome bloat and is slow"
Mystilleef
Member since:
2005-06-29

That's another problem with the C++ community. Everytime you point out how totally wrecked the language is, they tell you you are not doing things the right way.

Use feature X, don't use feature Y. You are coding C not C++. Use this library, don't use that library. All the while, time is passing, resources are been expended and I'm way past my deadline.

This is the language Mr Anonymous thinks will automatically do wonders for GNOME. This is the language to bring stability, security and consistency to GNOME.

There is a reason I called C++ unwieldy, and MORB just proved my point. It's unwieldy because no bloody person ever does things the right way. The amount of gotchas inherent in the language will make stone-cold killer squeal like a lil' bitch.

I know...I know...I'm probably coding C++ the wrong way...

*sighs*

Reply Parent Score: 1

RE[6]: Gnome bloat and is slow
by MORB on Fri 8th Jul 2005 16:02 in reply to "RE[5]: Gnome bloat and is slow"
MORB Member since:
2005-07-06

You sound more like you never really tried, actually.

And there are people doing good, working, proper, readable, enjoyable c++. KDE is an example.

Reply Parent Score: 1

rhavyn Member since:
2005-07-06

nd there are people doing good, working, proper, readable, enjoyable c++. KDE is an example.

That's kinda funny because KDE (because of Qt) is using non-standard extensions and preprosessors instead of using built in C++ constructs. So does that mean that "good, working, proper" C++ doesn't actually need to use C++ constructs?

Reply Parent Score: 1

Mystilleef Member since:
2005-06-29

As far as I know, the KDE/Qt folks shawned much of the C++ standards, and for good reasons might I add.

Reply Parent Score: 1