New challenge: build your machines for low cost from commodity hardware, rent your machines out to millions of customers and never have a single customer have > 1% of the hardware they land on fail.
Perhaps if HIV was endlessly highlighted by government and the media as a major problem in Sweden your analogy might have made some sense. In my opinion your post exemplifies the antithesis of a decent argument or even legitimate criticism.
If you look at stackoverflow surveys you'll notice that those using Scala are amongst the happiest users of any language and are very willing to continue using it. It's growing slowly but steadily and Spark is also driving adoption. With some exceptions most criticism seems to be coming from those who haven't had much exposure to scala and trot out the same tired old material time and again. Once you grok scala it makes more sense. It's a bit like complaining that Mandarin is hard to understand if you are English. It takes time to learn but it's worth it if you stick it out.
Thanks for the insight. I never really thought of that aspect. Over here I'm far more likely to collide with a corolla or vw polo than a giant Jeep etc.
A jetta would barely fit into my garage. If a "regular" pickup can swallow a jetta does that mean I can expect a "large" pickup to be bigger than my entire 5 bedroom house?
Thats quite a fascinating difference in culture/preference. Most people I know think Jettas are "too big" unless you have a family of 5 and need the extra space. Don't people find cars even bigger than that awkward to park in crowded parking lots?
The American variant of the Jetta was recently a stripped down cheapened version compared to the jettas sold elsewhere.They even removed the multilink rear suspension for the US model.
The reaction from some reminds me that some Java programmers will always resist change. Java's current feature set is the one true way (tm) and any features other languages have are bad, that is until they are officially added to Java and are then suddenly considered part of the one true way (tm) and further evidence of the language designers' wisdom.
It will be caught as a compiler error. Since you would typically have the method signature declare that it returns the most general type it should be a non-issue. It's really no different from breaking code today by changing a method signature in an API.
val is a much better idea. Final is longer to type, in many cases as long as just declaring the type. We should be encouraging immutability not discouraging it by making it more verbose than necessary.
Lombok has always been a hacky set of language extentions. It says a lot about the need for more language features in Java that developers have been willing to resort to using it. Adding val and var to Java will be a big step forward.