Linked by Thom Holwerda on Mon 17th Aug 2009 09:34 UTC, submitted by moochris
BeOS & Derivatives I had been following the mailing list for the Haiku project the past week with growing interest. The topic of discussion? Why, the alpha release, of course! What needs to be done, who needs to prepare what, and most importantly, what schedule are they going to settle on? Well, after numerous insightful back-and-forths, the community has settled on a schedule.
Thread beginning with comment 379014
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Good and bad
by aldeck on Mon 17th Aug 2009 13:05 UTC in reply to "Good and bad"
aldeck
Member since:
2006-12-07

I'm a longtime BeOS user and this is a milestone I've been looking forward to for a long, long time.

Unfortunately, I have a few problems with the Haiku OS and the project itself that needs to be addressed.

Code base
---------
The quality of the code base leaves a lot to be desired, and this of course trickles all the way up to the user.


No hard feelings, but i find it a bit severe from you to make such assumption on the "quality of the code base" just because you stumbled across a few bugs on your hardware ;)
A lot of attention is made over quality and every commits is reviewed by several people, and quite stricly. I'm not even sure what you mean by quality, but i bet that it's a lot higher than the original closed source BeOS.

For instance, the release from last week 1) didn't boot on my SMP machine (so I boot in non-smp mode), 2) didn't work with the my nvidia card (so I switched), 3) eventually corrupted my hard drive (which, fortunately, is only for testing.)


In fact, there is no "release from last week", because there hasn't been any release yet. Don't take me wrong, thanks a lot for testing and reporting bugs, but by trying the nighlties, you're essentially testing a work in progress code. That's why there's gonna be a code freeze before release. I'm using Haiku for developing Haiku for several months now on a recent quad core system and never had any serious problems.
Btw, concerning your hard drive corruption, i doubt the whole disk was corrupted, i suppose it was just your Haiku partition.

While Haiku isn't a target for nasty hackers yet, it's bound to be if it gains widespread usage. The network stack looks completely unaudited with respect to security, and I suspect a lot of the other subsystems suffers in similar ways.


Security is a problem that will be taken seriously, but there are other priorities now (and a limited work force).

Fixing these things late is painful, so please start working on this early!


Well, not doing it now doesn't mean we don't think about it, and we try to prepare for it to the best we can.


Project and focus
-----------------
There's too much focus on icons, web pages and sugar. I couldn't care less about these things right now. I know that in an open source project, people tend to work on what they want to, but some management is always possible in order to direct focus. And that focus should be code auditing, and making sure stability and security issues are being worked on.


I think you're exagerating a bit, i've been in bug fixing mode for about a year now, and several bugs are fixed every day. Non system devs focus on their area of expertise and work hard on the site and other important parts of a release.

In short, I don't think an Alpha release is the right thing to do now. There's just too many issues.


It has been discussed in large, and most of the current user/tester base have very little problems on their hardware, so the only way to fix the remaining bugs is to start releasing the baby ;)

That said, I really wish Haiku all the luck in the future!


Thanks, for you encouragements!

Reply Parent Score: 3

RE[2]: Good and bad
by WendelFree on Mon 17th Aug 2009 13:28 in reply to "RE: Good and bad"
WendelFree Member since:
2009-08-17

No hard feelings, but i find it a bit severe from you to make such assumption on the "quality of the code base" just because you stumbled across a few bugs on your hardware ;)



Why do you assume I assumed? I have actually studied and hacked on the Haiku code (mostly interested because I had intimate knowledge of the NewOS code base.)

And overall, the code quality isn't impressive. That doesn't mean it can't improve. It just means it has to be a priority.

I have already touched the security issue. Another issue for me has been SMP support (not just last weeks build - I have tried a lot of builds over time), and I have a rough idea why. The locking isn't always done properly, and the code base mostly ignores read reorderings that will bite you increasingly on newer CPU's (that's right, Intel/AMD cpu's actually does reorderings these days - so does your compiler...)

Edited 2009-08-17 13:31 UTC

Reply Parent Score: 1

RE[3]: Good and bad
by anevilyak on Mon 17th Aug 2009 14:30 in reply to "RE[2]: Good and bad"
anevilyak Member since:
2005-09-14


Why do you assume I assumed? I have actually studied and hacked on the Haiku code (mostly interested because I had intimate knowledge of the NewOS code base.)


Because you're assuming that the behavior you're seeing holds true for everyone else, which is very much not the case.

Reply Parent Score: 2

RE[3]: Good and bad
by mmu_man on Mon 17th Aug 2009 14:35 in reply to "RE[2]: Good and bad"
mmu_man Member since:
2006-09-30

As for bugs, here Ubuntu has issues with my ASUS laptop, but mostly due to highly broken ACPI table. And ZETA couldn't boot until I worked around what seemed to be a bug in the chipset. The fact an OS doesn't boot on some machines by no mean imply anything about its quality.

As for the rest, we do accept patches ;)
At least the overall code quality of Haiku is quite higher than that of the original for what I've come to see.

Reply Parent Score: 5

RE[3]: Good and bad
by axeld on Thu 20th Aug 2009 12:12 in reply to "RE[2]: Good and bad"
axeld Member since:
2005-07-07

WendelFree wrote:

Why do you assume I assumed? I have actually studied and hacked on the Haiku code (mostly interested because I had intimate knowledge of the NewOS code base.)

And overall, the code quality isn't impressive. That doesn't mean it can't improve. It just means it has to be a priority.

I have already touched the security issue. Another issue for me has been SMP support (not just last weeks build - I have tried a lot of builds over time), and I have a rough idea why. The locking isn't always done properly, ...


Based on your statements, I can only assume that you have no clue what you are talking about.

If you think code quality is poor, you have no idea what code quality actually is about.

If you have found bugs, please report them properly (none of your examples has been reported as a bug so far), or provide patches to fix them.

Until then, please go trolling some place else.

Reply Parent Score: 1