Hacker News Reader

I've made the mistake of using "opinionated" libraries in the past. Usually what it means is that they lock you into a workflow designed by someone with different use cases from yours, to a fault.

A product I'm working on is being choked by another opinionated framework as author's opinions no longer align with best practices and we're locked in.

View on HN

It's fair to point out the limitations of libraries like this, but it's only a mistake if you don't understand what you're getting into.

There's a definite tradeoff: short-term productivity vs. long-term flexibility.

I think there are certainly cases where it makes sense to choose short-term productivity, as long as you understand the potential tech debt you're incurring.

maybe I was a bit clumsy with my title because this project was designed to not lock the user but to lead him to a nicely structured app architecture.

Reply on news.ycombinator.com