[debt]

It would be tight if we could purge from the web all posts and threads related to unsupported and outdated ReactNative versions.

It's actually quite interesting to see the almost in real-time development of ReactNative through the lens of hobbled and broke-ass solutions to problems associated with deprecated RN versions posted on StackOverflow or Medium.

[SketchySeaBeast]

Ack, no! We need to find a way to version it, absolutely, but as I'm currently crawling through a codebase that's using an old version of react, I need those old threads.

[burtonator]

This is actually a problem that could be solved by naming actually.

Angular has a similar problem because if you search for an olde version of Angular you get 2.x and they're up to 7 now...

I think at some point it makes sense to rename the project to avoid the cruft of the past when it really deserves it.

[EpicEng]

I'm emphatically _not_ a front end dev, but recently I've needed to do some front end work on an existing AngularJs project. It took me about an hour to realize that AngularJs != Angular. A bunch of examples weren't working and I just couldn't figure out why...

[paraditedc]

As someone who used to write frontend blog posts, I found this issue particularly frustrating, as an author.

I have posts about Angular.js, webpack, React Apollo, etc and they become outdated every 6 months.

The problem is that I wouldn't know about it. Despite having lots pageviews and me asking readers to help notify me in comments, people just come, read and close the window. So the one way I found out they were outdated is when I actually went back to reference them for my own work. It's not fun.

[warmblanket]

I think it’s a good idea to list versions at the top of the articles.

[bdcravens]

Every technology has to deal with this problem.