6 ms·
> Could you make a few examples? Sure, not in any particular order (and there's a lot more) 1. Users can use drag and drop functionality on areas, making upda
by ecmascript 7y ago
> Could you make a few examples?
Sure, not in any particular order (and there's a lot more)
1. Users can use drag and drop functionality on areas, making updates to the backend as they are moving stuff around. To have the webpage reload would not be an acceptable experience.
2. File management. Users can upload files and create folders, refreshing the page after every update wouldn't be nice.
3. Users can retrieve data on many objects. Open specific objects and see it's data in popups. Edit the data, add comments, upload images etc. Wouldn't work very well with a refresh.
> Why couldn't the requests be done by the back-end?
When the backend can do the requests, it does. I meant doing requests to our backend and to static resources.
> Absolutely, but isn't that exactly the point of the article? Working with a framework can make development massively easier - however, the benefits of this only go to developers, while users have to bear the costs.
Not really. I am saying that many new apps aren't simple crud apps anymore.
- plorkyeran 7y agoWhat part of that do you think wasn't possible on the web 5-10 years ago? The term "ajax" is 15 years old now.
- true_religion 7y agoIt’s not that it wasn’t possible, but it was really fiddly keeping the HTML up to date with all state changes, and having the rendered template match up with what the JavaScript wanted to do. I ended up having to cut a lot of features to make projects happen on time, and adding a new complex feature to an existing site coded with unobstrusive JavaScript was always felt like a full rewrite. Doing it with React though is like being back to working with desktop GUIs. Anything you want we can do. In the older days, anything that had to be a complex webapp would be easier done as a java applet, or a flash app.