Here are a few big ones: 1. Abstractions that make sense, that are not built up from hacks, but are core to the platform itself. That is my number one peeve ab

Here are a few big ones: 1. Abstractions that make sense, that are not built up from hacks, but are core to the platform itself. That is my number one peeve about the web. Like I said in my original post, I want to specify "grid columns=3" instead of "div div div div div". 2. Control. When I build a native app, I have several orders of magnitude more control over the resulting product. Compare to the web and being at the mercy of browser manufacturers. I can access memory, files, TCP, UDP, ICMP. I don't have to break my program up into front-end + server if I don't want to. I don't have to use shims to get rounded corners or drop shadows. I can make a program that runs in your "tray" and receives push notifications without having to setup some complicated server-sided hackery to faux-push to the browser. I can make the computer do whatever my user wants, but not only that - I can do it with ease because I'm in control. 3. Choice of programming language. With native, I have a number of viable choices. (I don't care that anybody else thinks Javascript is great. Relatively, it's not...and besides...I want a choice. I want control! I am a solid Js programmer (was doing it 15 years ago and I haven't let it stagnate - I recently ported Node.js core module system to a completely different, non-v8 engine.) 4. Modularity (an important instance of "Abstractions that make sense"). Most native environments allow the developer to easily modularize commonly used artifacts (code, UI components, images, etc) without sacrificing performance. Compare to the web where it's a real PITA to make anything modular CSS, HTML or Javascript without resorting to using other tools that "transpile" down to CSS, HTML or Javascript - at which point I'm not using the web platform anymore, I'm using something else.