On November 30, 2016, at 4:03 PM, kallisti5 <kallisti5@xxxxxxxxxxx> wrote:On 2016-11-30 19:13, Dennis Catt wrote:
Now on to the bigger elephant...
I personally still *really* want to see R1 to be x86 gcc4h (cough
gcc5h).
I think we missed the gcc2h boat years ago.
gcc2h in 2006 made sense.
gcc2h in 2016 makes 0 sense.
The list of software that even compiles on gcc2 is shrinking rapidly...
why are we doing this to ourselves?
gcc4h (gcc5h now) means you can run BeOS apps, and have a native modern
compiler. The downside is users
won't be able to run BeOS replicants, drivers, or screensavers on R1.
At this point in time, I can't think of a single "must have 1999 BeOS
replicant" (that isn't open sourced).
There may be folks out there however i'm not thinking of.
So once again, why are we doing this to ourselves?
Well I think that Haiku A4 should remain available until B1 is made
available. We definitely need to do comparison testing to ensure B1
will perform as well as A4 from a stability, performance and
reliability perspective.
What's the deal with replicants, drivers and screensavers not working
with newer GCC versions? Just curious.