To read all comments associated with this story, please click here.
ebasconp,
"The problem is that turning your hobby OS in something usable (more yet with the current high standards) is a titanic task."
You got that right. For most users, what makes an OS "usable" is the apps. You might have a great functioning kernel + desktop environment, but without the apps it's useless to a great majority of users.
Even windows itself would be useless if it were a hobby os which worked as it does now but had no software for it... The property which makes it useful is the software.
For better or worse, the only way for hobby OSes to get real apps is to run them in a compatibility layer. But implementing another OS's APIs is a significant and thankless commitment. Look at the wine project, they've done a lot of good work, but it's still hit or miss and nearly everyone buying windows software runs it on windows.
The big questions are:
How should a hobby OS dev convince users to run foreign software on a compatibility layer in the new OS?
How should a hobby OS dev convince devs to write/port software to the new OS?






Member since:
2005-07-06
If more developers "dog fooded" by using their own os only, it make life a lot better because things speople actually need to get productive would get worked on. I once heard a developer of a small OS say "I use Linux and only boot into <my os> to do develeopment on it". Seriously, if your own OS isn't good enough for you, why should anyone else care?