Linked by Thom Holwerda on Fri 20th Aug 2010 21:40 UTC, submitted by koki
BeOS & Derivatives This summer, too, the Haikuproject is part of the Google Summer of Code event. One of the more interesting projects is the Services Kit (draft document!) by Christophe "Shusui" Huriaux, which is an API to facilitate the creation of native web-enabled programs using standard web protocols and data exchange mechanisms.
Permalink for comment 437806
To read all comments associated with this story, please click here.
Cool thread / frustrating thread
by AndrewZ on Mon 23rd Aug 2010 17:21 UTC
AndrewZ
Member since:
2005-11-15

This thread is both very exciting and very frustrating to read. It's exciting because it reflects the the fact that Haiku is nearing a tipping point. It's stable, the speed is good, Bugs are quickly fixed, lots of classic BeOS apps run fine, the development environment is mature, it's gaining visibility. That's all good.

But there is a lot of misinformation about Haiku. There is a lot of "arm chair quarterbacking" by folks who are interested but haven't taken the time to install Haiku and take it for a test drive. Like for instance: "and also adapt it to modern hardware."
Haiku runs fine a lot of modern hardware for basic purposes. Lots of drivers are supported. Here are instruction for installing Haiku as a dual boot. It also runs embarrassingly well on old hardware:
http://haikuware.com/wikis/doku.php?id=tutorials:install-haiku-besi...

The example of BeOS running many video streams without dropping frames is driving me crazy so let me address that. This was a great demo for 10 years ago. But just like the spinning teapot was cool, then wasn't cool, I think its time to find a better demo for Haiku.

What is the major strength of Haiku? It is the application APIs and the "mini" kernel. In operating systems theory class you learn about the trade-off between through-put and response time. An example of through-put is database transactions per second. Linux is very good at this, Solaris is/was best at this. Because the kernel was designed and tuned for throughput. BeOS was designed to be the best at quick response to user-centric applications. "It feels fast" means it responds quickly to GUI events. Why would one OS feel faster and not block on GUI operations? Because the application APIs and kernel were designed for minimal latency in the kernel.

These days I think you could probably play 6 or 8 video streams on Windows or Mac with no dropped frames. th4e hardware is so much faster and the video subsystems are much improved. It also not that exciting because how many videos do you need to play at once? Maybe 1 or 2. So playing multiple video streams on Haiku is no longer a great demo.

So what is a great demo on Haiku? I think we need some new ideas here. We need to write some applications that reflect what people do on PCs today AND use the application APIs to show it off in Haiku.

So I give this challenge: Write a simple app for Haiku and use the application API. It's fairly simple and very straight forward. There is an excellent tutorial for programming apps on Haiku. It starts with no assumptions in chapter 1, teaches you basic C++, and moves up to basic API/GUI programming by chapter 20. If you have never coded before but are interested, start here. If you are a seasoned coder but have never written a Haiku app, start here but skip ahead:
http://www.haiku-os.org/development/learning_to_program_with_haiku

I have more to say but maybe this is enough for one post.

Happy Haiku hacking

Reply Score: 4