Slashdot Mirror

← Back to Stories (view on slashdot.org)

BeOS Clone Haiku Releases R1 Alpha 4

Posted by Unknown on from the unix-haters-handbook dept.

New submitter kallisti5 writes "The Haiku project released their 4th alpha release today. A year and four months have passed since the 3rd alpha release. Haiku R1A4 includes several enhancements such as a large number of bug fixes, early IPv6 support, better drivers, improved file system support, better localization, and a wide variety of new features and applications." Multimedia enhancements include support for modern Intel and Radeon HD cards.

7 of 117 comments (clear)

  1. By the time version 1 arrives, in 10 years ... by Taco+Cowboy · · Score: 4, Insightful

    ... and nobody will remember what "Haiku" or "BeOS" is all about.

    --
    Muchas Gracias, Señor Edward Snowden !
    1. Re:By the time version 1 arrives, in 10 years ... by origin2k · · Score: 5, Funny

      Be is gone so sad
      Haiku is here so no fear
      Bits and bytes take time

    2. Re:By the time version 1 arrives, in 10 years ... by Anonymous Coward · · Score: 5, Funny

      the slashdot racists
      trolling with small endowment
      go back to 4chan

    3. Re:By the time version 1 arrives, in 10 years ... by lucmove · · Score: 4, Funny

      In 10 years, nobody will remember what "Haiku" or "BeOS" is all about.

      ...unlike today, when hordes of people know what "Haiku" and "BeOS" are all about. Right?

  2. In future news by viperidaenz · · Score: 5, Funny

    I just got back from a trip in my DeLorean and in 2017 Haiku Release R1 Beta 1 was announced.

  3. Re:NO ONE GIVES A FUCK!!!! by Scarletdown · · Score: 5, Funny

    fuck you geek faggots.

    Go ahead and continue. You got the format correct for the first line. Now you need to come up with 2 more lines for your entry to be complete.

    --
    This space unintentionally left blank.
  4. Re:Hoping for a light GPL-free desktop by jc42 · · Score: 4, Informative

    If you're trying to develop a commercial product, best make sure it has no GPL code in it.

    I think you mean: If you're trying to develop a commercial product by stealing others' code and claiming it's your own, best make sure it has no GPL code in it.

    GPL code has no legal problems that aren't much larger if you base your work on someone else's proprietary code. GPL merely legalizes your "stealing", but says you must then permit others to "steal" your code as well. With proprietary code, anything you do with it is illegal.

    Not that this matters much to the users, who mostly don't ever write any code, much less attempt to sell it.

    (There's a long tradition in technical circles of taking insults and turning them into technical jargon. And there's the old saying that copying from one person is plagiarism, but copying from many is research. ;-)

    --
    Those who do study history are doomed to stand helplessly by while everyone else repeats it.