Inspired by the Dobble card game, a friend and I built an iOS version where the symbols are emojis! You can customize the difficulty with options like “only green emojis” or other themed sets.
We don’t want to put ads in the game, but we’re exploring ways to add non-free features to make a little money from it. Has anyone done something similar? Any insights or past experiences with monetizing a casual mobile game would be really helpful!
One note from having worked with both that I don’t see mentioned: Golang dependencies are sources you basically pull and compile with your own code. In JVM-land dependencies are precompliled packages (jars). This adds one little step.
Maybe so... but so do Python or Javascript. It seems to me some other languages have only one stack (rust: cargo, rustfmt...; the .net world as well). Does it make them better? (honest question). Then again, what's Java official stack?
I'd pick sbt over mvn no doubt. Haven't played with either fury or mill, so can't comment on those (even gradle... I never really used it). But coming from years of Java/Maven I think sbt is way better. Things start complicating a bit if you have lots of plugins or macros probably.
Opposite for me. After years of Scala (which I like) I recently tried to port a few things to Scala 3 and it really feels like some of the wtf-implicit part is gone. We'll still need to make a complete idea about this version 3 though.
sbt is not perfect but new build tools are coming up lately for Scala (check out lihaoyi/mill and propensive/fury to name) plus people are working with bazel (but i guess that's more for monorepos/very big codebases. my experience (7 years and counting) with sbt is that it's very very good until you need to roll out your own tasks/plugins.
I, sort of, know the limitations WebAssembly has right now when it comes to JS interop (such as only being able to use functions with numbers as parameters!) but my guess is this is temporary.
It'd be curious to see experiments doing something Scala Native -> Emscripten -> JS-land.
Regardless, thanks so much for the work you're doing with Scala.ks (Scala is still my main language and I'm working on removing JS from my toolbox soon).
My two cents: to me WebAssembly seems like something Scala Native might address, more than Scala.js.
Or even better, both project can sort of blend for this purpose as on one hand (SN) addresses LLVM compilation and the other (SJS) is perfect JS interop (not so sure how WebAssembly does that).
Overall I think this is actually good news for people like typelevel[1]... that is people with a strong passion for Scala, a stronger community approach and a slightly different view than Typesafe/Lightbend.