[logarhythm]

Thanks for the feedback, and I'm glad to hear that you understood the concept from the text documentation.

We decided to include both videos and text in the documentation because we know that people are different, and have different preferences for learning.

You're right that people are opinionated, and that it's difficult to convince them to try new ideas. However, I've been pleasantly surprised at how open the Clojure community has been to our concept and at the momentum it's starting to build.

It'll be interesting to see if other language communities have the same mindset.

[tluyben2]

It's great you do this really. More ideas on how to actually get to LEGO (promised in software for a long, long time) like development. But yeah, even more than languages, I would think you need a massive following to get traction. Happy the community likes it!

[ModernMech]

> More ideas on how to actually get to LEGO (promised in software for a long, long time)

I think for this reason the Lego analogy needs to be completely abandoned. Every effort of software modularization has been analogized to Lego at some point, and yet they all fall short. No arhicture claims they are the equivalent of twine glue and toothpicks, even if that's what it ends up being. So any N+1 language/framework/architecture promising it's going to be Lego (for reals this time), even if it does actually deliver, will not be taken seriously when they make the claim.

[tluyben2]

Well, good ABI/API’s and, let me really clearly separate this from the word ‘good’, standard OS GUI frameworks like Windows wpf and Mac OS X cacao for frontends is as far Lego as I have seen for now. Web frontends is where it all goes terribly wrong; nothing fits and everything breaks when you put X into Y when X and Y are from other authors generally. It is a shit show. But for backends and internally it can be done with good APIs. Problem is… not many people can write those, so you end up with something that says lego on the pack but is in fact lego after your ‘always was a bit weird’ cousin played with it with his flamethrower.

[tengstrand]

Polylith targets the backend, so I will concentrate my answer around that. I agree that good APIs are important. Polylith helps you with sharing code because it's built around "movable"/decoupled bricks that can be reused across services (e.g. different kinds of APIs). Reuse is a hard problem to solve, and you need LEGO-like building blocks for that.

[jonahbenton]

As a Clojure dude, looking forward to reading. Would appreciate the docs in a single pdf for offline reading. Looks like there are tools that consume a gitbook but would be great if you could just publish a version yourselves!

[lioeters]

Not sure if the link will work, but here's the result of clicking "Export PDF" from right sidebar only visible on wider screen.

https://storage.googleapis.com/download/storage/v1/b/gitbook...

[furkan3ayraktar]

You can download PDF version of the documentation directly from GitBook. The option is only visible on desktop. When you land on the website, the top most item on the right hand side menu is "Export as PDF".