BeOS Legacy vs. modern Haiku OS legal solutions

The biggest reason is not the lack of money, it is the lack of focus. If Haiku would have focused its resources, R1 would have been released years ago.

Who has mandate to do whatever he likes and uses it to be all over the place.

1 Like

Haiku is ABI compatible, not API, it may be a minor destinction but it means that software compiled for BeOS will run, but there is no expectation that it can be compiled on Haiku without changes (or that Haiku cannot deprecate apis) : )

Nobody wants to be told what to do in their spare time, so it is the lack of money. If you want people to work on specific things please donate to the project so they can hire people to work on them.

1 Like

Which is why so many open source projects never reaches maturity. It is fun at first when everybody can work on what they want. But when the project is nearing completion and all the fun parts are done and only tasks that nobody wants to work with are left plus spending hours hunting for hard to find bugs in order to be able to deliver a polished product, then a lot of participants leave for other projects to play around with.

The 80/20 rule means that you often need 20 percent of the effort to create 80 percent of outcomes, and then 80 percent of the effort to create the remaining 20 percent of outcomes. Haiku is within the last 20%.

But yes you can throw money at the problem. But that only forces somebody to focus on the problems nobody else wanted to. So it is still a focus problem and it will only be solved with money if the payed developers are told to focus. @waddlesplash is not told to focus so do not count on his paid work to lead to a final release anytime soon.

2 Likes

I assume your native language is not english, your text doesn’t not make (much) sense, unfortunatly.

@ubu
it’s only translator. I inteted learn an english soon

Haiku is all over the place. The needed features and existing problems preventing Haiku from being a usable daily-driver operating system are all over the place. What do you expect, really?

I think I am, for the most part, working on things which are real problems in Haiku that affect many people or are desired by many. I can’t please everybody, of course, but what do you think I am working on that is a waste of time, or what am I not working on that you think I should be?

8 Likes

There are tons of “real problems in Haiku” and even more desires, in fact there are so many that you will never be able to solve them all within a reasonable time frame – or at all – since it’s partially (drivers, new 3rd party software) a moving target.

To release R1 as soon as possible.

For this a minimum requirement of what needs to be fixed needs to be defined so this work can be prioritized. When this is finished a defined period could be reserved to polish the system before a final release.

  • What is really needed to be fixed before Haiku can be released? Only the essentials. Define this so your work can be focused on it.
  • What bugs or missing features would be nice to work on but is not essential? This can also be defined and worked on if time permits in the polishing phase after the essentials are done.
  • What do not need to be fixed before R1 is released? Do not work on this.

It is not realistic to release a perfectly polished Haiku since the project lacks the resources to do so. So some bugs and warts will have to be included.

According to my opinion it took Microsoft until circa Windows 2000 SP2 until they released their first operating system that was stable (Windows NT got stable around the same time). Apple took even longer where System (“Mac OS Classic”) never got stable and it wasn’t until the early to mid 2000’s when Mac OS X got really stable. I’d argue that desktop Linux or BSD’s are not stable until this day. My whole point is that Haiku can be released with some bugs and warts.

1 Like

…all over the place fixing and improving things in the project. Look at the commits.

Do you think that somehow with putting a label “R1” on a release we’re all going to somehow get full-blown commercial support for this thing? What do you think is going to realistically happen?

6 Likes

No. I have never stated such a thing. R1 is not just a label, it is a stable platform.

It will attract users and some of them will start to develop on or for Haiku, improving the system and its ecosystem which will further attract users and the cycle continues.

Maybe this means all the tickets marked as blocker/critical?

Custom Query – Haiku → view tickets

Please do explain further how having R1 of a relatively niche operating system would attract users and developers, especially if it still doesn’t work on their computers due to unsupported hardware,

2 Likes

I am so sorry, your question just hit me that I have been wrong all the time. Never releasing a stable system and continuing to break functionality will attract users, and developers wants to write software that constantly breaks. That just makes sense!

