[haiku-development] Re: R1/a4 initial planning
- From: Ralf Schülke <ralf.schuelke@xxxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Thu, 23 Feb 2012 09:47:24 +0100
I think QT is not the best for a native interface kit for haiku!
I have nit see a GNU/Linux OS with QT/KDE in the Desktop Market!
Linus at self says, GNU/Linux for a Desktop OS have some problems, the
Problems is the many Hardware in the Desktop place.
Haiku OS is designet for a Desktop! Haiku need a not QT for the Desktop OS.
OpenJava is the best chose when we need a good big framework for
Interfacing.
But Haiku can go the way of QNX.
Small OS
Performant
good source and api design
etc.
I see Haiku as Base OS and all other stuff (Browser, other Frameworks, etc)
mast came from other Developents.
Haiku OS need the focus to R1 = stable the basics (API, Kits, etc) and make
open the dors for the industrie (QNX way).
stargater
Am 23. Februar 2012 09:11 schrieb lodewijk andré de la porte <
lodewijkadlp@xxxxxxxxx>:
> You'd likely only notice the availability of Firefox. I agree we need some
> method to the madness and not throw out any competitive edge.
>
> Fact remains being compatable with linux gives us centuries of programmer
> time worth of programs. If we could run Wine we get a shot at Windows
> programs too. It's a hard thing to pass up.
>
> We should strive to get Haiku end user ready ASAP. That said we must
> maintain a pure, complete and "native" structure which hacks and non native
> applications can route around for specific tasks.
> On Feb 23, 2012 8:55 AM, "Justin Stressman" <jstressman@xxxxxxxxx> wrote:
>
>> I don't have anything technically relevant to input, as I'm neither a
>> developer nor even a real programmer etc...
>>
>> But I felt compelled to at least put in my 2 cents as a Haiku fan and
>> user from an emotional standpoint.
>>
>> It pains me to see this talk about ditching the current API (with its
>> Be nostalgia and sense of nativeness etc) to replace it with Qt.
>>
>> It feels like all the things that make Haiku unique and cohesive are
>> being ditched for the sake of expedience. The trend of trying to be
>> BSD licensed, to try to do things natively where possible, etc. It
>> made Haiku feel more clean and special and unique.
>>
>> Now it feels like with all this talk of "let's just ditched all the
>> native stuff and principles and just go for pragmatism... ease of
>> porting and popularity for the general masses who won't know or care
>> really" that it's just turning into another "Linux"... a mish-mash of
>> disparate stuff all glued together. It's one of the feelings I never
>> liked about Linux (having been using it for 15 years now) and now to
>> see Haiku seemingly heading down that path makes me feel sad.
>>
>> To me there's a difference between using some device drivers with glue
>> on the back end... or using the webkit engine in a native browser
>> app... rather than tossing out the native apps entirely and the whole
>> toolkit etc... it's like throwing out the baby with the bathwater.
>>
>> Again, I'm not technically qualified to have my opinion have any
>> weight... I'm just speaking as an ignorant Haiku user/fan. Please
>> don't flame me too hard. :)
>>
>> --
>> 猿も木から落ちる
>>
>>
Other related posts:
