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 379016
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Good and bad
by WendelFree on Mon 17th Aug 2009 13:28 UTC 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[4]: Good and bad
by WendelFree on Mon 17th Aug 2009 15:10 in reply to "RE[3]: Good and bad"
WendelFree Member since:
2009-08-17

"
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.
"

AGAIN: I don't assume anything. I base my assertions on knowledge about the code, not merely the three examples of problems I gave.

I know it hurts to hear that the project you work on has problems, but I do this with the best intension.

In fact, I'm preparing a patch for a bug in the PCNet32 driver as we speak ;)

Reply Parent Score: 1

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