@udoschneider @daboe01 The difference is not, imo, in the drawing model, but the code organization one, and the available UI controls. The others, excepting perhaps ExtJS, are focused on augmenting raw html/css, rather than providing a truly robust event management mechanism and controls to go with it. They all hit the wall eventually - at least for small teams.
Apple, of course, has unlimited resources to tweak and extend SproutCore. Most do not.
@daboe01 @udoschneider The phrase 'desktop calibre applications' has become a negative for myself. With the rise of Electron apps it makes me think first of something with a clumsy and incomplete user interface. As more of macOS's minor apps are converted to Catalyst or SwiftUI this is increasingly true of those too.
Cocoa excels in providing tools to create efficient user interfaces which don't get in the way of the task at hand, in my experience — and this should be our value proposition.
@enquora With the rise of Electron apps it makes me think first of something with a clumsy and incomplete user interface.
Funny that you mention Electron. From my point of view many Electron "Apps" rebuilt a lot of a more complex desktop-like UI behaviour on top of HTML/CSS ... and it still feels/look foreign. You could give it a Marketing "looks modern" spin though. However I'm not quite sure if using platform agnostic HTML/CSS to emulate a native UI running in Electron to provide a "native" app is actually worth the effort compared to using a native toolkit directly (e.g. Qt if you really want to be platform agnostic). This kind of reminds me of my Smalltalk times where (at least the commercial) Smalltalk dialects were drawing their complete UI on their own. Sometimes even with different themes for Win9x, Motif, CDE and so on. But back then at least the level of UI complexity was comparable/above what was given on the underlaying OSs. With Electrom you get the worst of all worlds IMHO .... maybe except for the "built with modern web technology" buzzword bingo and the (on first sight) better availibility of developers ...
@udoschneider Almost all organizations view software as a cost rather than an asset. The natural outcome is to hire fungible lowest-common denominator people to create/maintain software. Not a prescription for good outcomes. When Apple itself continues to promote design awards for what it considers to be outstanding UI examples, yet allows its own design teams to commit what amounts professional to malpractice (macOS Notifications and every Catalyst app and most SwiftUI ones they've created), it's a trend not likely to change.
We should concentrate on identifying and reaching those who view software as an asset.
UI/UX design is very difficult, and fundamental to software usability. It's a mistake to treat it as an afterthought. Our biggest asset is a three-decades tested UI implementation.