this post was submitted on 25 Aug 2023
68 points (94.7% liked)
Programming
17333 readers
212 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Apparently I used it at its peak. It was the go to language for big data processing at the time
We had developers leave my company because they had to work with scala during 2 -> 3 migration. Everybody hates it now
I never used Scala 3 but was under the impression that the migration wasn't as bad as Python 2->3 https://lichess.org/@/thibault/blog/lichess--scala-3/y1sbYzJX
This better shows what migration is like https://docs.scala-lang.org/scala3/guides/migration/incompat-syntactic.html
More, new brackets near lambdas, new string formatting, indentiation change. Doesn't look much, but absolute madness when your team is weak in Scala. Only 1 dev had prior scala experience, but whole team had to be involved in migration of breaking changes in scala syntax behavior and... same for gatling. Also changes in syntax. Mid-level dev left the company because of it, we very soon completely got rid of scala and replaced it with TS and Go. Both languages new to the team, but 0 complaints since February.