Re:Please do not attempt to simplify this code
by mamon on Thursday December 27, 2018 @07:00PM
(#18773769)
Calling Scala "purist language" sounds riddiculous to me. It is a hybrid of object-oriented and functional styles, with tons of weird hacks like case classes for pattern matching, implicits, type inference that kind of works, but is not full Hindley-Milner, Java bindings that require weird conversions between Java and Scala collection types, _ as a wildcard in few different places. Scala is the opposite of purism. There's a reason why Odersky's "Programming in Scala" has over 800 pages - even listing all the hacks used in the language is not trivial.
Re:Please do not attempt to simplify this code
by dnautics on Friday December 28, 2018 @04:17AM
(#18775736)
Erlang is not at all a pure functional language, fyi. Functions definitely have three very important core side effects that are optional: message sending, message retrieving, and dying (raising an exception).
I would call the erlang system the "one white lie" category of purity on the FP purity scale. It is, by the way, a huge tradeoff that makes operating in EVM languages far easier than, say Haskell.
Re:Please do not attempt to simplify this code
by barrkel on Friday December 28, 2018 @08:51AM
(#18776674)
> deploying a distributed monolith
This is not what Kubernetes is for.
Take a step back and understand what you're criticising. You just look uninformed.
Re:Please do not attempt to simplify this code
by thdespou on Wednesday January 02, 2019 @09:38AM
(#18806384)
> Kubernetes' reputation is just the opposite: that far from being a simple and useful thing, it's an overengineered, overcomplicated solution to a self-inflicted problem (deploying a distributed monolith).
Thats why companies pay the buck to get 24/7 support. Because its that good!
Kubernetes' reputation is just the opposite: that far from being a simple and useful thing, it's an overengineered, overcomplicated solution to a self-inflicted problem (deploying a distributed monolith).
> But the closest I ever came to using a functionally developed product was RabbitMQ (written in Erlang). That one was _such_ a pain to use and operate — must have been the developers still dreaming in the purity of its code instead of writing some installation docs. I moved on to Kafka later and didn't regret it a minute.
Erm, Kakfa was developed in Scala, whose advocates far more of a reputation for purist pontification than Erlang developers do. Maybe all that beauty and purity is actually good for something?