3 ms·

I guess that was another hang up. What should you use? Why? When is it reasonable to use cutting edge vs seasoned libraries? Thanks for that, though. I’ll like

I guess that was another hang up. What should you use? Why? When is it reasonable to use cutting edge vs seasoned libraries? Thanks for that, though. I’ll likely give that a shot soon, because my current client loves the idea of MacOS apps. I like the idea of common code to rub on multiple platforms, but it seems like it’s too green.

jwells89 3y ago
I think that not just on macOS, but generally in desktop software, the older, more mature, more "boring" option is going to be best in the long run even if getting up and running is faster in newer stuff. Of course platform devs would like you to think otherwise because they want buy-in for their new frameworks, but buy-in is earned. New frameworks might eventually be great, but it's going to be a while before they're able to compete with the likes of frameworks such as AppKit, which have legacies stretching back 3+ decades. That's a lot of time to allow for refinement and better covering of common use cases. It's somewhat true on mobile, too, though to a lesser extent because mobile UI widgets don't need to be as functional, which makes it easier for new things to compete — for instance a table view with sortable, rearrangable columns and column headers is practically unheard of on mobile whereas it's a cornerstone widget on desktop. For user-facing platforms the web is the odd exception where it's somewhat the norm to jump for the latest trendy shiny thing on new projects.
duped 3y ago
It's not like Windows is any better, and Linux is kind of a free for all.