I 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.
No comments yet.