Re:Darling – MacOS translation layer for Linux
by simonh on Wednesday November 02, 2016 @04:01PM
(#12858712)
Microsoft tried this with RT, the web technology dev stack for Metro apps. Is that even still a thing?
On mobile web tech based apps are the ugly step-children compared to native apps. They've had their chance I'm afraid. I understand why they should be ruling the word in theory, but it just never works out in practice.
Re:Darling – MacOS translation layer for Linux
by nitrogen on Wednesday November 02, 2016 @03:56PM
(#12858674)
I don't understand all the downvotes for all of your comments. I have developed GUIs in Gtk, Qt, .Net, and Java+Swing, but I saw the writing on the wall and learned web dev. I really really hate writing GUIs in HTML (inferior tools, inferior performance), but that is where the wind is blowing.
Re:Darling – MacOS translation layer for Linux
by pjmlp on Wednesday November 02, 2016 @05:54PM
(#12859709)
There is plenty of money to be made in native GUIs, one just needs to search for the right customers.
I have been developing green field native applications in the last three years.
It has been a return to sanity after doing around 4 years web dev.
Qt, GTK, and other desktop techs are "weird" little tiny niche skills to acquire, and since desktop dev in general is lower priority these days they're going to be rare. HTML5+CSS+JS with a stack based on React or Ember will draw tons of dev talent.
For consistent look and feel the environment could standardize on a single set of CSS themes (maybe a fork of bootstrap) and a "recommended" UI toolkit (I'd recommend React). Use of other CSS or other UI toolkits is okay, but if you do you're strongly recommended to hold to the style guidelines.
Those style guidelines could in turn be informed by things like Atom, Visual Studio Code, Slack's desktop app, etc.