Hmm, I just don't like JS. It feels to me rather fragile. Alone == and === let ring my alarm bells. And the most examples you can find on the web for JavaScript

Hmm, I just don't like JS. It feels to me rather fragile. Alone == and === let ring my alarm bells. And the most examples you can find on the web for JavaScript are just a messy hell. Abuse of closures (are those real closures in JS anyway?) leads to spaghetti code. And most of the major frameworks tend to support this "paradigm". > theoretical develop once, deploy on the most important platforms After all those years that's something I won't buy :) Today's html documents are still filled with "ifdefs" for different MS browsers and special css selectors for every major html rendering engine. Testing a webapp for compatibility with common browser/os combinations must be hell. But there are other reasons why I tend to avoid webdev: There are considerations like security. If I deploy a desktop app and one user gets hacked because I messed up then this one user got hacked. Depending on the bug hacking more users tends to be non trivial. If on the other hand I have a glitch in my web app suddenly all my customers' data is in danger because all the juicy targets sit in one place waiting to be mass-hacked by a script. I hope that webapp shops hire a full time security guy for their apps but ... who am I kidding ... most of the apps probably run on unsecured boxes and have a dozen of (forgotten) developer backdoors in them. Security is just a huge and complex issue I wouldn't want to deal with. (And couldn't to be honest.)