2 ms·
> Alex Roetter, now our SVP of Engineering, then an engineer, personally led the effort to convert what Scala code the ads team had already written into Java.
by retrogradeorbit 11y ago
> Alex Roetter, now our SVP of Engineering, then an engineer, personally led the effort to convert what Scala code the ads team had already written into Java.
I'm having trouble understanding why on earth you would rewrite Scala code to Java. The Scala code runs on the JVM and can interoperate with the Java, so what is the point?
- mseebach 11y agoThat's cool if the Scala bits are mostly static bit, not so much if they see active development. When (say) 5% of your codebase is Scala and the rest is Java, and your engineering team prefers working in Java, those 5% become stumbling blocks. The context switching slows you down and increases the risk of introducing errors. Also, a tool chain that will support two languages in parallel, while obviously not impossible, is necessarily more complex than only supporting one.
- flurdy 11y agoMaintenance and when adding more features to it. Obviously runs and interops fine, but for less paper cuts when they are modifying it or near to it, it makes sense to refactor it to a common base. And removing the scala plugin from poms will make the project(s) simpler. Though as a Scala dev, not the direction I would have chosen, ever.
- technomancy 11y agoI'm sure faster compile times are at least part of it.