@the_leander
Thanks for the BeOS/Haiku information. I liked Haiku before, but now I have even more reason to like it!
@Piru
Piru wrote:
No
The reasons these topics tend to go around and around is useless answers like this. Ok, you say no to CAOS functions, I say why? You have to explain your point of view for me to take it seriously.
@bloodline
Your reaction to the question is far more interesting than either my question or Hans's answer could ever be!
I was interested in what experience Hans had, so that I could answer his questions better, perhaps he has experince in VxWorks... I don't know, but his questions were not those of someone who has spent many a bored evening messing around with an Assembler trying to get stuff to work...
You rection though, immediately makes me think there is far more to this than you are letting on, and not a good way. Someone is bullsh1ting us here!
Why would you believe someone is bullsh1tting you? Bloodline, from conversations I've had with you in the past I know you can be a helpful guy, but let's face it, you were not going to help anyone by asking if Hans_ had ever programmed for AmigaOS before (comments like that just make you seem like your looking to put people down, though you may not have meant it this way). If you wanted to him see your point of view you would have given him an example of why his ideas wouldn't work with AmigaOS, just like you had helpfully done when I was talking up MP stuff.
bloodline wrote:
Bug fixing a library that is not native to the Amiga is hardly a way to learn about the internals of AmigaOS.
I don't claim to be Hans' biographer, I was just giving you an example of Amiga programming he has done.
It couldn't be finished. It wasn't possible to get it done in the time frame/budget that Commodore had, to get the Amiga out in time. If they had stuck with it and the project had rolled on for 2 more years... too much money would have been spent, and every other computer company would have had a chance to make something better. The Amiga would have failed before it even left the stable.
Granted, it is quicker to adapt an existing OS like Tripos than start from scratch. If the CAOS developers hadn't wasted time during the development process they may have had time to get it done for the A1000 launch, who knows. We are not working to those same time restrictions, and I doubt there would be much resistance in the Amiga community to the idea of resuscitating CAOS. So exec is the same in CAOS and AmigaOS, and other functions are similar, we don't have to throw everything away to get the job done do we?
bloodline wrote:
99% of all free software is POSIX, and a new operating system needs free software to be in any way useful.
How hard is it to port a POSIX compatible app to a non-POSIX OS, in terms of libraries missing and other needed infrastructure?
bloodline wrote:
AmigaOS is what it is. If you want to make a new OS go right ahead. But I like our little dinosaur.
I think this is the core of why these discussions get you (and others) worked up. In my opinion we are not defiling the memories of AmigaOS by discussing new ways we can take our OS's. The classic AmigaOS architecture will always be what it is, but new Amiga compatible OS's can take the OS in new and interesting directions. Why not look at what all of those possible directions are? You don't have to hate the new to preserve the fondness for the old.
@Hans_
Hans_ wrote:
Correction, I'm extending MiniGL. I have worked on other stuff, but none of that is released yet (and some of it is discontinued).
Thanks for the correction.
Hans_ wrote:
Like it or not POSIX is now an official standard and a lot of code has been written that uses it. Any new system that ignores POSIX is doomed.
I'd still personally resist a 'one size fits all' computing world even if there were significant drawbacks. Got to give the world a true alternative to POSIX one day IMO.