libretto
jsoniter-scala
Our great sponsors
libretto | jsoniter-scala | |
---|---|---|
2 | 29 | |
190 | 706 | |
- | - | |
9.5 | 9.6 | |
3 days ago | 3 days ago | |
Scala | Scala | |
Mozilla Public License 2.0 | MIT License |
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.
libretto
-
Synit – A Reactive Operating System
I'm not sure this is actually easy to solve. The basic idea here seems to be that actors coordinate with the help of shared mutable state (the "dataspace"). At this point you're actually back to square one as synchronizing shared state is the core problem with distributed, concurrent systems…
Given that, and the fact that this whole thingy is untyped makes me skeptical. Not even the std. ingredients like type-state, session types, behavioral types, or the like seem to get used. I also don't see linear types here, which go very well with session types / behavioral types, and can help making typing message passing easier.
Also that this approach would be completely network transparent, as I see it, seems like a design flaw. One needs control over the various effects that can occur! Otherwise the points form "distributed systems future work" can't be solved, imho.
And form the practical point of view: There is no Akka / Pekko based Scala implementation? I'm quite surprised, to be honest.
Akka / Pekko is the actor runtime, and Scala is famous for it's eDSL features; besides of course its type-system, which makes thing like Libretto possible, which seems related here:
https://github.com/TomasMikula/libretto
Syndicate-lang looks OTOH more like the usual callback-hell.
But like I've said, I don't get this whole thingy really. I've just clicked through some parts of the web-sites. Most likely I'm just overlooking the elephant in the room. So would be glad to learn more!
(BTW: Very nice web-site design on all the projects. Especially nice typography. Really enjoyed this part while clicking through this stuff.)
- New Scala 3 Codebases
jsoniter-scala
-
1BRC Merykitty's Magic SWAR: 8 Lines of Code Explained in 3k Words
What an amazing step by step explanation!
More than 2 years ago I found that byte array view var handles are quite suitable to cook efficient SWAR routines with Java/Scala.
See a lot of other examples of SWAR usage, like parsing Base16/64 string, java.time.* and number values directly from byte arrays:
https://github.com/plokhotnyuk/jsoniter-scala/blob/master/js...
-
The Newest Java Json Benchmark Results just dropped
Afaik dsl-json came up with a lot of improvements and inspired a several other libraries like JsonIter and jsonIter-scala. Jsoniter-scala by u/plokhotnyuk is probably the most optimized JSON library on the JVM at this point, and seems to power most of the Scala ecosystem. Some implementations/optimizations eventually made their way back into Jackson and other libraries.
-
Please try my JSON library
I was on your place more then 5 years ago, when cut the 1st release of jsoniter-scala.
-
Post your problems with Scala 3/2.13 compiler performance!
I've just increased compiler performance in ~1.5x times by adding these JVM options for the code cache
-
smithy-translate : a CLI tool to turn openapi specs and json-schema specs into smithy specs, written in Scala
We have our own open-source code-generator that produces Scala code from Smithy. The code module is entirely dependency-free, and the generated code is not biased towards any library, be that http or json. We do however have out-of-the-box integration with jsoniter and http4s.
-
Why does Scala seem to be slow at benchmark results?
You can use jsoniter-scala. It is easy to use like upickle.
-
Scala needs *highly* efficient libraries to survive in a multi-core age
BTW, jsoniter-scala uses it for faster parsing and serialization using SWAR techniques, like here.
-
Using Circe with GADT
Probably you should have both codecs (for Foo and for its T) are implicitly available in the scope, like it is done in the following test for jsoniter-scala:
-
Starting with scala
BEWARE: uJson is vulnerable under DoS attacks
-
Is Scala a good choice for a data intensive web backend?
Please see sources (and GitHub history of development) of jsoniter-scala as an example in the domain of JSON parsing and serialization.