Am 22.02.2012 02:03, schrieb Sean Collins:
Its like this, I could build and machine engines, I have done it for years, but given my limited personal resource "time" I find it easier to handle the engineering and farm out the machine work and assembly these days. Just a anecdote to imply that I understand the pride etc of having something you made yourself, but at the end of the day, if you can browse the web, or drive down the race track, the destination is sometimes more important then the journey.
Sometimes it is, sometimes it's not. There are plenty of projects out there where the destination seems to be more important than the journey and that's perfectly fine. After all, we need results and something to work with. However, it's not the point of Haiku to be build just like another Linux distribution, only with a less capable kernel and yet another API called Be API, similar to Qt only much less complete.
But let me tell you something about only putting together parts. The way Linux distributions work, they want this steering wheel and those brakes and this engine but with that exhaust pipe. But unlike a car (hopefully), software stacks don't necessarily fit together. And so when they want this steering wheel, it only works with another set of tires and including these certain brakes means they also have to include a second pair of wheels. And so what you get is a car which does drive, but somehow ended up with three different sets of tires, combined with two pairs of wheels, somehow made to work at the same time. But it works "good enough" and even looks pretty, since they managed to hide the cludges with paint.
But if we wanted that, we wouldn't work on Haiku. Doesn't mean the Haiku way doesn't come with its own set of problems, like for example that the car is still unreliable, doesn't work with all kind of gasoline and can only be driven on certain roads.
Best regards, -Stephan
