4 ms·
"Click next to continue" ...I don't see a next button. But I do see the hamburger icon in lower left corner-- so, that works. This is cool. I remember tellin
by hellohowareu 4y ago
"Click next to continue" ...I don't see a next button. But I do see the hamburger icon in lower left corner-- so, that works.
This is cool. I remember telling someone I was introducing to web app development how they should follow a similar path: Learn XHR, then jQuery Ajax, then fetch/axios for example.
Just so they can see why the newer methodologies exist.
- hardwaresofton 4y ago> This is cool. I remember telling someone I was introducing to web app development how they should follow a similar path: Learn XHR, then jQuery Ajax, then fetch/axios for example. I'm convinced this is one of the best ways of learning (whether you're going for breadth or depth). Knowing the path an ecosystem took and the stops along the way is critical to understanding why things are as they are, and contrasting new entrants. This comes up a lot in frontend framework fatigue. Most frontend frameworks and tools exist in a path-dependent context and knowing the path often answers many questions. This is also the reason why a mark of high quality projects is the comparison section ("Why use X over Y?"). It indicates that the creator is a student of the history and intentionally struck out to create something different (and possibly better).