requests-scala VS Play

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.

Another thing that caught my attention is the choice for HTTP client. If the authors wanted to go with the simplest thing, they could have picked requests-scala (from the com-lihaoyi family of libraries). If they wanted to go with full blown Scala FP, they could have chosen http4s client (Ember). Sttp awkwardly sits in the middle being neither.

Finally, to give you an example of how simple Scala can be when you get rid of all the fancy stuff, take a look at the examples in Li Haoyi's requests-scala library, a port of the excellent requests Python library. I challenge anyone to call that code complex.

http4s (either with Blaze or Ember) is great, but you may need to think a bit about what you're doing. Maybe https://github.com/com-lihaoyi/requests-scala will be the best choice for your particular situation?

My major complain here is that, as far as being a web framework there is precious little information here about the framework. How does this framework scale with multiple requests? What concurrency strategy is it using (threads, processes, actors, etc?). Is this opinionated (it doesn't seem so but it also doesn't say it isn't either). How does this work with popular libraries x,y,z. The full docs have a little bit more information, but not a ton. But mostly there are some cute toy examples and "built in python" and thats about it.

Lets compare this with for example play https://www.playframework.com/ I know from this that it built on Akka, its stateless, aims for predictable resource consumption, has non-blocking io, etc. There is a ton of really important information on what does this web framework actually do that is really important when you are making a choice of a framework.

I have no idea how good this framework is, but besides a few toy examples, I can't see anything that makes me thing "wow this is great I need to use this".

A web application framework for Java/Scala: https://www.playframework.com/

Scala 3 migration isn't as simple as migrating other apps, you can track the work at https://github.com/playframework/playframework/issues/11260

And there are frameworks you can use to make development easier, like Play. And Java has plenty of choices for dependency injection frameworks.

However do note, Play should be perfectly usable as well, and it's still maintained by the community: https://github.com/playframework/playframework/issues/11649

In university I learned a bit of Java, so maybe I could use it professionally I guess?. There were many options to choose from. DropWizard, Spark, Play Framework. But the more documented one in the internet I found was Springboot, besides there were some courses in spanish and some friends that knew something about Springboot, so I give it a chance.

For a backend web server I use Play - https://www.playframework.com/ which I find to be the easiest one as a backend web server. For learning/using spark I found this course from coursera to be very useful. https://www.coursera.org/learn/scala-spark-big-data