Stackoverflow, the place in which those who search for Javascript will almost certainly leave with jQuery.

@rEaL-jAsE ...

That's because SO is increasingly outdated, and answers that made sense years ago don't anymore.

The hard truth is that the whole Q&A concept of SO doesn't work in a fast changing domain.

Ah, reminds me of this one: https://doxdesk.com/img/updates/...

And here I am finding myself actually USING jquery at work. 😖

@Root It's OK for legacy projects where the cost of eliminating jQuery would exceed the benefit.

But whoever is using jQuery for new projects in 2019 reveals himself as noob, or is forced to take orders from an noob.

@AlmondSauce love how the person who gave a non-jQuery answer got downvoted heavily

@AlmondSauce The honest answer got down votes? :-D :-D

@Fast-Nop wouldn't they be able to sort of fix that by adding a decay factor to answers? As in, when ranking search results, add a certain penalty to older threads that's proportional (or monotonically increasing anyway) to thread age, so they'd appear lower in results. Of course this would require manual tuning too, but it should work

@RememberMe Sounds quite OK, but the issue is that this is at odds with what SO wanted to be: some sort of encyclopedia that gets written and then only looked up.

You would have to allow duplicate questions because the tech may have changed in-between. You see where this is going.

Instead, the SO idea is that people would really update years old answers although they won't reap new reps. That fails because SO is designed around rep-whoring. And because the SO audience is now full of trolls who have no intention of contributing anything useful.