> I absolutely see no problem with using readystate. We have a load event now. Ready state is the legacy cruft left behind by Microsoft a decade ago. Let's not

> I absolutely see no problem with using readystate. We have a load event now. Ready state is the legacy cruft left behind by Microsoft a decade ago. Let's not confuse new devs with magic numbers and convoluted events that are often cargo-culted incorrectly. > To confront beginners with all their overhead (build tools for JS! Just crazy) is in no way helpful. People have been dropping a jQuery CDN script tag on their pages since well before most build tools were invented. W3schools has _multiple_ "tutorials" that could be replaced with $('...').load('...'). It's rich when HN complains about websites that do things like break middle click and browser history and lack error states, but then advocate for trash code like w3schools peddles that makes these bad practices more common.