6 ms·
I don't think any of scala's good features are even on a Java road map anywhere. It's actually a breath of fresh air to work on scala production systems. We d
by runT1ME 11y ago
I don't think any of scala's good features are even on a Java road map anywhere.
It's actually a breath of fresh air to work on scala production systems. We don't use a mono repo and compile times are negligible. We are also one of the largest scala shops in the country and despite the various styles used in different projects, it's all been very maintainable and easy to read.
My main complaint is tooling and the fact that you do need good training to onboard the folks who don't have scala experience.
- pkolaczk 11y ago> you do need good training to onboard the folks who don't have scala experience I can see where you're coming from, however I noticed that people experienced in Java and some other different programming language, like Python, Ruby or C++, don't need much baby-sitting to learn Scala. I've been showing some of my Scala code to other peers who don't do Scala daily for review and I never heard a complaint "I can't understand what this code is doing". More often I hear it feels quite Pythonic, only with braces and type annotations...
- brianwawok 11y agoDepends a lot on the style of Scala you write. If you write "Scala is a better Java style" (which is more what I do), it is not bad. If you write it as "functors and mondads are cool", it can be very hard for the other people to intelligently code review.
- pkolaczk 11y agoAgreed. However there is lot of "better" in the "Scala being better Java". It is not just nicer syntax. Even advanced features like implicit objects or abstract and path dependent types can be very useful and obvious at the same time, if used carefully.
- runT1ME 11y agoI don't believe this is true, assuming your peers have had the proper training. As I said before we are one of the biggest scala shops and make heavy use of pure functional style and scalaz, it works out fine.