3 ms·
With jquery, you'd have to put in a lot of work to do this. And I'm not a front end engineer, so I went from knowing enough jquery to be dangerous to doing Reac
by epistasis 3y ago
With jquery, you'd have to put in a lot of work to do this. And I'm not a front end engineer, so I went from knowing enough jquery to be dangerous to doing React tutorials,
where I saw how the design of this system was enabling bad default behavior.
If my irrational hatred has a better target than the term "React" I would like to know it. I do despise the usability of nearly every SPA I have used. It is perhaps possible to program an SPA so that the deficiencies are not noticed, which is great, but that does not appear to be the norm nor is it made easy by SPA frameworks.
- ctvo 3y agoIt's a state issue. The flash of inconsistency you see is because the client eagerly modifies state before the server persists it (or some form of this problem). The routing issue is because the application (SPA) is using business logic to control the browser's navigation state. Sometimes opening a modal will be a new push on to the nav stack so you can hit back, sometimes it isn't, sometimes they forget things, etc.. All of it though is just too much state being managed on the client by the application and that state being managed poorly. This isn't only related to React. It's always been possible to screw up with managing state in any framework.
- epistasis 3y agoExactly, the framework changes static data display into "state" which is something that should be avoided unless absolutely necessary.