4 ms·

I agree with all of that, but the worst part to me(which I guess relates to your point about the accepted answers) is that there's no path to deprecating old an

I agree with all of that, but the worst part to me(which I guess relates to your point about the accepted answers) is that there's no path to deprecating old answer and old questions. I've been lambasted here in the past for saying this, but I'll say it again now and see if I get a different response; it's no longer helpful to search for "javascript" related questions and get mostly answers for jQuery. These days I'm able to solve a lot of problems just reading MDN, but sometimes I click on a Stack Overflow article and it turns out to be 12 answers that are all jQuery-specific even when the question itself doesn't call for it. jQuery isn't bad, but the world has changed around it and we can't keep pretending like everyone is using it for the same reasons we did back in 2011. This not only does new developers a general disservice, but it can do a disservice to projects that have less-than-average momentum. For instance, I use Ember JS every day, and it's a framework that has really changed a lot since its inception, but you'd never know it if you looked up questions for it on Stack Overflow. The Ember questions on there are so woefully outdated that I believe it gives potential new users the complete wrong impression of it. There are outdated React questions on there as well, but at least there's enough inertia behind React that new activity helps overcome this to a degree. On the other hand, people almost certainly have given up on Ember because none of the Stack Overflow answers work at all. Sure, we could all submit updated answers, but they'll be below the fold and they will never be reselected as the accepted answer. There are other reasons why Ember has been in decline, but I do blame the mechanics of SO as a big detractor. Preventing duplicate questions is fine, the overzealousness not withstanding, but if there's no mechanism to correct existing information as time goes on in a meaningful way, the only result can be rot.

jakelazaroff 6y ago
> it's no longer helpful to search for "javascript" related questions and get mostly answers for jQuery jQuery is used on 83% of all websites; React is used on 4% [1]. You’re right that people are probably using it differently than they were a decade ago, but even in 2021 your average jQuery question is probably useful to many more people than your average React one. [1] https://css-tricks.com/how-the-web-is-really-built/ https://css-tricks.com/how-the-web-is-really-built/
- mastazi 6y ago
  > jQuery is used on 83% of all websites; There are a lot of websites I made in the past and they are still online and many of them use jQuery, but I don't need to check Stackoverflow in relation to those websites, because I'm no longer working on them (and in most cases no one else does either, they just happily keep running unmodified). All of those are part of that 83% that you mention. Stackoverflow is a Q&A websites for developers so IMHO it should focus on tech that is currently in use on actively developed systems.
  - jakelazaroff 6y ago
    Even if only 10% of jQuery websites are maintained, and every single React website is, there are still almost twice as many actively developed websites using jQuery than React.
    - mastazi 6y ago
      That's a fair point, I didn't think about it that way.
    - adjkant 6y ago
      See my comment, and actually with that 10% number it doesn't hold true with only 50% of the logic applied. 50/10 vs 4*(unmaintained rate) + undercounting (possibly a large majority, possibly small) is probably React winning out
  - cosmotic 6y ago
    I still use jquery actively. Without substantial work and complexity, a typical react site's initial page load still requires an enormous javascript chunk for anything to show on the screen. When I notice a site I'm using is slow, unresponsive (interactivity wise), or buggy, more often than not the react dev extension is lit up. React (and ecosystem) may represent the future but they still have a lot of growing pains to overcome before totally replacing jquery.
    - 6y ago
duxup 6y ago
Even React answers of the past are often class component based... and for my taste the react answers are either slapshot / they work but aren't best practices, or if they are good they rarely explain why you would do A instead of B.

jakelazaroff 6y ago

> it's no longer helpful to search for "javascript" related questions and get mostly answers for jQuery jQuery is used on 83% of all websites; React is used on 4% [1]. You’re right that people are probably using it differently than they were a decade ago, but even in 2021 your average jQuery question is probably useful to many more people than your average React one. [1] https://css-tricks.com/how-the-web-is-really-built/ https://css-tricks.com/how-the-web-is-really-built/

mastazi 6y ago
> jQuery is used on 83% of all websites; There are a lot of websites I made in the past and they are still online and many of them use jQuery, but I don't need to check Stackoverflow in relation to those websites, because I'm no longer working on them (and in most cases no one else does either, they just happily keep running unmodified). All of those are part of that 83% that you mention. Stackoverflow is a Q&A websites for developers so IMHO it should focus on tech that is currently in use on actively developed systems.
- jakelazaroff 6y ago
  Even if only 10% of jQuery websites are maintained, and every single React website is, there are still almost twice as many actively developed websites using jQuery than React.
  - mastazi 6y ago
    That's a fair point, I didn't think about it that way.
  - adjkant 6y ago
    See my comment, and actually with that 10% number it doesn't hold true with only 50% of the logic applied. 50/10 vs 4*(unmaintained rate) + undercounting (possibly a large majority, possibly small) is probably React winning out
- cosmotic 6y ago
  I still use jquery actively. Without substantial work and complexity, a typical react site's initial page load still requires an enormous javascript chunk for anything to show on the screen. When I notice a site I'm using is slow, unresponsive (interactivity wise), or buggy, more often than not the react dev extension is lit up. React (and ecosystem) may represent the future but they still have a lot of growing pains to overcome before totally replacing jquery.
  - 6y ago

duxup 6y ago

Even React answers of the past are often class component based... and for my taste the react answers are either slapshot / they work but aren't best practices, or if they are good they rarely explain why you would do A instead of B.