You know you live in a clown world when memorizing nonsense makes one more employable than learning some front-end stuff to be a little more full-stacky.
228 karma · joined December 19, 2020
You know you live in a clown world when memorizing nonsense makes one more employable than learning some front-end stuff to be a little more full-stacky.
Borland Pascal already had reasonable static types, classes, pointers, modules with a public API, and blinding compilation speed in the early 90s. All the basic building blocks to grok. Golang seems to be the closest modern-day approximation.
A total of 1,053,829 people died in the Gulag not including labor colonies (https://en.wikipedia.org/wiki/Excess_mortality_in_the_Soviet...).
The Communists didn't prey in some vaguely psychological sense, they physically exterminated anyone who disagreed.
Come join the dark side where we enjoy the wonders of binary formats such as avro and protobuf.
Only you'll get higher-level abstractions (pattern matching, FP-style maps/flatMaps&Co throughout the standard library) and powerful collections with full support for generics.
Better yet, start with Kotlin from day one.
* introducing Java developers to the world of FP about ten years ago (i.e. before JDK8 and Kotlin) with a lot of that knowledge transferable to Kotlin in particular
* significantly influencing Kotlin and evolution of Java itself
Don't forget that it also made Spark (and to a lesser degree Flink and Kafka) possible.
The success of the Apache Spark engine can at least partially be attributed to
* being able to have the same expressive power as SQL but with a real Scala API (including having reusable libraries based on it)
* being able to embed it into unit tests at a low price of additional ~20 seconds latency to spin up a local Spark master