InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now. Learn more →
µPickle Alternatives
Similar projects and alternatives to µPickle
-
-
InfluxDB
InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.
-
Catch
A modern, C++-native, test framework for unit-tests, TDD and BDD - using C++14, C++17 and later (C++11 support is in v2.x branch, and C++03 on the Catch1.x branch)
-
-
jsoniter-scala
Scala macros for compile-time generation of safe and ultra-fast JSON codecs + circe booster
-
hitchstory
Type-safe YAML integration tests. Tests that write your docs. Tests that rewrite themselves.
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
-
-
-
-
-
os-lib
OS-Lib is a simple, flexible, high-performance Scala interface to common OS filesystem and subprocess APIs
-
-
-
redis-dict
Python dictionary with Redis as backend, built for large datasets. Simplifies Redis operations for large-scale and distributed systems. Supports various data types, namespacing, pipelining, and expiration.
-
doc-detective
Doc Detective is an open-source documentation testing framework that makes it easy to keep your docs accurate and up-to-date.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
µPickle discussion
µPickle reviews and mentions
- Unit Tests as Documentation
-
Why does Scala seem to be slow at benchmark results?
The upickle library has traditionally had great performance for handling json in Scala apps so is likely to be seen as a safe choice for someone starting a Scala project. It appears though that not just upickle, but other json library projects are having difficulties maintaining their old level of performance when they release using Scala 3's macros. uPickle currently has an open issue where you can see some of these issues: https://github.com/com-lihaoyi/upickle/issues/389 and here you can see the weePickle folks are also having the same performance problems. Looks like things changed up significantly enough between Scala 2 and Scala 3 so that in order to maintain the same functionality they have resorted to using runtime reflection for mapping to/from case classes.
- Preparing for uPickle 2.0.0
-
Updated benchmark results of JSON parsers for Scala - now with results for circe and play-json boosters based on jsoniter-scala.
See here for sample code size numbers (not picking on upickle specifically, it's just what I'm using myself. I've heard similar reports about e.g. circe)
-
[help] Trouble with derivation and generics
A good starting point is the note in MacroImplicits.scala in upickle sources. "derives Writer" for a specific case class Foo simply adds a given Writer[Foo] to a companion object of the same specific class. However, this cannot be done automatically for a trait defining sum type - in this case trait Thing. The required given must be defined manually, and the ones automatically obtained for case classes can be used in it.
-
A note from our sponsor - InfluxDB
www.influxdata.com | 19 Jun 2025
Stats
lihaoyi/upickle is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of µPickle is Scala.