Haiku x86_64 can’t build itself nowadays. An old revision can. Devs arguing over what direction Haiku should go in. R1 possibly never being reached admitted to. The ship is slowly tearing itself apart, because there is no captain to helm it in the storm.
Under Steve Jobs, Apple was a very focused machine (if not always 100% winning on everything). Without him (then and now), fracturing occurred.
We need one man to lead. To say, THIS is how we’re going to do things. Right or wrong, at least there is focus and purpose. Of course, I still believe, as I did many years ago, when Phipps was OFL (Our Fearless Leader) that the cart was before the horse, which is WHY we are where we’re at, today, but it is what it is.
I propose a way out of the mire. I propose extreme focus and a razor-sharp goal. But it comes at an extreme cost that few, if any, are willing to consider. The status quo will only cause further degradation. 20 yrs. between releases? How about NEVER? The goal of “BeOS R5” was a nice idea, but its growing more and more untenable, since it was passed, so long ago, nobody can even remember when it occurred. 32-bit apps in a 64-bit world? Pointless.
But open-source, for all its glory of available man-power, also has a glaring weakness. Lack of leadership, because everyone works for free and therefore say “I wanna do whatever I wanna do”. Not what NEEDS to be done, for the good of the project, but whatever makes the individual dev happy. “Cart before the horse”, as mentioned above. And now the cart and horse are so horribly tangled, it’s almost time to shoot the horse and dismantle the cart for firewood.
Was this end worth the journey to get here? Really?