Haiku: the present and the future

Still, I would like to know the answers to a few questions: why today you need to another operating system (local response will result, with the global difficult), and whether the developers of this system to overcome the fear releases?

Operating system officially stuck at around R1/Alpha 4.1, uses tens of thousands of people. The exact number is unknown. Maybe they are smaller.

The vast majority of them have not that system, which came to light in November 2012. Love works wonders and forces you to install on your computer that is called nightly builds. Unofficial releases. With corrections, additions, something new.

The local answer to the question “who needs this Haiku?” – those who use this system, no matter what.

Globally to answer this question, I can’t. On the one hand, in the system there’s definitely something uniquely attractive. Talk about “the gene pool of the operating systems” I, frankly, do not quite understand.

And what about the fear releases…

This is the ninth (and last) part of a series about Haiku. Previous parts:

  • First: Haiku (OpenBeOS);
  • Second: Who needs this… Haiku?;
  • Third: Haiku R1/Alpha1.
  • Fourth: Haiku: The Return Of The BeOS.
  • Fifth: Web+, WebKit and Qt4.
  • Sixth: WebPositive, the best web browser in the world.
  • Seven: Haiku – modesty and understatement.
  • Eighth: Haiku: modern history.


In the previous part described the history of the past, at the moment, the official release of Haiku. At an early stage of formulation of the fourth alpha version, bug tracker was was ticket number 8684. But the author of this ticket did not think to specify in the description of the problem exact configuration of the machine where the bug manifested.

Making sure the bug is not reproduced, it ceased to pay attention. Sometimes the computer (complex device, actually) maybe something happened to him earlier, come in a “bad mood.”

And, most likely, the bug is “closed” with the words “not reproduced”.

Just in case I will specify: the text “bug”, “ticket” and “ticket” are synonymous.

Possible configurations too much, so testers can test the code on all of them. Is it possible to deal with it? Yes. Apple found a very convenient solution: do not multiply entities beyond necessity. Users grumbling, but it’s acceptable.

On 12-13 November, the same bug was registered under the accommodation and 9139 9153. It soon became clear that this is the same 8684. The problem was solved.

However, the fact that for the entire programming world ordinary working situation for the company excessively and publicly proud of the lack of problems in its products, it was a blow below the belt.

The fourth alpha will be the last alpha release, in 2013, the planned R1 release. Just in case, started training more and R1/Beta 1.

In 2014 Adrian Dastugue got the contract to bring R1/Beta 1 in the release state, but, despite the dedicated work from 9 am to midnight, reset the number of open bugs, he failed.

Beta versions are available for running them on the widest possible number of different configurations, in different conditions. The beta warning to the user. And the alpha warning in the square. More dangerous than alpha nightly builds only.

Whether they will cope with religioua?

After adriana Delogu, thread R1/Beta 1 was engaged a few people now (according to 14 August 2018), the trekker R1/Beta 1 was 330 bugs, of which 320 is closed and 10 (only 10!) open. I mean… that’s it? Let’s wait and see.

The branch R1 is the total number of bugs close to ten thousand, and about fifteen hundred of bugs open. Long traders would close their eyes to all these bugs, and would risk bringing a product to market. This has some meaning – in versions 1.0.1 and 1.0.2 some part of the most unpleasant bugs will be fixed, then there will be something to boast…

A few words about the archaic Haiku

One of the tasks solved at the present time the developers of the Haiku – getting rid of obsolete parts of the system, ensuring its compatibility with BeOS R5. These parts of the system exist in it since 2001, and, of course, much of the system somehow depends on them.

When writing new code, as applied (outside of Haiku, Inc.) or systemic, the old library was used. Not a trivial task, but without its decision to move forward is not easy.

Of course, to use applications written for the BeOS will be impossible, but…

Swift in Haiku

In may and August 2017, the Intern program GSoC Joseph ‘Calvin’ hill, undertook a project to move the Swift language Haiku.

Mentors Joseph was jérôme Duval and Julian Harnath.

It was not about a complete transfer Swift for four months is unrealistic. The task of Joseph was porting the LLVM compiler Swift REPL (this is the swift command-line), and other basics.

In July, Haiku was already possible to compile a simple program in Swift 3.1.

In the last days of summer, Joseph began to work to support Swift 4.

Joseph received a scholarship (he is a third-year student at the University of Hull in East Yorkshire, UK) after GSoC planned to continue the transfer of Swift in Haiku. Along with learning.

Work on Swift continues, and I may soon have a reason to contact Haiku. This language I love.

Today and tomorrow

In 2018 in Haiku ported LibreOffice, and began work to transfer the Rust language.

And, I will tell you the big secret, work on the R1/ Beta 1 also intensified. It is not know what time, and over whether it is a new release…

What will happen tomorrow, and if Haiku hope for a better place in the world of the future?

Let’s wait and see…

0 Comments on “Haiku: the present and the future”

  1. Black on black in the Charger I’m creepin’ Rub me the right way, you might get a genie B o B, black Houdini

Leave a Reply

Your email address will not be published. Required fields are marked *