Does it though? I mean I'm still teaching thread-safety and recursion to my interns... a solid foundation is a solid foundation.

▲

dangus 5 days ago | parent | next [-]

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.

▲

locknitpicker 4 days ago | parent | prev | next [-]

> 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?

▲

victorbjorklund 4 days ago | parent | prev | next [-]

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.

▲

mathgeek 5 days ago | parent | prev [-]

For the fundamentals, sure, but many of the top sellers are going to be on things like React, Next, etc.

▲

malfist 4 days ago | parent [-]

And in ten years after react is forgotten about, there will still be companies actively hiring Java developers

▲

llbbdd 4 days ago | parent | next [-]

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.

▲

locknitpicker 4 days ago | parent | prev [-]

> And in ten years after react is forgotten about, there will still be companies actively hiring Java developer

In ten years you'll see greybeards complaining that new kids don't know shit about React fundamentals.

▲

bcjdjsndon 4 days ago | parent | next [-]

> In ten years you'll see greybeards complaining that new kids don't know shit about React fundamentals.

Nah you won't. Js frameworks comme and go all the time

▲

locknitpicker 4 days ago | parent [-]

> Nah you won't. Js frameworks comme and go all the time

React was released 12 years ago, and since then a few React clones popped up as well such as Preact.

▲

malfist 4 days ago | parent [-]

React occupies a very similar place today as angular did back in the day, and angular is on life support, if that.

	▲	locknitpicker 4 days ago \| parent [-]
		I don't know what argument you think you are making. React was released in 2011 whereas AngularJS was released in 2010 and Angular2+, what we actually call Angular, was released in 2014. So your counter examples of popularity are projects what at best started out at the same time as React but unlike React winded down in popularity. After over a decade l, React is not only the most popular framework by far but also is the support framework for a few of the top 10 frameworks. So what point did you thought you were making? That React managed to become the dominant framework whereas your examples didn't?

▲

cindyllm 4 days ago | parent | prev [-]

[dead]