Re:Scala vs Go
by pweissbrod on Tuesday February 14, 2017 @10:24AM
(#13644069)
Transportability is an oft under-valued quality when comparing languages. Yes you could write something highly performant/compact/domain-specialized in perl,scala,lisp etc but when the time comes that your product is successful and your team needs to scale or you want to transfer ownership to another team how easy is that transition going to be?
[ Parent
| on HN ]
Unless your app is so trivial that syntax and APIs are the dominating factor, I'd wager the team transition will have so much other stuff to deal with. Hopefully, not least of all, the actual program logic.
And team transitions are rather rare compared to the day to day dev that goes on. Optimising for them seems misplaced.
Re:Scala vs Go
by pweissbrod on Tuesday February 14, 2017 @06:03PM
(#13648135)
As a consultant, transitioning your work to maintainers remains a constant concern
Re:Scala vs Go
by alextheparrot on Tuesday February 14, 2017 @11:20AM
(#13644589)
A lot of Scala is written to be that scaling code, see Spark. I know your point was the possible hand-off between teams, just wanted to indicate it is often used as that scaling language in data-processing.
Spark is not just written in Scala, they shared the same philosophy of underthought design.
Luckily, there's a little reason of using Spark after Yandex released their Clickhouse: it better compresses data, it is much faster, it doesn't need crazy infrastructure of low quality Apache's code, it can be used in a realtime which is really huge.