Regarding Beta 5

Man,
from this listing more programs are intensively used by other Haiku users !.. :rofl: :rofl: :rofl: :rofl: :rofl: :rofl: :rofl: :rofl: :rofl: :rofl: :rofl: :rofl: :rofl: :rofl: :rofl: :rofl: :rofl: :rofl:

Please, be calm.

1 Like

I hope Haiku devs who are called/related have such humor sense like me
and reading this opinion
- wanna-say recommendation (LOL) -
and they are laughing loud fluttering their knees at this time reading this.

Right, I’m done for today.

I like how the Haiku project has followed the same “we’ll ship it when it’s ready” attitude that has made the Debian project successful. People trust the stability and reliability of Debian because of their attitude to how they manage their releases. It speaks volumes on software quality. Those shepherding the Haiku project are doing the right thing. I get it, we all can’t wait until R1 stable hits the shelf, but the best things come to those who wait IMHO. I think a lot of folks thought Haiku (previously OpenBeOS) wouldn’t make it this far. It has been an amazing story to see unfold.

4 Likes

user said “more function, we will forget the risk of unstable”

developer said “more stable will bring more function”.

time said " there is a cross point in the future".

and, the day, R1 will be true.

4 Likes

Debian has gotten quite good at hitting a two year release cycle, like ubuntu lts. i think this is a reasonable cycle for a stable project like debian.
For a project like haiku, that is developing i think a cycle of about a year makes sense. releases, even beta releases are a lot of work, but they also show the project to the public, i would love to have a beta 5 soon.

2 Likes

A Haiku Beta 5 with updated FFmpeg 6 would be a good step!

1 Like

i see what you did there :wink:

If only…

We could move WebPositive out of Haiku sources, sure. But when I work on it (or any other app, really), a lot of times, I end up having to fix bugs in Haiku.

But who will do it? If it’s the same people, nothing is won. We just have more “paperwork” to do: managing separate releases of these apps, separate bugtrackers, packaging at haikuports, and then telling people “oh you want to edit text? there’s an app for that”. “you want to play an MP3? there’s an app for that”. And installing Haiku moves from a 3 click process to a week of hunting the right app for each thing.

We have enough competition from other operating systems and distributions already. I don’t think we need to add inside competition withing Haiku between different app ecosystems. We can instead have cooperation between developers to fix and improve the existing apps, or even replace them. For example, Genio is making a lot of progress, and we can consider integrating it in the next release as a replacement for Pe.

Of the apps you listed, some aren’t even included in the Haiku image (musiccollection, text_search, TV very recently), some are not maintained by the Haiku team but just repackaged (Pe) and could easily be replaced, and other ones don’t really have any alternatives. And for some of them, removing them is a bad idea because we want to ship a usable system, including a text editor, a web browser, etc. Not just a kernel and an empty desktop.

5 Likes

How is it a replacement for Pe? wouldn’t that be Koder?

Anyway, I think it’s a good thing to separate Haiku as an OS (with a minimal amount of only the most necessary applications) and Haiku distribution (Haiku with additional applications). Why?

  1. System development requires a much higher level of programmer qualification than distribution production.
  2. Other people (not even programmers, or novice programmers, or those who prefer it) could do the simpler work related to the production and maintenance of the distribution.
  3. There could be several specialized distributions for different purposes (perhaps even paid ones).


Among other things, it was a successful BeOS business model (which was not fully realized and was abandoned by Be Company before it even took off): The essence of the model:
Assemble the system you need by adding what you need to the base of the system, for free.
If you want a ready-made OS with specialized programs and additional support, pay.

I dont think The maintenance for the preinstalled Applications, appart from webpositive is very big, i think codycam and tv could be dropped, at least as long as there is no usable webcam support, but this would not make the development easier, so why change it

As others have said here, this would just replicate the Linux distribution model and dilute the more complete Haiku desktop experience. For desktop OSes, they are supposed to come with a bunch of apps to get most people started. Even in the Linux ecosystem, desktop-focused distributions do the same thing.

If you think that maintenance of a theoretical core Haiku distribution can be done by non-progranmers and novice programmers, then what do you think is stopping them from helping with that right now on Haiku?

1 Like

As always, in such situations: authoritarianism, monopoly, too many restrictions, too complicated to start.

The ecosystem works, and that’s what matters.

The Linux ecosystem is a mess.

3 Likes

Why are you bashing linux here on the haiku forum?
The linux developers wont see it, for haiku developers it is not relevant.

Offtopic:
Btw, it has gotten much easier, as long as you use a mainstream distro with systemd and flatpak support.

Between the ongoing bikeshedding fiasco in Wayland Protocols, the re-emergence of desktop-exclusive apps straight out of the pre-X days, and more DEs planning to undergo rewrites (e.g. COSMIC, Budgie, etc.) away from a shared tech stack (GTK), I wouldn’t exactly say that the Linux desktop ecosystem is currently working well or will assuredly continue to in the foreseeable future. There’s more, but it’ll probably derail this thread too much.

Besides, Haiku’s ecosystem is reliant on having a unified desktop platform to build upon. Being able to know exactly what’s available on every Haiku install greatly simplifies support and development. No need to have containerised package formats, multiple package formats, library runtimes, etc. There is also no need to consider differences in supported features between DEs (an emerging problem with the Wayland transition), package versions available in repos, or fallback to providing support through terminal commands to bypass people using different desktops.

Look, I like Linux enough to use it as a daily driver. However it does have a lot of issues as a desktop platform. Haiku’s focus on providing a complete and unified desktop system avoids many of the structural problems Linux has as a desktop platform, making it closer to Windows and macOS with regards to desktop cohesion.

1 Like

Comparing Linux and Haiku… Basically, there is nothing to compare here. Linux is a working system, with flaws, of course, but they are being worked on and progress is being made.

After all, from the user’s point of view, the most important thing in the operating system: it has to do the job.

If system do job good it is good system.

The benefits of system design and architecture, use of programming languages, licensing, and the like are secondary.