No foundation? What do you think all these libraries and frameworks are built on???
The true path to having a "deep" front-end toolbox is in learning things that are not libraries. Here is a "long-lasting" frontend list that really just scratches the surface:
- CSS(animations, advanced layouts etc...)
- HTML(canvas, accessibility, svgs...)
- websockets, advanced networking
- advanced browser APIs(indexdb, mouse/touch events, events in general, WebGL...)
- high performance js, perf monitoring
Its really just DOM/state manipulation, and different levels of caching that frameworks provide.
I take your point but keeping an app current enough to maintain the ability to hire, is hardest in this area. Not like SQL or C for example. Knowing that can be useful for decades. You build knowledge that persists - experience is a good thing. I can’t tell you the front end stuff I’ve not used in a long time because the list is very long. Much of that knowledge isn’t useful and the code has long changed. I can get involved but I’m not as interested.
It’s like in a war when the new guy shows up. Don’t get too friendly; he’s probably not going to make it.
The true path to having a "deep" front-end toolbox is in learning things that are not libraries. Here is a "long-lasting" frontend list that really just scratches the surface:
- CSS(animations, advanced layouts etc...)
- HTML(canvas, accessibility, svgs...)
- websockets, advanced networking
- advanced browser APIs(indexdb, mouse/touch events, events in general, WebGL...)
- high performance js, perf monitoring
Its really just DOM/state manipulation, and different levels of caching that frameworks provide.