11 comments

[ 46.7 ms ] story [ 434 ms ] thread
Yes, it is an ad for Pharo, but I think it is nice to hear some success stories for technologies that always felt like they deserved better (like Smalltalk)
I have a headache from looking at the screenshot. Don't you think the UX could be a bit more streamlined?
I love that screenshot. Personally I really dislike the hot trend in UX to removing information in order to make the display look "cleaner."

For serious work, like investing, I want my software to use all my screen real estate and display as much information as is reasonably possible.

As you say, it's largely the difference between serious work - i.e. "expert" tasks - and other things tech is used for. To call it a "hot trend" seems to overlook the reality that humans use technology for a lot more nowadays than just cognitively heavy work.

Even when the work itself is cognitively heavy, it is sometimes imperative that the cognitive load of the UI is low, since the user is actually using most of their cognition outside the computer screen: In the actual world with which they are interacting.

If you were at a doctor's office, would you rather have the doctor focusing their attention on listening to you or on complex data on the screen? - Possibly both, depends on the situation. But if the UI for data entry there demands heavy cognitive load, there is probably a cost for how present the doctor can be for listening and observing their patient.

I thought Smalltalk did native UI, but not so much web stuff? Is this that Seaside framework they talk about?
Pharo has it's own UI, but can also run native OS UI windows (this feature is being improved). What you are seeing in the screenshot is indeed a web interface and a Seaside application appears to be hosting it, according to the description
Yes, this is done with Seaside web framework. We also use Bootstrap, Ajax almost everywhere, JQuery, etc. Obviously we also use several JS libs like Highcharts, Datatables, CodeMirror, TinyMCE, etc.
We're just doing ads now?
I wonder why they didn't use moose[1]; I guess it probably started development before it.

[1]: http://www.moosetechnology.org/

The main reason is because Quuve is a web platform while Moose is desktop-like. But yes, Quuve (with a different name and even without a UI) was started several years ago, probably before Moose.