0) It's hard to explain to people that they need encryption, how it works, what it is. People think email is secure! The "envelope" iconography is very misleading - email is more like a postcard, delivered by a random selection of disreputable postmen.
This is incorrect at this point, I'd say it's more like a postcard pinned to a bulletin board in the hallway, with everyone passing being required to take whatever cards are going to where they are going, with the requirement that multiple copies be made and dropped at every corner on the trek. That's probably more accurate as an analogy of today's email situation. The implication being, obviously, that email is visible to everyone on the trip, and copies are made and kept.
As for the rest, there are ways around a lot of that, but we're not there yet. Your analysis of webmail is spot on, webmail as it lives today should die a very very quick death. The sooner, the better.
Maybe ask the government to grant snowden clemency?
Nah. Why exert the effort to click an online petition when it is so much easier to just bitch about how hopeless things are?
And yet you post as AC.....
JS failed on mobile....The browser has been evolving to reduce or eliminate the need for JS as much as possible.
When did either of those things happen? Wishful thinking?
You are serious? Your reading comprehension is that contemptible? Show me the wonderful set of JS apps for mobile. Anything in the top 100 for any of the 4 top smartphone OSes (yep, I'll even let you go down to Blackberry).
HTML5 - huge reduction in JS needs.
Oh, that[JS] failed a long time ago. Why people keep using it is beyond me. At least people learned to stop using it on mobile.
Because there's nothing better? At least CoffeeScript has fallen by the wayside.
Having been down the path of using JS on the server, I can unequivocally state "hell no". Debugging that crap is worse than debugging on a browser, where at least the toolset and use cases are somewhat limited. Try handling JS requests running against shared data. Oops, multi-threaded what? Node.js does not have a benefit with non-blocking IO, as that's been around in Java since Java6, and is now in its 3rd generation. It's unlikely JS will ever catch Java in performance, security, maintainability, nor just ease of use.
What's truly funny about your 1 sided viewpoint is that it's purely based on the browser. JS failed on mobile, completely, because it sucks so badly. The browser has been evolving to reduce or eliminate the need for JS as much as possible. (Have you even looked at HTML5?) New frameworks and "wrapping languages" keep popping up purporting to "fix JS", there's a hint, it's not because JS is great. So far everything has failed with the possible exception of jQuery, which actually has lasted and remained somewhat useful, primarily because it's a toolset that reduces the JS disaster to something manageable.
...Optimal Java runs only 3 times slower as C code...
Where on earth do you get this info? Java, depending upon the usage, can run faster than equivalent C code. If you're talking about micro-benchmarks, then I'd agree. Generally speaking, I don't write micro-benchmark type code. I agree with the rest of your sentiments however.
yah, but we trust google more than AT&T.
Out of the mouths of babes...
sometimes only comes prattling nonsense.
He has not acquired a fortune; the fortune has acquired him. -- Bion