Nice post. Lots of interesting applications of this with profunctor adapter patterns.

With ADTs we are unbundling data from behaviour. Data goes in the ADTs and behavior goes in functions that operate on them. Think pattern matching vs polymorphism. Often The choice of approach is nuanced on what is mainly driving change. For types OO and operations ADT

Indeed it is good to see the evolution. In the meantime i've used this in many projects to solve this builder issue records. Its really quite neat solution
github.com/Randgalt/rec...

Thats great. Let me know how you get on

What sort of examples would useful? I had some ideas about potentially integrating with springs reactive webflux types and form validation. That might be a bit more practical for some users.

There is certainly boilerplate adding hkts to java and room for improvements but i think you might be surprised once you get familiar with the patterns how much they can help. Did you see the draughts game i added? If you have any suggestions as to what might help i'm really happy to here

I did a blog series here that covers some of these ideas. blog.scottlogic.com/2025/01/20/a... Im hoping to do some posts on the what why how of #higher-kinded-j over the coming weeks. In the meantime take a look at the order example in the project. Any feedback or questions most welcome

There is certainly an art to writing a good fluent api. An enjoyable and insightful series.

This is a good alternative github.com/Randgalt/rec...

A most excellent commentary and thoroughly good read!