3 ms·
"Why I no longer use full MVC frameworks to build sites that have no need for models or controllers." The better question might be why you ever started? As a
by Lazare 11y ago
"Why I no longer use full MVC frameworks to build sites that have no need for models or controllers." The better question might be why you ever started?
As a bonus, the article discounts React out of hand as one of those "average MVC frameworks" that does too much, then reinvents an incredibly crude version of hand-rolled JS components rendering DOM...the one thing React does.
The takeaway from the article, I think, should be:
1. If you only need some simple React components being fed by a basic Sinatra or Express server, just do that; it'll be ten times easier to develop and maintain. (Edit: Although frankly, the example is so simple I think the author might be better off with a static site generator...)
And:
2. Do your research before reinventing the wheel badly.
- tracker1 11y agoIn addition, I find it funny, that TFA's final solution isn't really much different than static server-side rendering using react, mercury or a number of similar tools already invented. Not to mention that using babel you get jsx and es6 template string support... even if not using react/jsx I'd still favor string templates for my code.