undefined | Better HN

0 pointsjrq8y ago0 comments

I've seen it a while ago too, but without lightbend blessing it's next to useless, in practical usage. I can't deliver that to a client

0 comments

5 comments · 2 top-level

_lbaq8y ago· 2 in thread

There is more to it, sbt has a very rich echo system of plugins, it will take time for any alternative to gain traction.

jrqOP8y ago

Of course, I agree. In time, as the scala ecosystem flourishes and adapts, I, along with many others, may be coaxed back in.

Scala suffers from a problem of too many bright people all trying to solve too few problems. And implicits. Bad idea there. But the rest of it is logistical, and just takes time, as you said.

Have faith! Learn ocaml or f# too, but have faith all the same.

threeseed8y ago

> Scala suffers from a problem of too many bright people all trying to solve too few problems

1000x yes.

And bright people who are so bright that they simply can't appreciate what the user experience is for people who aren't bright. These people are from a lot of experience a bit toxic. And it's a bad choice of word and it isn't personal but because they are on a different level technically they can really change teams for the worse.

At some point Scala is going to need to better reconcile the Typelevel world of Scala and the Play/Java world of Scala. Otherwise languages like Kotlin is going to chip away until nothing is left.

aphexairlines8y ago· 1 in thread

Stripe uses Bazel to build Scala code: https://github.com/bazelbuild/bazel/wiki/Bazel-Users#stripe

Other large companies use Gradle or even Ant to build Scala code.

Why would a client be restricted to sbt?

threeseed8y ago

Because SBT is (unfortunately) the standard build tool for Scala.

So if you're trying to do any cross project compilation to Scala Native or ScalaJS then there is no alternative to SBT.

Likewise many much needed Scala build tools only work with SBT.

j / k navigate · click thread line to collapse

0 comments

5 comments · 2 top-level

_lbaq8y ago· 2 in thread

There is more to it, sbt has a very rich echo system of plugins, it will take time for any alternative to gain traction.

jrqOP8y ago

Of course, I agree. In time, as the scala ecosystem flourishes and adapts, I, along with many others, may be coaxed back in.

Scala suffers from a problem of too many bright people all trying to solve too few problems. And implicits. Bad idea there. But the rest of it is logistical, and just takes time, as you said.

Have faith! Learn ocaml or f# too, but have faith all the same.

threeseed8y ago

> Scala suffers from a problem of too many bright people all trying to solve too few problems

1000x yes.

And bright people who are so bright that they simply can't appreciate what the user experience is for people who aren't bright. These people are from a lot of experience a bit toxic. And it's a bad choice of word and it isn't personal but because they are on a different level technically they can really change teams for the worse.

At some point Scala is going to need to better reconcile the Typelevel world of Scala and the Play/Java world of Scala. Otherwise languages like Kotlin is going to chip away until nothing is left.

aphexairlines8y ago· 1 in thread

Stripe uses Bazel to build Scala code: https://github.com/bazelbuild/bazel/wiki/Bazel-Users#stripe

Other large companies use Gradle or even Ant to build Scala code.

Why would a client be restricted to sbt?

threeseed8y ago

Because SBT is (unfortunately) the standard build tool for Scala.

So if you're trying to do any cross project compilation to Scala Native or ScalaJS then there is no alternative to SBT.

Likewise many much needed Scala build tools only work with SBT.

j / k navigate · click thread line to collapse