What's Next for Scala
I wanted Scala to be my &quot;better Java&quot; for a long time, mainly because it seemed to have plentiful headroom as I seek to learn more.  The community enthusiasm was also contagious.<p>But:
1) the ecosystem makes it seems like I need to be a genius enough to learn a new DSL a bit too often, and everything is so...complex, which leads to...<p>2) It is hard to pitch to an organization because of the learning curve if you assume any project maintainer must learn scala to expert level.  I failed (in one attempt on a scala mailing list) to pitch to the scala community the idea of having language levels:  a compiler switch or the like that would guarantee that a given project will be maintainable by java programmers with only N (1-2 I hope, for the first level) hours of scala training or study, maybe another level for adding certain features (or listing them in a config file), and full-on expert.  So teams can be formed with realistic long-term maintainability in mind.  Edit:  This may be practical with add-ons I didn&#x27;t try yet.<p>3) It was unclear what would be the best reasonable, maintainable way to use sqlite.  (Edit: in a multiplatform way to include at least BSD, linux, windows, mac.  Maybe call a native code library for each?  Sounds like lots of work and maintenance to do it well.)<p>4) Startup times, future viability of scala native (edit: or equivalent), and whether it helps or adds enough more complexity given all the above, to just learn Rust and (hopefully) simplify life (in some ways).<p>5) And you have to learn java first (for those who didn&#x27;t know it already), and know its libraries and idioms to some extent.  Will that still likely be true?<p>Comments welcome.  (I enjoyed the article.)  Maybe I&#x27;m just the type that wants to hit the sweet spot between what C, Java, and Scala do (edit: and Scheme), in a way that is hopefully&#x2F;eventually at a complexity level that is inviting to other devs, but with plenty of learning headroom for my future growth.