Home | Forums | Submit   Haiku Generator | Quotable JLG | The Icon Tarot 

Xentronix Changes Focus to MacOSX

Filed under the:  department.
Posted by:Deej on Monday, 04 Jun, 2007 @ 9:17 AM
Art / Image

As reported over at Haiku News, Xentronix is ceasing development on BeOS/Zeta/Haiku platforms and focusing entirely on the MacOSX platform. It’s very sad to see them go, but it looks as if Frans, et al, took a hit, both financially and in faith, during the recent Zeta troubles. Can’t say that I can blame them. For the details, head on over to Haiku News to read all about the email Remi received from Frans.

5 Responses to “Xentronix Changes Focus to MacOSX”

  1. biffuz Says:

    Not a surprise. If you like to develop software and sell it, BeOS/Haiku/ZETA is just pointless now. Not even Linux is a good market. You’re left with Windows or Mac, which one would you choose?
    I will continue to develop AtomoCAD for Haiku, but my target is OS X now.

  2. Jonathan Thompson Says:

    Perhaps Haiku will somewhat reinvigorate the market for commercial development, but it’ll be hard to support anything beyond quickly done/low-complexity products.

  3. Yez Says:

    You know what? Quickly done/low-complexity products done well work just fine for me! The simpler, the better and maybe that should be a mantra for a while for Haiku. I would like simple apps that just work. We can add bells and whistles later! Biffuz, thanks for taking the time to continue developing AtomoCAD for Haiku and I completely understand why you want to build for MacOS X as well. Good Luck!

  4. Konrad Says:

    How hard would it be to port QT Framework to Haiku/BeOS? Then devs dont have to choose platform, they can get a port easily done in days or even shorter.

  5. Jonathan B. Thompson Says:

    Hi Konrad,

    I’ve not verified it, but I suspect there are some threading primitives that QT Framework may use that exist on other OS’s (WaitMultipleObjects and stuff like that) that BeOS/Haiku has no support for, and would be a PITA to implement.

    Thus, if my suspicions are correct, porting that would be a nightmare, even if the GUI details of BeOS don’t cause other problems, as well as other things I’ve not mentioned that I may not know/suspect about specifically.

Leave a Reply

You must be logged in to post a comment.

[powered by WordPress.]

Random Haiku:

BeOS geeks and
haiku error messages -
the perfect marriage.

Since 1998 - Until the Last User Leaves...
BeGroovy, established 1998

search BeGroovy:

BeGroovy Archives:

February 2021
« Sep    


23 queries. 0.059 seconds

[powered by WordPress.]