Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Brutal Lifecycle of JavaScript Frameworks

stackoverflow.blog

Post reply on HN
Print view View original

71–80 of 128 posts

Re: The Brutal Lifecycle of JavaScript Frameworks

#71

Post by sapper123 »

mattmanser wrote: post #60
tkone wrote: post #59

Earlier quoted context omitted.

They said they only did this for US based IP addresses. (Not that it makes it OK...)

Not explicitly, they might have been just using US data as an example in this blog post. Even if they aren't, I still wonder that if they're checking everyones IP addresses against that database, essentially sharing our access of SO with a third-party, would it still be an inappropriate use of personally identifiable information?

It seems they're using data from a company called MaxMind https://www.maxmind.com/en/geoip2-isp-database#features .

Quoting their website, "The organization name is available for about 40% of corporate, government, and educational networks."

Re: The Brutal Lifecycle of JavaScript Frameworks

#72

Post by rainbowmverse »

mattmanser wrote: post #45

As an aside from the interesting article, does any one else find it pretty scary and privacy invading that stackoverflow think it's ok to match our IP addresses to the company we work in? It seems like a massive invasion of privacy (which I guess lots of websites are doing). But to me that SO can so casually mention the mass surveillance and privacy invasion they're doing without thinking that there's anything wrong…

Much of the industry Stack Overflow serves is based on collecting, aggregating, and selling access to exactly this sort of data. I'm not sure what to think of this specific example, but it's just one small manifestation of whatever it is, bad thing or not.

Re: The Brutal Lifecycle of JavaScript Frameworks

#74

Post by eitland »

shams93 wrote: post #44
codingdave wrote: post #12

Earlier quoted context omitted.

On the same note, the older frameworks solved older problems. jQuery was the killer framework because it handled browser compatibility back in a time when people not only needed to support IE8, but IE6, and few companies felt comfortable telling people to just update their browser. Well, those days are past, so that problem is no longer a reason to choose a framework, and when you take that out of the picture, jQuery…

Yeah with jquery we were composing templates server side. Compared to Vue trying to do a SPA in jQuery is a season in hell. It can be done but it's brutal and fragile.

> It can be done but it's brutal and fragile.

Actually many who did jQuery were proud of it.

Some of us made rock solid sites or improved exiting ones quite a bit using a technology known as progressive enhancement.

Let me tell you what is fragile: the cool things I make today that won't even try to work if I disable Javascript. :-)

Edit: and given what we have seen over the last few days now would be a good time to reconsider if every website really needs to be able to run Javascript.

Re: The Brutal Lifecycle of JavaScript Frameworks

#75

Post by Kajayacht »

myth_drannon wrote: post #21
Kajayacht wrote: post #2

One of the things I don't think it accounts for in talking about the downfall of something like jQuery is that as time goes on, the questions have already been asked. So of course there's going to be less questions asked about jQuery in 2017 versus 2009, because if I need to figure out how to select elements based on an attribute rather than a class or id, it's already there.

StackOverflow's job posts show the same trend. Jquery is required less and less http://www.reallyhyped.com/?keywords=angularjs%2Creactjs%2Cj...

I think part of that is that jQuery is pretty universal and it's probably assumed that if someone says they know JavaScript, they know jQuery. Or, I at least assume that when I'm doing interviews.

Re: The Brutal Lifecycle of JavaScript Frameworks

#76

Post by emodendroket »

itcmcgrath wrote: post #14
iambateman wrote: post #8

Earlier quoted context omitted.

This intuitively makes sense, but I'd like to see some control data. Has the volume of PHP questions (for example) fluctuated much over time?

http://sotagtrends.com/?tags=[jquery,python]&relative=false

That seems like a pretty compelling counterpoint.

Re: The Brutal Lifecycle of JavaScript Frameworks

#77

Post by rodolphoarruda »

Pretty much a Gartner's Hype Curve like behaviour on each case. Accelerated adoption, a peak, then delusion kicks in causing many people to lose interest and step away from the technology. Late adopters find lower barriers of entry later on caused by lessons learned and improvements made to the same technology. Usage increases again but a lower level when compared to the initial peak. Expectations around tech's capabilities are now more concrete and realistic, bringing stability to the ecosystem as a whole.

Re: The Brutal Lifecycle of JavaScript Frameworks

#78

Post by pjmlp »

codingdave wrote: post #12
Kajayacht wrote: post #2

One of the things I don't think it accounts for in talking about the downfall of something like jQuery is that as time goes on, the questions have already been asked. So of course there's going to be less questions asked about jQuery in 2017 versus 2009, because if I need to figure out how to select elements based on an attribute rather than a class or id, it's already there.

On the same note, the older frameworks solved older problems. jQuery was the killer framework because it handled browser compatibility back in a time when people not only needed to support IE8, but IE6, and few companies felt comfortable telling people to just update their browser. Well, those days are past, so that problem is no longer a reason to choose a framework, and when you take that out of the picture, jQuery…

I wish those days were past.

Need to target IE 11 and FF ESR currently.

Re: The Brutal Lifecycle of JavaScript Frameworks

#79

Post by pjmlp »

shams93 wrote: post #44
codingdave wrote: post #12

Earlier quoted context omitted.

On the same note, the older frameworks solved older problems. jQuery was the killer framework because it handled browser compatibility back in a time when people not only needed to support IE8, but IE6, and few companies felt comfortable telling people to just update their browser. Well, those days are past, so that problem is no longer a reason to choose a framework, and when you take that out of the picture, jQuery…

Yeah with jquery we were composing templates server side. Compared to Vue trying to do a SPA in jQuery is a season in hell. It can be done but it's brutal and fragile.

For the majority of my web development that verb is in the present tense.

Re: The Brutal Lifecycle of JavaScript Frameworks

#80

Post by myth_drannon »

Kajayacht wrote: post #75
myth_drannon wrote: post #21

Earlier quoted context omitted.

StackOverflow's job posts show the same trend. Jquery is required less and less http://www.reallyhyped.com/?keywords=angularjs%2Creactjs%2Cj...

I think part of that is that jQuery is pretty universal and it's probably assumed that if someone says they know JavaScript, they know jQuery. Or, I at least assume that when I'm doing interviews.

I think that would apply more to an Html than Jquery
Post reply on HN