kriiuuu

We use Scala as well and are very happy with it. We also have a lot of TS, and at this point we are tempted to just switch to using ScalaJS on the frontend as well because of how much better the language is to use. It feels like Scala 3 fixed a lot of issues people had with the language. The IDE tooling isn’t the best, but even then it feels like the IDE tooling for TS breaks all the time once the project is large enough.

Effect systems are great for concurrent programming and easier to reason about than actors. They aren’t available in all programming languages however.

Hopefully scala-cli being the default runner might help in the furure

AWS also has it’s own implementation of this with smithy

Significantly easier because there is just a lot less surface area.

I feel the same about Scala. I use Scala3 daily and almost every other language is such a step back. I have looked at F# and it looks like one of the only other languages I would enjoy as much as Scala. Haskell is nice too, but the ecosystem is just not quite there. F# being able to tap into the rich C# ecosystem and Scala being able to tap into the Java ecosystem is such a win and makes them feel a lot less niche when you use them.

Good news is that you can achieve this with relatively little boilerplate in Java with sealed interfaces and records now. Relative to Java that is

That is not UB. That is simply mutable data. The solution here is static analysis (Rust) or immutable persistent collections.

Unison would fit here

I don’t think anyone actually listens to anything said in a standup. 99% just does not affect you in any way. If we have an issue we need help with we just send a message on teams or get on a call. The standup is pure ritual

Yes. I hate it with a passion. Pointless meetings, planning that doesn’t matter and endless timesinks. The only devs I can imagine liking it are the ones that don’t want to take responsibility of the product backlog nor want to think about feature implementation. They just want micromanaged tiny tasks that tell then what to do next, a life void of responsibility.

Yes. I would quickly look for a new job. A linter should help the programmer along the way, but be easy to disable when it’s invalid.

Looks exactly like smithy?

Scala 3 has opaque types for this. And libraries like iron build on top of it so you can have a very clean way of enforcing such things at compiletime.