Linked by Thom Holwerda on Tue 16th Jan 2007 13:34 UTC, submitted by Tomasz Dominikowski
SkyOS Lots of news on SkyOS. Kaffe using GNU Classpath (without AWT) is now working fine on SkyOS, just like Wine. Although there is no Wine graphics driver yet, you can already start Windows console applications directly from within SkyOS (once a Wine/SkyGI backend is available Wine should run on SkyOS as good as it does on Linux, and will be available via Software Store). On the driver side there is now an ACPI driver including support for ACPI power/sleep buttons (a SkyOS service, the PowerMonitor, will react on power events with configurable actions like shutdown, reboot, etc.). And finally, the SkyOS LiveCD is shaping together and should soon be available. Take a look at the changelog for all updates. Note: If you have problems accessing the SkyOS.org website, please click read more for how to solve this issue. Other than that, read more for a first glimpse of yet another improvement coming to SkyOS.
Thread beginning with comment 202450
To read all comments associated with this story, please click here.
backwards compatibility
by Darkness on Tue 16th Jan 2007 23:55 UTC
Darkness
Member since:
2005-08-27

One of the great things about the current state of skyos is that it absolutely does not care about backwards compatibility :p

You made a nice application for build XXXX and it doesn't work in build XXXX+y, well, go fix it!

Backwards compatibility is something that I think hurts some other operating systems in certain areas.
For example Linux, why do they keep supporting the old open sound system? Dump it, allow only alsa in the next release and force devs finally to update their software to make use of the new/improved features.
Have the people of alsa/arts/esd sit together and make it uniform and working out of the box, on every system

Reply Score: 2

RE: backwards compatibility
by arielb on Wed 17th Jan 2007 00:41 in reply to "backwards compatibility"
arielb Member since:
2006-11-15

it's why linux still uses x windows and aros still doesn't have memory protection. I certainly hope that haiku doesn't turn into another aros.

Reply Parent Score: 1

RE: backwards compatibility
by adamk on Wed 17th Jan 2007 00:47 in reply to "backwards compatibility"
adamk Member since:
2005-07-08

In all fairness, darkness, any reasonably decent distribution will have audio setup for the user, out of the box, without the user having to worry about if he or she is using alsa/oss/esd/arts. I certainly haven't had to worry about it in a long time.

Compare this to SkyOS which is missing drivers for lots of audio chipsets :-)

Adam

Reply Parent Score: 1

RE[2]: backwards compatibility
by Kelly Rush on Wed 17th Jan 2007 03:47 in reply to "RE: backwards compatibility"
Kelly Rush Member since:
2005-06-30

I got my USB microphone working one time with Ubuntu (not sure how), and it hasn't worked since. ;)

Reply Parent Score: 1

RE: backwards compatibility
by saxiyn on Wed 17th Jan 2007 00:48 in reply to "backwards compatibility"
saxiyn Member since:
2005-07-08

For example Linux, why do they keep supporting the old open sound system? Dump it, allow only alsa in the next release and force devs finally to update their software to make use of the new/improved features.

Because ALSA is Linux-only, but OSS support is widely available. Until you get ALSA working on BSDs and numerous other Unix systems with OSS support, supporting *only* OSS leads to Linux lock-in. GNOME and KDE run on Unix-like systems, not on Linux, and such lock-in would be hard to sell.

Reply Parent Score: 2

RE[2]: backwards compatibility
by Darkness on Wed 17th Jan 2007 01:00 in reply to "RE: backwards compatibility"
Darkness Member since:
2005-08-27

Because ALSA is Linux-only, but OSS support is widely available.
ok, didn't think of that for a moment ;)

Reply Parent Score: 1