It seems to me the author misunderstands what's behind React: it's not a framework but just a library, focused on a functional approach (versus an imperative one) older than "the pattern survived in decades", sentence which doesn't prove there could not be something better.
The author has a lots of experience, because of this I would have expected more technical criticism about React flaws, avoiding illations about companies; he seems more frightened to leave his comfort zone than to understand how you can do something different without coupling, without the MVC pattern and explain why React is doing it in the wrong way.
aselvini 3574 days ago. link 1 point ▲ ▼