Scala folks, I've been wondering - what are the biggest issues and hindrances with modernisation and maintenance of existing Scala apps? I mean things that have historically caused you the most pain in long term care over an existing codebase in Scala. My personal bet is that it's Spark because how far behind it is in terms of language versions and the write-once, care-never-if-it-runs approach to Spark pipelines but I'm happy to find out if I'm wrong. Beneath is a poll with few predefined options:
1) spark being behind modern Scala versions, also job abandonware status
2) breakage introduced by Scala language proper (2.13 collections, 2->3 migration)
3) ecosystem fragmentation and resulting lack of maintenance or breakage
4) abuse of abstraction for abstraction's sake
If there's nothing in it that fits your experience - leave a comment. Please retweet!
11%
Spark
23%
Scala language breakage
41%
ecosystem fragmentation
25%
abuse of abstraction
339 votes • Final results