Hacker News Reader

Comment by ng12 | Hacker News Reader

I think the opposite: it's a sign that your API is too wide and users expect more special cases and edge features to solve their needs.

View on HN

If a user felt that way, it would make no sense for them to choose Vue. Vue’s up-front, stated design goal is omit special cases or edge features intentionally and directly assert that’s not a good way to design a framework.

Vue may be right or wrong, but nobody wishing for special case features can claim to be surprised. If you picked Vue knowing you need a bunch of special case features, that’s on you.

Everyone always needs a bunch of "special case features". Always. If you're not doing something new, why are you bothering to write code?

That's like saying that if you don't need to invent new words, why are you bothering to write books.

The abstractions a framework makes available are not analogous to words, but rather ideas. Indeed you should not bother writing a book if you have no new ideas.

I use Vue and haven’t found it hinders me from doing this myself. Are you suggesting Vue should not just release a framework but also solve every user’s special case? Your comment isn’t making sense to me.

Right, I think this is evidence that they're not doing as well at that stated goal as they could be.

Exactly, the users are not doing well because they’re expecting to be able to misuse Vue and demand special case features, while Vue itself is doing good by resisting this and sticking to the plan in terms of framework design.

Reply on news.ycombinator.com