Linked by David Adams on Mon 4th Oct 2010 19:32 UTC, submitted by Idefix
Permalink for comment 443993
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
More Features »
Sponsored Links



Member since:
2010-03-08
There are interesting things in this post, but I think you misunderstood the original comment and went a bit too far in UNIX hate to make a good point.
The OP complained about several things. Apart from lack of applications on an OS that has been here for a long time, he complained about the low-leven layers (networking stack) and about the lack of vision, of plans for the future. You did not answer those.
Agreed, it's good to point this out. UNIX advocates' point is that it can be adapted to just about anything, but I'm more skeptical about this myself. It remains an OS based on text files and pipes, with a user/admin security model, not exactly the best start for a mono-user OS design.
This is highly debatable (and I'm writing a kernel in C++). Several features of C++ (exceptions, RTTI...) require runtime support and can be considered dead for kernel development. Other, like templates, are nice but more adapted to API coding than low-level OS code. When writing code at the kernel level, it's mostly classes (for code separation in independent blocks) and operator overloading (for easier debug code than printf) which prove to be useful. Where most of C++ really shines is on the interface side, and you can very well make a C++ interface to a C kernel.
Yeah, it's written in managed code, like those experimental OSs written in Java we've had for ages. And ?
This is ridiculous. Singularity has been canned by microsoft and doesn't have the tools which server users use daily. Plus, being fully written in managed code, it will have a comparatively weak performance, maybe suitable for the desktop but not for the power-hungry server market.
Oh, come on ^^ Aren't you burying it a bit fast ? Look at the current state of Haiku, it's not desirable for anyone else than BeOS fans, and afaik there are no plans to change this.
User-friendliness is about UI, and that of Haiku is not nearly close to KDE for that matter. It's for devs that UNIX apis are terrible, and they use extra layers like QT anyway.
This is just ridiculous. A compiler is a compiler, no matter how you see it. It has a well-defined purpose, so there's not much room for improvisation. GCC compiles well-optimised code from many languages to a very wide range of binary targets, so it's a good compiler, there's nothing else to say about it