Yeah, but you can purchase open headphones with which to listen to the radio (or music) while you bike. The 'open' part is important as you can still hear your surroundings with those, while you can't with 'closed' headphones and it's dangerous to bike deaf. I recommend the Jabra Sport.

1. 1. Really? You don't know how to do html/css without javascript? Your SEO must be shit, m8.
2. 2. All those 'rich' libraries are great until they don't work on IE8 or Chrome 37.0.20341. I especially love when stuff that worked fine years ago is broken today because browser updates changed the internal perfomance characteristics of the javascript vm. Simply put, doing too much on the client puts you at the mercy of client configuration changes which you have no control over.
3. 3. Libraries, that was your argument in #2 wasn't it? Compare libraries available to Java vs Javascript on the server side. Best tool for the job, right? Sounds like you found yourself a golden hammer.
4. 4. Can you really? How do you replicate the declaritive html5 form validation on the server? And is it really a good idea sharing your validation code, bugs and all, with the client? Sounds like a major security problem to me.
5. 5. Let's see how your sorting goes on a table with a million rows client side.. if you're batshit crazy enough to even try that. Most of what you mentioned should and generally does get written in SQL, not JS.
6. 6. lol, now that's just bait

Performance... you're funny. Tell me about your performance when your server falls over with memory problems and you don't have anything like visualvm to figure out why. Don't get me wrong, Java sucks in its own special ways, but I'd never choose Javascript as my primary language.