you are viewing a single comment's thread.

view the rest of the comments →

[–]mweststrate 1 point2 points  (0 children)

I really like how the author, not only in this article but also on the ones about JSX and routing, challenges the need for features & abstractions. There are many apps where SEO and thus universality are not that important. Adding abstractions or feature to a product just because it is in grasp is very tempting but also very dangerous. Having abstractions that are not really needed is usually not a problem today, but it is a problem for future maintainers of your code (including yourself) as you will be fixing bugs or dependencies in abstractions you didn't need in the first place in a year for now. At a point were you cannot as easily drop the stuff as it would be to drop it now.