3 ms·
I was hoping the "beyond" would be along the lines of domain specific languages. It wasn't, and I can't follow the article's conclusion. Library vs framework v
by JonChesterfield 5y ago
I was hoping the "beyond" would be along the lines of domain specific languages. It wasn't, and I can't follow the article's conclusion.
Library vs framework vs DIY seems domain specific.
If your thing has been built so often already that much of the logic can be factored out into a framework, great - may as well use that. Unit testing also works well as structure you plug tests into.
If parts of your thing occur elsewhere but the overall structure doesn't, probably want libraries for the common parts. Equally use libraries for when the frameworks that fit don't look good enough.
If you can't find an adequate library, DIY time.
Write your own language seems difficult to justify economically but I really like the domain/language fit you can get out of it.
- nilshauk 5y agoI don't think my article shuts the door on domain specific languages even though it doesn't offer it as an answer. It could be an answer. By relying a bit less on frameworks and writing more code ourselves we have the chance to make our code fit the domain we're working with better. For now I wanted to wrestle a bit with the idea of always pulling in frameworks to do things. > If your thing has been built so often already that much of the logic can be factored out into a framework, great - may as well use that I agree, though that often comes with some costs and tradeoffs like I tried to outline in the article.