Chimney Alternatives

Chimney reviews and mentions

• Chimney alternatives - ducktape and MapStruct
  3 projects | 3 Jun 2025
• Chimney 0.8.0 (stable) released
  1 project | /r/scala | 13 Oct 2023
• Chimney 0.8.0-M1 with the initial support for Scala 3
  1 project | /r/scala | 5 Aug 2023
• Chimney 0.8.0-M1 – type mapping library for Scala released for Scala 3
  1 project | news.ycombinator.com | 3 Aug 2023
• ORM in Scala
  1 project | /r/scala | 3 Apr 2023

  But yeah, I wonder if using a tool for case classes conversion like https://github.com/scalalandio/chimney would help in managing those ADT hierarchies for DB/business logic/web layer/etc.

• Chimney 0.7.0 released
  2 projects | /r/scala | 24 Feb 2023

  Hello, if you have some nice examples could you please check if it's something that would fit any of issues planned for 0.7.1 or create a new one?

• Output object with Circe with sealed trait + case classes adds sealed trait block
  1 project | /r/scala | 13 Nov 2022

  Perhaps, https://github.com/scalalandio/chimney would leverage it.

• Smithy4s 0.15.0, now with Smithy 2.0 support
  2 projects | /r/scala | 18 Aug 2022

  Thankfully, there are some solutions that can help reduce the boilerplate of these manual conversions. For instance, chimney : https://scalalandio.github.io/chimney/

• Is it possible to get runnable generated scala code from a macro (chminey to be specific)?
  2 projects | /r/scala | 20 Jan 2022

  I want to upgrade one project to Scala 3.1, but I'm using the macro heavy chimney (https://github.com/scalalandio/chimney) to reduce the boilerplate, which is not available for Scala 3 yet. My idea was to copy and paste the code that chimney generates on 2.13, and after that uncomment the uses of chimney for now.

• From ES6 to Scala: Basics
  9 projects | news.ycombinator.com | 20 Jan 2022

  In my $dayjob we originally used Scala, but I pushed for a couple of new services to be written in TypeScript/Node as it was really hard to hire Scala developers. I'd say it worked well, we even took a somewhat functional approach to building things. We tried fp-ts but that was a bit hardcore (when you are trying to hire TypeScript developers who don't know functional programming), so just built Either and Option types which provided 99% of what we needed.

  There are still a few things I miss though:

  * Pattern matching and exhaustive checking. Using a switch statement it is possible to define a function that can emulate the compile-time exhaustive checking, but it's still rather weak compared to what you can do in Scala.

  * Implicits. Being able to define something that can convert say a UUID to a String or vice versa automatically just feels like magic, especially when dealing with data from third party systems.

  * Compiler macros and metaprogramming. It enables tools like Chimney (https://scalalandio.github.io/chimney/) to be built, which I don't think are possible with TypeScript right now.

• A note from our sponsor - SaaSHub
  www.saashub.com | 11 Aug 2026

  SaaSHub helps you find the best software and product alternatives Learn more →