Linked by Thom Holwerda on Mon 17th Apr 2006 12:02 UTC, submitted by SilentBob4
Ubuntu, Kubuntu, Xubuntu MadPenguin takes a look at Flight 5 of Ubuntu Dapper, and concludes: "All in all, Ubuntu 6.06 is gearing up to be quite an impressive release. Granted, I saw some bugs during my stay on the distribution, but can I really complain? It's not a full release, so it deserves some breathing room. Considering some of the horribly authored software I've looked at over the years, I feel that Ubuntu in pre-release form is more stable than other distros when they reach final release status. It's not quite in the league of Slackware and Red Hat/Fedora in that respect yet, but it's surely getting there in a hurry."
Thread beginning with comment 115595
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: The thing about Ubuntu is
by n0xx on Mon 17th Apr 2006 16:32 UTC in reply to "RE[2]: The thing about Ubuntu is"
Member since:

Like is should be?, nobody has do it in C thats why it's in C#, what difference would it make being done in C?

By the way, the overhead of mono is smaller now and mono apps perform just as good as C apps.

Like... no app running on top of a virtual machine will ever run as fast as an app running natively. Do you have bechmarks to back up yout claim?

Reply Parent Score: 2

SlackerJack Member since:

And were are your equivelent C apps that beat mono apps?. What is your problem with C# anyway, because it's damn site easier than C to learn.

Reply Parent Score: 0

somebody Member since:

And were are your equivelent C apps that beat mono apps?.

Probably all operating systems? Why do you think MS pulled out most of managed code out of Vista.

Believe me. Until heavy load or long run is in question, overhead is just too big.

Apps that rely on small ammounts of ram that fit in memory (with its sloppy memory handling) are probably faster than native C. In C one has to do all allocating and deallocating, which leads to performance suffering. VM on the other hand runs GC, where one memory can be reallocated without even being ever deallocated. But if your memory load is bigger than ram, GC will have to step to handle its job. Well, trouble is that GC needs all references released and people do tend to forget to release references on them. Either using WeakReference or using (var = null) helps a lot here but not even nearly enough. I can give you more exact examples if you want.

What is your problem with C# anyway, because it's damn site easier than C to learn.

Agreed, but I think he doesn't have much against C#. He's just being more objective than you.

I use it daily for my desktop projects. But on server side? I thought of it, tested it and lost all my hope I'll ever be coding service in C# (and as you said, it is a damn nice language. I would preffer results were different much more than this reality).

Reply Parent Score: 1