Today it looks surreal that a mere portfolio of mind boggling animation effects would be enough to get a 21 year old an $84k job, but back in the time of peak web 2.0 craze, just having words jquery and 3 years experience on your resume was just enough to get 3 to 4 calls with ready offers every month.
The Brutal Lifecycle of JavaScript Frameworks
51–60 of 128 posts
Re: The Brutal Lifecycle of JavaScript Frameworks
#52Re: The Brutal Lifecycle of JavaScript Frameworks
#53Earlier quoted context omitted.
Indeed! In fact, after I spent time using react and angular for two separate products, I actually switched back to mostly rolling my own JQuery (usually). It just works, and takes up much less of my mindshare than trying to learn various frameworks every time I roll a new site (which incidentally is every 3 - 6 months). There is always more support for it (with all the questions being answered), and the API never cha…
I did that on a product as well. It went pretty well. The issue is with more complicated UI. The more complicated it is, the faster JQuery breaks down. That being said, it's better to have a bit of a spaghetti JQuery than to try and retrain unwilling programmers in Angular.
Re: The Brutal Lifecycle of JavaScript Frameworks
#54As 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…
Re: The Brutal Lifecycle of JavaScript Frameworks
#55Earlier quoted context omitted.
Acceptable way would be "Hey, it's done like this, but since the language sucks there's this random library where you can do it this way". Including jQuery for one small task would be stupid. Including jQuery in a non-web project would be weird. Including jQuery in some es variants would be impossible.
At that time, javascript was used exclusively for client-side web development. It was pretty much impossible to write ajax requests in any sane fashion that worked cross-browser. It's not such a stretch to assume the user asking the question could use jQuery.
And while I agree with the second, I'm talking about general language questions not related to web in any way (no DOM manipulation, no http requests, etc..).
Re: The Brutal Lifecycle of JavaScript Frameworks
#56Why are 'angular' and 'angular.js' seperate tags?
Re: The Brutal Lifecycle of JavaScript Frameworks
#57Why are 'angular' and 'angular.js' seperate tags?
Re: The Brutal Lifecycle of JavaScript Frameworks
#58As 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…
Does SO operate in the EU?
As it offers goods and services to EU citizens, it has to operate according to GDPR as far as I understand it.
And it does do sales in the EU, there are plenty of SO jobs being advertized (and paid for) in the EU.
Re: The Brutal Lifecycle of JavaScript Frameworks
#59As 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…
Re: The Brutal Lifecycle of JavaScript Frameworks
#60As 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…
They said they only did this for US based IP addresses. (Not that it makes it OK...)
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?