pekko
requests-scala
pekko | requests-scala | |
---|---|---|
8 | 4 | |
1,074 | 702 | |
4.8% | 1.0% | |
9.7 | 4.5 | |
7 days ago | 5 days ago | |
Scala | Scala | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
pekko
-
Is akka still worth learning to be employable?
Pekko is open source, has the same API. So there's no problem there.
- Migrate the classic transport of pekko to Netty 4 without CVEs
-
6 Common Misconceptions Around Akka-HTTP / Pekko-HTTP
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.
-
Reconnecting with Scala. What's new?
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.
-
Scala opensource projects
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
-
What is the current status of Akka in your organisation?
There is an option missing: Considering switching to pekko when it's ready: https://github.com/apache/incubator-pekko
-
Stop Building on Corporate-Controlled Languages
- 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.
requests-scala
-
Scala opensource projects
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.
-
Scala Toolkit makes Scala powerful straight out of the box
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.
-
Scala vs Java/C# code examples
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.
-
Every time I sit down to use an HTTP client and JSON parser, I get really frustrated
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?
What are some alternatives?
zio-akka-cluster - ZIO wrapper for Akka Cluster
Akka HTTP - The Streaming-first HTTP server/module of Akka
ZIO - ZIO — A type-safe, composable library for async and concurrent programming in Scala
Finch.io - Scala combinator library for building Finagle HTTP services
Scala Native - Your favorite language gets closer to bare metal.
jefe - Manages installation, updating, downloading, launching, error reporting, and more for your application.
scala-cli - Scala CLI is a command-line tool to interact with the Scala language. It lets you compile, run, test, and package your Scala code (and more!)
Http4s - A minimal, idiomatic Scala interface for HTTP
Play - The Community Maintained High Velocity Web Framework For Java and 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
nim-sqlite3-abi - SQLite3 wrapper
sttp - The Scala HTTP client you always wanted!