And then you thought that millions of websites, a lot of commercialy crafted for customers, adopted it in no time? So an update, to the most used version which has even security isseus is not nessacary? You live in a nice world :)
That might be an option, but not as ubiquitous and easy to use. We’re dealing with people who barely read and speak a single language, much less English.
Why you use XMLHttpRequest instead of Fetch API (which makes ajax utilities more or less useless)?
It would also be nice to have a custom ajax error handling. Console logging is nice to have, but sometimes you maybe want to throw in custom error handling.
Thanks for the explantation. I wasn't aware of this (but i guess this will change when the fetch API is more widely used and vendors are implementing faster methods).
"React allows developers to create large web-applications that use data and can change over time without reloading the page. It aims primarily to provide speed, simplicity, and scalability"
You can do the 'almost' same thing with with Zam, but without the slow Virtual DOM. I say 'almost', because you really need to be good at vanillajs if you expect to create a massive and scalable web application that's written in Zam.
Well, in the programming world you can do 'almost' anything with anything, basically. So -- if you really good at it -- anything is an alternative to anything else.
Some weeks ago an experience developer said to me: "Parameterize a query? Since years i don't care about it, because ORMs like Doctrine or Sequelize take care of that"... So it's not only students or new devs who should watch out, because even ORMs can open up SQL injections.
