Login

logo6


Haikuware News & Blogs

Spread your news, software reviews, comments, & ideas about Haiku!

Legacy Apps & GCC4 Poll Results

Karl vom Dorff
Karl vom Dorff
I'm a Haiku enthusiast, and try to help further Haiku any way I can!
User is currently offline
Jun 09 Latest News 4 Comments

poll1



poll2


Tags: Untagged
Hits: 516
0 votes

About the author

Karl vom Dorff

I'm a Haiku enthusiast, and try to help further Haiku any way I can!

Trackbacks

Trackback URL for this blog entry

Comments  

 
0 # Could have been betterumccullough 2011-06-16 22:08
I understand what the point of these two polls were, and I would have been interested in the results, but I have some serious problems with the way these were presented, which I think makes the result kind of wrong:

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.
 
 
0 # RE: Could have been better3dEyes 2011-06-16 23:05
In my opinion, Haiku should be only gcc4. This will solve many problems in porting applications today. Support gcc2 applications can be made optional. For example: installoptionalpackage gcc2support
 
 
0 # RE: RE: Could have been betterkarl 2011-06-17 07:02
I just wish the two could live happily together. Would a dual boot GCC2/4 image be useful for developers? Or how about both compilers included on a developer disk with a GUI in the preferences (that explains why there's two) to switch them? By putting that GUI in there, you'll make people aware that there's two compilers included (and a readme, maybe in the same fashion as the installer) which wouldn't necessarily be so obvious otherwise.
 
 
0 # RE: RE: Could have been betterumccullough 2011-06-17 13:06
Quoting 3dEyes:
In my opinion, Haiku should be only gcc4. This will solve many problems in porting applications today. Support gcc2 applications can be made optional. For example: installoptionalpackage gcc2support


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.
 


Please register to post comments

The Largest BeOS/Haiku Software Repository