Haikuware News & Blogs
Spread your news, software reviews, comments, & ideas about Haiku!
« A Picture is worth a thousand words
mmlr's Coding Frenzy »
A Picture is worth a thousand words
mmlr's Coding Frenzy


Hits: 516
Trackbacks
Trackback URL for this blog entry

Comments
Let's start with the first poll. The wording here was pretty bad I think (and that's probably due to the lack of native-english speaking individuals who produced it).
I think the question should perhaps have been:
"Should Haiku also release GCC4-Only builds?"
Which may seem similar, but it makes all the difference I think. The way it was phrased seems to ask: "Should Haiku only release GCC4 builds?". Was that really the intent of the question? Because that basically suggests throwing out BeOS binary compatibility completely if you answer "Yes".
The second question is even stranger... as it provides a 3rd answer which is totally unrelated to the question.
The answers should have been yes or no. "Sometimes" doesn't matter - and what does that even have to do with GCC4? A BeOS app could never be built with GCC4, and a Haiku app built with GCC2 isn't necessarily BeOS compatible. It seemed like a very loaded question and a bit biased.
In any case, I didn't vote on either because I felt the questions were poorly thought out and misleading to the poll-takers.
FWIW, I do usually build GCC4-only images for my Haiku testing anyway - as I hardly ever require BeOS binary-compatibility... If I had a choice, I would probably recompile all the software I used in GCC4 anyway (assuming source was available)... I don't mind if the API/ABI changes in the future.
Aha, so perhaps I did misunderstand the intent of the poll :)
As I said, I personally don't need the legacy support either... but I can understand the desire for it.
I suspect that once the new PackageFS package management solution is fleshed out some more, (properly packaged) Haiku apps will coexist more happily with legacy BeOS apps. Right now, the way the lib directories are laid out makes it pretty painful I believe.
RSS feed for comments to this post