4 ms·
The problem with Scala is that it's a huge language and it gives you a lot of ways to misbehave. It is the same exact problem that C++ has - too many people tur
by papito 5y ago
The problem with Scala is that it's a huge language and it gives you a lot of ways to misbehave. It is the same exact problem that C++ has - too many people turn it into an intellectual exercise and a dick-measuring contest of who can write the most elegant (unreadable) code. If you ignore all that, Scala is an amazing language.
- cies 5y agoThis is exactly my experience. Like C++, a Scala project needs a document describing what parts of the languages should not be used, or avoided in most cases. There is a great danger in this. Hence I prefer a language that is smaller and helps me to avoid cruft being checked in to version control. Linters are a solution, I've seen it work in JS/TS project. Not sure if C++/Scala have linters up to the feature level of JS/TS linters.
- halfmatthalfcat 5y agoThat's also a strength? If you (the technical founder) know how to leverage Scala and can hire competent Scala devs (there are a lot of them who exist), you can potentially cut your development team by some large factor.
- cies 5y ago> you can potentially cut your development team by some large factor Compared to what? Java? Kotlin? And only initial development? Or also maintenance? And why potentially and not certainly? What can make that difference?
- papito 5y agoThat's all moot once you decide to do micro-services and your team has to explode by 10x, while completing the same work or less.