[haiku-development] Re: What's the status of Haiku?
- From: Ralf Schülke <ralf.schuelke@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Wed, 3 Sep 2014 12:15:28 +0200
Yes Haiku are verry nice and works, but some leading ships are not so nice.
When i leading ship haiku :-) Then will pushed some thnigs:
- 1. compiler
Here i see llvm/clang more potetial as the gcc4
- 2. more 64Bit support for x68 and AMD (MIPS are comming back) (yes
remove r5 backward compatibility)
- 3. new simple but mordern design like chrome os
- 4. Stable the KITS, because App Developer can make Apps yet and by a
new release need only recompile the app.
- 5. remove unless code (back up this before) eg: atari, mk68 port and
x86 32bit and more
- 6. learn other devleopers from guru developers, this can do with
documentation what haiku are and how its works.
- 7. remove blobs, we dont need a closed code in haiku, free are better.
- 8. a set of hardware he work and a main development board
(minowboard are x86, arm ? Tegra board?), here we need communicate
with hardware ventor.
-9. case studio of apps for making music, video, imageprocessing etc..
- 10. democratically duration of members of board in a two years
circle, with a memo of haiku design
(kernel->[libs->]server->kits=>apps) and this cant remove or de
designed.
Let us make a own world and looking what is good and not and what are
the future eg: 4k are coming is haiku ready for this (font rendering ,
layouting, etc)
so far, so good
stargater
2014-09-03 11:21 GMT+02:00 Rudolf Cornelissen <rudhaiku@xxxxxxxxx>:
> I wrote apparantly:
>
> - Sounds like much farther developed that still early alpha state ;-)
>
> I meant of course that it's so stable and useable to me that I think from
> that perspective it should not be still alpha. It seems to deserve more than
> that. And it deserves much more users than there actually are :)
>
> Rudolf.
>
>
> On Wed, Sep 3, 2014 at 11:17 AM, Rudolf Cornelissen <rudhaiku@xxxxxxxxx>
> wrote:
>>
>> Hi there,
>>
>> If someone is to complete the ARM port and add a serial driver, I could
>> complete the translation myself :-)
>> Though of course the acceleration functions are nolonger used on Haiku.
>>
>> BTW I still love haiku, and every time I boot it I see again how stable it
>> is and how easy it works.. Sounds like much farther developed that still
>> early alpha state ;-)
>>
>> These days BTW my full-time job concerns windows app development and
>> maintenance.. never thought I'd be doing that..
>>
>> Bye!
>>
>> Rudolf.
>>
>>
>>
>> On Fri, Aug 29, 2014 at 8:41 PM, Andrew Hudson
>> <dmarc-noreply@xxxxxxxxxxxxx> wrote:
>>>
>>> >http://haiku-os.org/legacy-docs/writing-video-card-drivers ?
>>>
>>> >François.
>>>
>>>
>>> >Yes, it was an interesting reading but unfortunately the Chapter 6
>>> > (Writing the Driver) was never finished
>>>
>>> >I've seen this document in numerous places, for years, & always hoped
>>> > that it would be finished by those with the knowledge to do so. Sadly, it
>>> > never happened. This could have ended up being the most important driver
>>> > document for BeOS/Haiku. It's missing >far more than just chapter 6. Maybe
>>> > developers will drift in & flesh it out more as time goes own 7 with the
>>> > proper motivation. It might be beneficial to ping past video driver
>>> > writers
>>> > & ask them to take a few moments of their time to contribute to the
>>> > document. >The worst that could happen is that they say 'no'. But, if they
>>> > say 'yes'...
>>>
>>> >--
>>> >Regards,
>>> >A. D. Sharpe, Sr.
>>>
>>> >I second that, the article was very good.
>>>
>>> No article will ever have enough details on how to write a functional
>>> video card device driver. If you really want to write a video card device
>>> driver
>>> you must go to the source code and figure it out. Recompile it, make
>>> changes, understand what the kernel wants, put the time in. This is how it
>>> is done.
>>>
>>> Otherwise you are just arm chair coding. I encourage you to make the leap
>>> and just go do it.
>>>
>>> Andrew
>>
>>
>
Other related posts:
