I'm submitting the website because I'm quite unhappy with how much performance-requiring scroll hijacking they decided to pack into that website. To copy over my Tweets:

"Apple Music website: If you're gonna hijack the scroll and do cool things, then don't pack so much performance-requiring stuff in the page.

"My CPU fan becomes hot when I scroll on http://www.apple.com/music/ on a NEWEST/BEST-CPU rMBP 13" on NEWEST SAFARI. I see 10fps. @AppleMusic

"I should try hard not to make an app/webpage assuming all users have a high-end machine with a nice GPU. That's doing less by doing too much"

Nice.

Also, one might simply outperform him/herself in HTML/JS than in other languages. Can't blame that...

This. Plus, sure, WWW was probably meant for sharing content, but HTML/JS is a front-end standard not necessarily tied with WWW.

I sense a connection, for example, between Rust's `fn foo<T>() -> Result<T, E>` and Java's `void foo<T, E>() throws E` (this might be incorrect Java syntax). I'm not entirely confident though.

I find Java's checked exception similar to Option type, because they are all part of the function's type. You cannot pass alone without checking the possible failure case.

I'd say that one possible solution is to not use `this` at all. Same goes for `new` for that matter.