4 ms·
or gradle, or bazel. Scala doesn't require sbt, and the other build tools work well for mixed codebases (scala, java, kotlin, javascript).
by aphexairlines 6y ago
or gradle, or bazel. Scala doesn't require sbt, and the other build tools work well for mixed codebases (scala, java, kotlin, javascript).
- bchallenor 6y agoBazel is a nice build tool, but AFAIK it still doesn't support Scala 2.13, released mid-2019: https://github.com/bazelbuild/rules_scala/issues/809 https://github.com/bazelbuild/rules_scala/issues/809
- hocuspocus 6y agoI think Lucid (the charts, not EVs) use these internally: https://github.com/higherkindness/rules_scala https://github.com/higherkindness/rules_scala And they support Scala 2.13
- bchallenor 6y agoInteresting. Here is a comparison of the two rules_scala implementations: https://github.com/higherkindness/rules_scala/issues/261 https://github.com/higherkindness/rules_scala/issues/261
- natchy 6y agoOne of the reasons I chose F#. Too many choices for a Scala novice. Seems to be a pervasive pattern. I think Scala was actually a better choice since my company mainly does AI/ML (python) and Scala has some clout in data science. But I’m only migrating the application layer so not a deal breaker. I was leaning more towards Scala going into the “exploration phase”. —————————— Side note. Using typescript on front end, f# on back, vscode, and GitHub for repo + CI/CD. Feels nice using a single vendor (Microsoft) for dev, even though each tool is stand-alone.