3 ms·
i worked at a big company ($10B+) that was heavy on scala and akka. we had tons of bugs across almost every team trying to figure out which application.conf was
by foolfoolz 3y ago
i worked at a big company ($10B+) that was heavy on scala and akka. we had tons of bugs across almost every team trying to figure out which application.conf was setting something or getting overwritten from somewhere else. we had many unnecessary configs to force something we couldn’t figure out. we had maybe 2 people who actually understood it and could debug it. what a horrible system. no one ever walked away from akka and said i enjoy the decisions they made to configure it
- asimpletune 3y agoHaha I wonder if we worked at the same company. Anyways, I also remember that a lot of those same teams never read the documentation that explained how any of that stuff worked. In general, most of Scala stuff was made out to be super hard and complicated by other people, when really they just needed someone to explain to them the basics in simple terms what was happening. I don't get to write Scala anymore and now I really miss it for certain things.
- foolfoolz 3y agoi wrote scala at work for like 12 years straight. it’s a great language and i really do miss it at times. scala code always achieved its goal of being less code. but there were some things like this where scala made it more difficult. and i would like to chalk this up to “someone just needed to learn the basics”, but why was everyone having this issue? it’s a bad interface