ZIO
Http4s
Our great sponsors
ZIO | Http4s | |
---|---|---|
50 | 22 | |
3,694 | 2,366 | |
0.8% | 0.3% | |
9.8 | 9.9 | |
3 days ago | 3 days ago | |
Scala | Scala | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ZIO
-
40x Faster! We rewrote our project with Rust!
The one advantage Rust has over Scala is that it detects data races at compile time, and that's a big time saver if you use low level thread synchronization. However, if you write pure FP code with ZIO or Cats Effect that's basically a non-issue anyway.
-
What’s so great about functional programming anyway?
> It's a weakness of functional programming, not the language.
I would strongly object this.
Have you seen ZIO?
-
Switching career from F# to scala
But overall, I'm happier with Scala. It has not one, but two lively FP communities. I recommend that you pick one of them: ZIO or TypeLevel (Cats Effect, fs2, http4s, ...). To some extent, you can mix TypeLevel libraries in ZIO projects.
- New to Scala;
-
Next Steps for Rust in the Kernel
I think "better Haskell on JVM" (in contrast to "worse Haskell") is a good identity for Scala to have. (Please note that this is an intentional hyperbole.)
Of course, there are areas where Haskell is stronger than Scala (hint: modularity, crucial for good Software Engineering, is not one of them). And Scala has its own way of doing things, so just imitating Haskell won't work well.
Examples of this "better Haskell" are https://typelevel.org/cats-effect/ and https://zio.dev/ .
All together, Scala may be a better choice for you if you want to do Pure Functional Programming. And is definitely less risky (runs on JVM, Java libraries interop, IntelliJ, easy debugging, etc...).
None of the other languages you mentioned are viable in this sense (if also you want a powerful type system, which rules out Clojure).
I agree that Rust's identity is pretty clear: a modern language for use cases where only C or C++ could have been used before.
-
Java 19 Is Out
I would use Scala. I like FP and Scala comes with some awesome libraries for concurrent/async programming like Cats Effect or ZIO. Good choice for creating modern style micro-services to be run in the cloud (or even macro-services, Scala has a powerful module system, so it's made to handle large codebases).
https://typelevel.org/cats-effect/
The language, the community and customs are great. You don't have to worry about nulls, things are immutable by default, domain modelling with ADTs and patter matching is pure joy.
The tooling available is from good to great and Scala is big enough that there are good libraries for typical if not vast majority of stuff and Java libs as a reliable fallback.
-
Scala Isn't Fun Anymore
I actually think Scala is in the best position it's ever been.
There is a commitment to making the language simpler, easier and cleaner.
On the backend, ZIO [1] is the best concurrency library on any platform. On the frontend you have really interesting Scala.js projects like Laminar [2].
The biggest issue really is the tooling. SBT is simply awful.
[1] https://zio.dev
- A Python-compatible statically typed language erg-lang/erg
-
Ask HN: Any alternative to Java (OOP) which has the same ecosystem?
Scala? With some help from additional libs such as Zio (https://zio.dev/) it allows you to write production quality programs like you would in Haskell on top of the JVM quite quickly...
- Cats vs ZIO
Http4s
-
Sequential application of a constructor?
See also cats-effect and fs2. cats-effect gives you your IO Monad (and IOApp to run it with on supported platforms). fs2 is the ecosystem’s streaming library, which is much more pervasive in functional Scala than in Haskell. For example, http4s and Doobie are both based on fs2.
-
Grasping the concepts and getting them down to earth
Most important/known: * https://http4s.org/ - an HTTP client/server * https://github.com/typelevel/fs2 - streaming * https://github.com/tpolecat/doobie - JDBC
-
Relative popularity of programming languages on Hacker News
Scala devs are too busy wondering about free monads and F[Request[F] => Response[F]]. I am very pleased by http4s, Doobie, ScalaJS, and the whole ecosystem, really: https://http4s.org
-
http4s as a replacement for akka-http?
In reality, your performance issues will not be http4s, but something else. That being said, there are improvements that http4s can and is making, and I'm quite excited about the future 1.0 release, which has some important and fundamental performance improvements already, like a a 125% performance improvement on the plaintext benchmark from https://github.com/http4s/http4s/pull/6091 - and finally, yes, akka-http does have very good performance, but you can also get good performance out of http4s.
-
Is Scala a good choice for a data intensive web backend?
http4s for REST services.
-
Scala became Typelevel/Zio only ecosystem?
This is a long list of misunderstandings I don’t have the patience to unpack. Instead, let me refer you to the links in my top comment in the thread, then suggest you learn at least http4s, a purely-functional web service library that’s been used in production for a decade or so now.
-
Pleasant to use Scala libraries
I would say http4s and Doobie. Both are pure FP libraries in the Typelevel ecosystem. Both are exceptionally clear, extremely reliable, extremely pleasant to use… I like to point out http4s, in particular, is primarily a collection of types modeling the relevant RFCs. What behavior it has comes overwhelmingly from the underlying Cats, cats-effect, and fs2 libraries. This reflects the generality of those underlying libraries and the intense focus of the http4s team. The same applies to Rob Norris and Doobie, which tames JDBC as well as it can be tamed, IMO.
The most popular nowadays are - I guess - akka-http and http4s. You can also use Play if you don't want to start from scratch but prefer a framework-based approach.
-
Scala Http Framework
If you want something more powerful, pure-functional and you need to do complex, concurrency-heavy operations, have a look at http4s: https://http4s.org/
-
Typelevel: On Recent Events
I don't think this is toxic but still, it doesn't sit well with me: https://github.com/http4s/http4s/issues/4718
What are some alternatives?
Akka HTTP - The Streaming-first HTTP server/module of Akka
sttp - The Scala HTTP client you always wanted!
cats-effect - The pure asynchronous runtime for Scala
Monix - Asynchronous, Reactive Programming for Scala and Scala.js.
Finch.io - Scala combinator library for building Finagle HTTP services
cats - Lightweight, modular, and extensible library for functional programming.
Vert.x - Vert.x is a tool-kit for building reactive applications on the JVM
fs2-kafka - Functional Kafka Streams for Scala
Spray - A suite of scala libraries for building and consuming RESTful web services on top of Akka: lightweight, asynchronous, non-blocking, actor-based, testable
Scala.Rx - An experimental library for Functional Reactive Programming in Scala
Reactor-Scala-Extensions - A scala extension for Project Reactor's Flux and Mono
scalaj-http - Simple scala wrapper for HttpURLConnection. OAuth included.