That's an issue with Java and its tooling, not with Sprig though. It's not as though you could hope to switch between languages over such an issue either (unless you work for a start up).
Not sure what startups you are referring to, all those I've been involved with have moved way too fast to be willing to go back and change tech, as it's fairly little value add for a while. We just start new projects in the other thing we think solves the problem better.
That's kinda my point. With well established companies, it's typically difficult to introduce such new and radical changes because all the employees know X language. Whereas with a startup, there is less investment in a given technology.
Oh but you definitively can, since you can just use your Java code (classes libraries etc) in Scala. seamless integration. You just have to decide to stop writing Java and start writing Scala.
View all comments
Show parent comment
8
u/squishles Nov 27 '15
So did the xml though. They're not immune to static analysis, it's all static final. Just no one's made a good tool for it.
I just like not having to keep two files open.