I think this is one of the things that Java really solved even though the actual implementation is a bit weird.

Being able to generate a war or jar as a released binary is something that would be cool to see in the ruby world.

I see this cited a lot, but honestly I would say the majority of jobs use Spring, and it has been that way for quite a while.

I don't believe this is true. I received these alerts this morning, but as my phone is only on vibrate it did not produce any audio.

I think if it's set to silent/vibrate, it won't generate audio on most phones.

But as I'm on-call for my organization, that's not an option.

I wouldn't say so. The original plan was to have the LCBO handle sales of marijuana as well.

The Liberal government that was drafting this plan lost the provincial election and the Conservative government scrapped that it.

So it nobody learned any lessons, we just had interesting timing with our election.

I'm not saying I disagree but for a lot of businesses (even one with relatively high traffic) it is not unheard of to deploy with almost no tuning of the GC (aside from setting a heap min / max of 2,4,8GB) and have no issues.

I'm sure this all depends on use-cases, but I'll chime in to agree. I work on web services that do high (not Google high, but you've-heard-of-it high) levels of traffic, we run on the JVM, and GC pauses are not something that cause us to lose any sleep using out-of-the-box settings + explicit heap min/max.

Try a Spring Boot app using Gradle as the build tool.

Weblogic and all those app servers were a product of a different time. They solve problems that are largely solved other ways now (you could argue for some of their features). Spring Boot ships the web server in the application which is more akin to Rails, node etc.

Maven itself is also showing its age (its 1.0 release was 2004). I won't say that most of the industry has moved to Gradle, because the truth is so many workflows and projects are using Maven that it will be around for a long time. The good thing is that other build tools like Gradle, SBT etc. interop with maven the package repo just fine.

There is nothing stopping you from developing Java in vim. Syntastic and other plugins will help though.

From what I recall, Java didn't switch because it didn't work. I think it switched because the green threads were built on what Solaris supported, and they moved to full OS threading to support Windows, Linux, Mac etc.

I think that was taken into account when the "try with resources" statements were added to Java.

As you said it would be nice if the languages could make these situations impossible.

I think its a bit of a chicken and egg problem because some language issues don't come to light until people are using it and it is too late.

Java 8 (and 9 more so) bring a lot of changes but more focused on core libraries than the language itself. Not as drastic as the changes JS has seen.

C++11 though is quite a bit different. Probably the biggest change being that raw pointers * for the most part should not be used anymore.

It is not a requirement for Java it is just standard practice.

Also Maven does not allow you to remove packages once they are pushed, I think that is what he meant by Java being unaffected.

npm also does not allow you to remove packages. read my comment more carefully.