I 100% agree with Kas1e here. If OS4 doesn't do something then it's a dead duck that's just never going to progress. And since I do understand the sandboxing concept, even if not in detail, I'm all for it.
I've just sold my OS4 system. And I won't lie, one reason, but by no means all is that OS4 is just flaky as hell.
I'm not a long term user. I only had A1200 briefly back in the 90's when they came out and have only been into OS4 for about 12 years now, so I don't necessarily know all the gory details of what I should and should not do and trust me when I say, it's extremely easy for me to crash the system. Especially when I start to mess about with programming.
I'll be back to OS4 at some point, I'm sure, especially if I start to see movement in releases and improvements so anything that can move things forward is a plus in my eyes.
Amibench is as I understand it a Aros 68k distribution, similar to apolloos or my distribution, running in full emulation. The problem is not how fast it is but how good it integrates and how the feeling for the users is. Is it still feeling very much the same or not? Feelings are very important to retro users who we all are today in one way or the other.
So short... if you want to move forward you have to ditch 68k compatibility and the way 68k is currently integrated in but it will also feel different if you still use 68k apps.
it can be quite fast... and feel quite normal, if you don't go for a full emulator. A600GS / A1200GS - AmiBench is moving in that direction.
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
After I wrote the message below, I realised everything has been said already. I'll post it anyway.
I am using a lot of 68k software too.
WordWorth TurboPrint ArtEffect AREXX CubicIDE PageStream4 (Since PGS5 is buggy at least) To name a few.
What bothers me most is being stuck with a system where a single misbehaving program can bring the whole thing down. Then there's the nice hardware with multiple cores and being limited to just one.
The OS should move on. Then developers would also be more interested in it when better development tools are available, and this too seem to be related to the OS being stuck too much in the past.
AmigaOS 3 is being developed further, so there is the alternative with Vampires and other "68k" hardware.
All other OSes have moved forward; we should too. To me, it seems silly to have two parallel OS 3.x and 4.x, with the only difference that one does run natively on hardware that can only be supported partially, at half the speed.
To have fairly modern browsers, especially since a few of us in the thread want one, we need to move forward. And we need a 64bit os for modern browsers. I don't think there is a way around it. we might be able to to get along for limited amount of time, but sooner or later nobody will be able to to take webkit and make it run on 32bit.
I vote for moving forward, but I wish a better and faster e-uae was available. Judging from the explanations of kas1e, I think that is a good way forward. So count me in with kas1e and Andrea. and thanks to LiveForIt for cooking up some mystery better development tools.
it is about being API compatible but not binary compatibility. That finally means integrating 68k only by emulator. The advantage you can basically make changes to the OS without caring about breaking compatibility with 68k. That makes it possible to do currently a migration from 32bit to 64bit. But this of course comes with a price. You can as example not use original 68k libraries in the system like those needed for arexx. I think this is possible in amigaos because of petunia. There is a replacement for it but it is not fully compatible. You also must run emulation to use 68k. That is creating a different feeling at many users obviously.
So short... if you want to move forward you have to ditch 68k compatibility and the way 68k is currently integrated in but it will also feel different if you still use 68k apps.
I do not know if 68k integration like it is currently done in amigaos has still the same meaning as it had in the past. I know that at least in past 68k integration was a reason why people preferred one system to the other.
Now THAT is really satisfying... I like the mood, it makes me feel so - saturated! It also gives me the impression, that this is something really, really valuable to look at, here in my nightgown getting ready to voluntarily shut down my circuitry until the day tomorrow, where I have to perform dastardly feats against an unbeknownst enemy. I have to say, that is extraordinary! I am just waiting for everyone else to join in and have a caballesque (whatever that is).
Was about to record same kind of video (alfkil gives me test bins as well), but as Flynn was faster, i only can add that yea, speed is ok. Not slideshow or whatever, pretty ok. Of course can be a bit improved here and here, and a bit more integration with visuals and os4 design can not hurt, but hey hey, that pretty good.
That's fabulous! Now - for the devil within me: Could we have some music on top of that?? Not the slightest of what I'm after, so anything will do, just any music at all! Can you do that for me!? Oh the joys of laughter, wo-ho-ho, beyond the wild canyon where the roses grow....!
...And perhaps also tell me: How do people normally upload images in posts here?? I had to let go of my homepage service, so I am left with cloud storage, that doesn't play so well with the [img] function here.
You did an absolutely amazing job. We can all see everything loud and clear! Nothing is hidden, everything is written - in vast codes of orbital noise, beridden with fearless joy and laughter... Ho-ho-ho! Do the moose dance and join the quest for glory -
Well, I call parsimony, and the fact that I have done absolutely nothing to prevent the blue bar from going under. As a matter of fact I have followed the logic prepared by whomever took the liberty and do the jumble for the rumble of putting things in certain places in the window-holder factorization entities.
If, on the other hand, parsimony is not an option, I could also give the conceptual argument, that the lower part of the window is where the Qt specific status bars go in QMainWindow driven settings. So it would not be good value of visuality to put another bar there to puke on.
If it is good value to you to keep things straight up and running, I will do absolutely nothing about it. I think there should be an entry on this put in the documentation of the subject - not to clearly cut the differences involved, but rather to haunt you in your sleep, when you least want to see bars of blue turn golden in an abstained vision of corporeal nature in the hidden unknown.