@Argosy

Quote:

Argosy wrote: @HenryCase Quote: If CommodoreUSA support AROS financially, I will take them seriously Hmmm... after carefuly thinking this over, I think they should just hire a dev team and develop AROS on their own + naturally they can still pay bounties for some of the work. The reason being here is that it is unlikely, in my opinion, after having read democles' comment about AROS64, that the AROS community would do the right thing and cut connections with OS 3.1 for a future AROS release. That would mean C=USA getting stuck with AROS as it is today and then we have just a another pretty much useless OS for anything other then retro fun. Which would be a damn shame

I can't speak for the AROS community as a whole, but I am an AROS fan, and have been someone who has opposed breaking the API when the matter has come up in the past.

My reluctance to support an API change is not due to anything more than wanting to finish the job with what we've got. AROS has become a useful system for many people, but there's still some work to do on getting it stable, specifically completing the ABI and API (and bug fixing). If it's abandoned now then we won't get anywhere fast, as we'll be constantly chasing the latest must have features.

Look at the plan for Haiku for an example of how to do it. First release is aimed at BeOS compatibility, but they have the Glass Elevator project for features that will go beyond the features that BeOS compatibility permits.

In other words, get to AROS v1, then work on the next evolution. I am not the only person in the AROS community that I've seen express these thoughts, though I also appreciate not everyone shares my view.

Last edited by HenryCase on 01-Sep-2010 at 02:50 PM.
Last edited by HenryCase on 01-Sep-2010 at 02:49 PM.