Yes. The autodesk fusion course that I learned 3D printing design off of on Udemy had a bunch of instructions for UI elements that had moved in the application.
It wasn’t a big deal but I would have still appreciated it if the author inserted some new recorded segments or re-recorded some content to make up for it.
> Does it though? I mean I'm still teaching thread-safety and recursion to my interns... a solid foundation is a solid foundation.
I think you are confusing interiorizing some fundamentals with things moving fast. There are languages and frameworks rolling out higher level support for features covering concurrency and parallelism. While you focus on thread-safety, a framework you already use can and often does roll out features that outright eliminate those concerns with idiomatic approaches that are far easier to maintain. Wouldn't you classify that as moving fast?
But are you teaching the basics of programming with 30 year old textbooks? Can you learn the principles of web dev by building like they did 30 years ago? Sure. But it will be a pain in the ass vs using something that is up to date.
See you in ten years! We're a hop, skip and a jump from one click automated conversion from every legacy Java app to web and electron desktop compatible code and we can just retire Java entirely. in 2025, Java is not the most performant. It does not run in the most places. it is not the easiest to write or reason about. its advantage over anything else is momentum and it's losing that too.
React is just a formalizatio of a UI update pattern that exists in every app ever made except the ones that are bad.
Source: written a lot of java and nobody is currently paying enough to make it worth doing again.
It wasn’t a big deal but I would have still appreciated it if the author inserted some new recorded segments or re-recorded some content to make up for it.