4 ms·
Yep, all the native toolkits failed, that's worthy of ranting about, but that is not what OP was doing.
by nilliams 10y ago
Yep, all the native toolkits failed, that's worthy of ranting about, but that is not what OP was doing.
- m_fayer 10y agoThe only native toolkit I've ever tried that I thought could compete with web is wpf. It was slow and cludgy but way ahead of its time, and the web is only now starting to approach its power.
- sixbrx 10y agoI think WPF is nice but has actually fallen behind a bit on binding vs. some of the web toolkits like React/Redux, Angular 2, Ember. It's been a while since I messed with it, but MVVM didn't work so well for some kinds of things, which seemed to be why for example selected items property is often not a dependency property of MS supplied widgets (so can't be participate in binding). For example see http://stackoverflow.com/questions/22868445/wpf-binding-selecteditems-in-mvvm http://stackoverflow.com/questions/22868445/wpf-binding-sele... (from what I remember this accepted solution also has a subtle bug of double notification (or was it lack of notification on one side?)).
- mwcampbell 10y agoPerhaps WPF was the Electron of its time, in terms of being a resource hog. I remember how one particular WPF-based application hastened the obsolescence of my brother's laptop some years ago. [1] [1]: https://news.ycombinator.com/item?id=8444494 https://news.ycombinator.com/item?id=8444494
- ivm 10y agoI can't see how Cocoa failed at anything.
- nilliams 10y ago> I can't see how Cocoa failed at anything. Will my Cocoa app run on Windows, Linux and the web? (A well-designed web app built with Electron will). Why should any company that wants their product to be widely available invest in Cocoa developers?
- ivm 10y agoWhy should it? It focuses on its platform and does it well. I prefer native Mac apps to cross-platform ones. Serious companies should build native apps and keep UX guidelines of each platform in mind.