Haiku will always have unsupported hardware because it is a moving target. That is an unsolvable problem. It can be minimized but that requires more developers. And Haiku will attract more developers by never releasing a final stable release that will constantly break because of new functionality that is not compatible with existing drivers.

1 Like

None of the changes required there require the BeOS source code.

Rewriting the Be Book would be cheaper than buying the licence for it.

You can’t rewrite the BeBook because they have the license.

Anyone can write API documentation for anyones API.

Sorry but you are not standing on the ground of reality -
You - and some other member here - wants to force their vision and imagination of an imaginary Haiku to the real existing Haiku … Haiku which is a project actually.

Haiku is a project … not a startup !..
The difference is that :
there are no financial investors of the market here but faithful users and believers who are capable to donate

→ with their money – Haiku users (and maybe devs also)
→ with their work (coding/docs writing/ticket handling) – Haiku and app developers
→ with their translation activities – both groups (especially as all devs also users of Haiku as well)

this project.

You want to haul Haiku up for something that’s not in its area. It was not funded as a startup to be finally a product or a successful enterprise.

It was founded – by founders – for not letting the essence of their beloved BeOS go into waste or fade away. They wanted to create an alternative for the future and also they had put a solid base for an effort to re-create it on an open source basis. They were not targeted to sell a product or lead in to the market. They just wanted to keep and share with others who would use it as well.
Moreover the project had evolved - mostly on x86 and x86_64 - so now it is far more capable in HW/SW support than BeOS was…

This way very false if some of you still try to set up the Haiku project as it is stil some remaining of an old legacy OS blablabla … what we know very well it is just a simple lie, a misstatement or lack of real knowledge of today Haiku.
We - others here – we feel very sorry for you as you are
not fully satisfied
or
not satisfied at all
as how Haiku are now … but we use it as we can do and for that it is already capable now.

There are some of us who are capable to evolve/fix Haiku itself and/or programs/applications running on it.
Most of us relates to each others with respect an patience - respecting their personality and knowledge and efforts they can do put in the Haiku project

We expect that you are all adults - means you can make decisions and then can leave with it. I beg for pardon for teenager users/coders here.

This way were offered if you are not satisfied

→ help in Haiku project with above detailed supporting activities

→ create an own version

→ or not use it … if its usage as is or slowness of its progress makes frustration in you.

On progress I mean anything that usually cause disturbace in the members here who compose such urging critics.

We can identify them as always debates but never show up some real example and/or as really doing somethingbut talk
(ok exactly write the stuff 'cause it’s a forum - you all know what/how I mean).

If you are adults it should not hurt you as these offers are honorable and not done for insulting / hurting you but these are the reasonable choices.

So please See Haiku as it is - a successful project. Not a product.

Especially not for everyone. Many people use their system what they use as they do not want to learn new - they just want to use what they know well and can use/manage.
They won’t use it Haiku - anyhow you propagate the opposite –
just about the existence of a mentioned missing service/program should added/ported and also a plus target HW platforn supported finally. They just want the OS itself as well to
look like and work like what they use actually.
Against you – they do not like or hate OS or computer systems - they just use it : they will remain on Windows , macOS, Linux anything … even on old computers, or unsupported OSes … just because they want to use it as they can handle and they are comfortable there.
Haiku would be a new place – where they must learn again - even the ported software, even the available service, etc.

Otherwise - if you want to continue your empty debates …

… it is better if rather all of you put together your efforts …

and start an own Haiku as a startup and finally step up as role models …
executing your dreams … there.
Then expect what you can expect from such phenomenon you haul the Haiku project up for in long essays for devs.

2 Likes

I find it ironic that you wrote a massive post telling me I should not ventilate my criticism in a post that is criticism against me. That is the definition of hypocrisy.

“All animals are equal but some animals are more equal than others.”

2 Likes

Then enjoy it, sir, I mean your finding and intellectual superiority ( if any ).

I wrote everything that I wanted. Any other supplemental is meaningless, indeed -