3 ms·
I think that’s OK. When I first had to use XML, I had to learn the XML spec and output it manually - serialization libraries didn’t really exist yet. I’ve sinc
by Ancapistani 5mo ago
I think that’s OK.
When I first had to use XML, I had to learn the XML spec and output it manually - serialization libraries didn’t really exist yet. I’ve since seen generation of juniors come up through the ranks using XML as an interchange format (and then JSON) without ever learning it fully. It was fine, and nothing terrible happened.
I’ve seen AJAX go from the hot new thing to people not knowing what it stood for, to now most people not even recognizing the term. AJAX didn’t die; it became so common we don’t need a word for it anymore.
- tyre 5mo agoKind of like JQuery. I know why it was such an incredible library and am happy no new devs I work with (a) know what it is (b) understand why it was necessary. Thank god the underlying language, libraries, and browser support have moved forward. And IE6 is dead. God, what a nightmare.
- Ancapistani 5mo agoI remember when IE6 was the shiny new solution that we desperately wanted :). IE 5.5 was much, much worse, and there was a long time there when it didn’t get any updates at all.
- dzonga 5mo agoif you learnt Ajax - it still works just like it did whether you're using the XHR api or the newer fetch api. html forms still work the same way. can one say the same for the various form libraries for react or state solutions.
- Ancapistani 5mo agoI’m aware of the entire progression, and objectively I’ve seen juniors come up without knowing “the old ways” at all. I’m not sure it’s a problem, but I also can’t quite wrap my head around the way they understand systems.