Reaction vs MUI (as what concerns the API)

[kolla]

Both suck immensely.

[kolla]

AWeb user interface is just plain horrible.

Well, you can turn it off and just create your own UI with MUI or whatever. Can one do that with OWB?

[kolla]

Reason why ClassAct/Reaction never really took off is they never understood what made MUI so popular.

MUI is nice, but it's also ridden with annoyances. just to name a few:
* Too bloody many options, why do I have to configure each and type of "box" or "list" or whatever individually for each and every class? Why is there no cascading of styles? "Apply this to all string input gadgets"
* No overview of which MUI apps that have individual settings, have to check this manually in env:mui/envarc:mui, and also (iirc), no way to set MUI settings for a certain app back to default settings (other than deleting the corresponding file in envarc:mui/env:mui
* No quality control of third party classes whatsoever, no official "approved" list, no warnings from the system when well known broken classes are called upon.
* Legal situation that only favours MorphOS.

[kolla]

The only remotely relevant argument that was given so far is about speed, but there's no benchmark to prove it, which means it may just be wishful thinking or propaganda fruits.

No, speed is not the big issue - memory consumption is.

I've been one of those who prefer ClassAct apps over MUI alternatives, simply becuase with CA options left my system with much more RAM free. Also, the development of CA at the time was much more open than that of MUI, the devs were all easily reachable online. Stuntzi was always away on some bicycle trip or whatever.

[kolla]

In practise it would rule out all MUI classes not maintained by the MorphOS team.

Yes, isn't that what you want?

"Nopeat syö hitaat". (Old Finnish saying.)

In this context, that saying makes no sense - MUI and MorphOS too are very much in the slow lane.

[kolla]

But pretty much after fast RAM expansion it becomes non-issue. It does not mean much when you have 4 MB fast. You always run out of chip ram first.

... when browsing the web, perhaps.

You make it sound as if web browsing is the only task you'd use the computer for, but then... why on earth bother with an amiga system in the first place?

And you do know that you can run Miami without _any_ GUI engine?

[kolla]

Now, where is that cool application I can run on my Amiga?

http://aminet.net/package/dev/misc/AWNP_2-54 and you're all set.

[kolla]

frankly I don´t know what snappshotting means in an Amiga application context

Snapshotting the window location and size.

[kolla]

Great, so I can install multifunction pipe on my Amiga 500. What now?

Now you pass data through that pipe, to build GUIs and do whatever you like.

[kolla]

So, it seems ClassAct is not much use at all.

Well, there's Grapevine IRC client and AmiFTP - the only native Amiga ftp client that grasps VMS servers.