cask VS pekko

I want to just block as if there's no tomorrow, no effects / hardcore FP (maybe only something like https://github.com/softwaremill/ox), what would you use? E.g. for http server / db / json ?https://github.com/com-lihaoyi/cask ?

There's the Li Haoyi's ecosystem of tools and libraries that's fun to hack on, has a low entry-bar (with a design philosophy of using the least complex abstractions for the job), and has few libs like requests and cask that may appeal to those liking some python minimalism. That's not the fastest way to learn hardcore FP, that's not the worst either.

Wonder if anyone uses: https://github.com/com-lihaoyi/cask

Is play-framework a strong requirement? If not, you might have an easier time building a simple API and serializing JSON with the lihaoyi ecosystem, namely cask as the microframework and uPickle/uJson.

For people who want to get their feet wet with Scala, I highly recommend Cask and the rest of what some people affectionately call “the Singapore stack,” in honor of Li Haoyi, its developer. He emphasizes tasteful use of Scala features with an emphasis on API ergonomics. All of his work is a joy to use.

The documentation points to a pretty outdated example. Can you try with the latest 0.8.3 release?

If you want something really easy and simple, have a look at cask: https://com-lihaoyi.github.io/cask/

Best I can do is Cask: https://com-lihaoyi.github.io/cask/ 😅

Pekko is open source, has the same API. So there's no problem there.

Understandable considering the size of Pekko and how much time is passed, I would recommend asking any questions/concerns on either the Pekko mailing list https://lists.apache.org/[email protected] or on Github discussions https://github.com/apache/incubator-pekko/discussions.

Another big reason behind the "struggle" is we have done further improvements. For example the first release of Pekko will support all Scala versions from 2.12 up to 3.3.0 LTS (which was just released a couple of days ago). This also includes Pekko's modules which means we had to either add back in Scala 2.12 support or Scala 3 support. Yet another example would be https://github.com/apache/incubator-pekko/pull/281 which allowed us to drop scala-java8-compat dependency for Scala 2.13 or higher. So while these improvements aren't technically necessary, they have a large impact on Pekko going forward, i.e. the scala-java8-compat change means that we can drop Scala 2.12 at any point in time without breaking users.

Apache Pekko is the open source fork of Akka. I know they can use more hands right now - https://github.com/apache/incubator-pekko/issues

There is an option missing: Considering switching to pekko when it's ready: https://github.com/apache/incubator-pekko

- In 2022, Lightbend changed the Akka licence, made it proprietary and very expensive at large scale

Software that starts out as more "pure", non-corporate open-source can still turn the tables on you and charge large licensing fees later. But at least if it's open source from the start, it can be forked, e.g. for Akka, there's this Apache fork that was started after Akka changed its licence: https://github.com/apache/incubator-pekko . This is the key open source protection, and it's true for both corporate and non-corporate projects.