Live data from Hacker News

HelenOS 0.8

helenos.org

1–10 of 57 posts

Re: HelenOS 0.8

#2
I like the concept. It sounds like a modern take on some of the plan9 ideas. Decoupling of system components into components that work together through a message passing framework.

Re: HelenOS 0.8

#3
post #2

I like the concept. It sounds like a modern take on some of the plan9 ideas. Decoupling of system components into components that work together through a message passing framework.

Sounds a bit like QNX actually

Re: HelenOS 0.8

#6

For those who, like me, wondered "what's HelenOS?" and got little idea from release notes: http://www.helenos.org/wiki/About

Unfortunately, http://www.helenos.org/wiki/DiffFromUnix presents it as different enough to make porting software difficult. On the other hand, they say they've got GCC and Python, so it's doable.

Re: HelenOS 0.8

#7

For those who, like me, wondered "what's HelenOS?" and got little idea from release notes: http://www.helenos.org/wiki/About

Unfortunately, http://www.helenos.org/wiki/DiffFromUnix presents it as different enough to make porting software difficult. On the other hand, they say they've got GCC and Python, so it's doable.

It it wasn't different enough to make porting software difficult, it probably wouldn't be different enough to bother making.

Re: HelenOS 0.8

#8

For those who, like me, wondered "what's HelenOS?" and got little idea from release notes: http://www.helenos.org/wiki/About

Note the following, from the FAQ page (http://www.helenos.org/wiki/FAQ#WhatisHelenOSusedfor):

"At this point we don't consider HelenOS usable for something different than development and research, but we're getting very close to the point where it will be usable for something really practical."

Re: HelenOS 0.8

#10

For those who, like me, wondered "what's HelenOS?" and got little idea from release notes: http://www.helenos.org/wiki/About

Unfortunately, http://www.helenos.org/wiki/DiffFromUnix presents it as different enough to make porting software difficult. On the other hand, they say they've got GCC and Python, so it's doable.

I am frankly not very impressed with a quick glance at the networking API. What they show would not be difficult to implement as a library atop sockets, and I'm not convinced their callbacks capture the full flexibility of the old APIs. Meanwhile not providing at least a wrapper to handle the most simple socket scenarios to aid in porting strikes me as a bit stubborn. They determined a priori to hate sockets and that's it.
Post reply on HN