Viewing profile — logarhythm

Thank you for explaining how you work, and I would never laugh at a developer for copy/pasting code. We've all done it! I'm still intrigued to understand exactly how you share code…

Thank you for your comprehensive and detailed feedback! I'll leave Joakim to respond to your comments about his presentation, and I'll respond directly to your comments about the n…

I'm not sure we're understanding each other. When I asked "How does it solve the problem of sharing code across service boundaries?", I meant how does your language or architecture…

That's useful feedback, thank you. I'll suggest that change to Joakim.

Have you read the "Advantages of Polylith" page? https://polylith.gitbook.io/polylith/conclusion/advantages-o... It tries to summarise the benefits from both a development and depl…

Technically, a Polylith interface is a collection of "pass-through" functions, each of which delegate their function call to an "implementation" function within the component. I ag…

Which ecosystem do you work with? How does it solve the problem of sharing code across service boundaries?

That's right, it's a highly opinionated approach to building software, which comes with a host of benefits. Including my favourite; a complete untangling of your development and pr…

I was confused because you were replying to a comment which mentioned the "long video", so I assumed you were both talking about the forty-minute one on the homepage of the documen…

The idea with that part of the video was to couch the new concept (components) within the framework of existing concepts (functions, objects, layers, etc.) to try to help people co…

Exactly! Components are an attempt at scaling-up functions to a system-level building block, whilst maintaining as many of the benefits as possible.

Your understanding of Polylith is essentially correct. It is a combination of existing ideas, such as monorepos, convention, components, interfaces, encapsulation, and static code …

Thanks for the feedback, we appreciate it. It's tricky to pick the right level of detail when explaining an idea like Polylith. If we could precisely identify the level of understa…

Before you completely give up on understanding the concept, I would like to suggest you try the 10-minute "Polylith in a Nutshell" video: https://www.youtube.com/watch?v=Xz8slbpGvn…

Thanks! It was a bit nerve-racking to give traffic light ratings to existing architectures that people use and enjoy, but I hope we were fair in our assessment.

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 w…

I'm a member of the team that created Polylith, so feel free to ask questions or give feedback. Polylith has been gaining momentum within the Clojure community. As an example, you …

Polylith is, first and foremost, an opinionated file structure for codebases (similar to how a framework forces you to structure your code in a particular way). Polylith's structur…

We've simplified the architecture, by reducing the number of concepts down to just three: components, bases, and projects. The tool is simpler, gives faster feedback, and a better …

Thanks for pointing this out. I've added that fair play note to the first page of the documentation.

Nova | nova.com | Web Developer | Stockholm, Sweden | Full-time, on-site Nova is a talent network, which is transforming into a product organisation. We’re building web and mobile …

Totally agree with your point, but just a quick note: using the thread-first -> macro won't work in this case, instead you'd use the thread-last macro ->>. Also Clojure doesn't hav…