jQuery sizes by version and compression: https://mathiasbynens.be/demo/jquery-size
This is the first time I can justify a move from a version 1.8.0 to 2.0 or 3.0 of a product with "it has fewer code".
jQuery 3.0 Release Candidate
41–50 of 71 posts
Re: jQuery 3.0 Release Candidate
#42Exciting news for jQuery. Last night, I was working on a side project. For the front-end, I'm using React, React-Route, and I'm working on figuring out Fluxible. superagent to wrap XmlHttpRequest. browserify to compile what I serve to the front-end. I don't run a reverse-proxy with a node backend since the API is in PHP, I just served the minified JS files. Honestly, it's a huge pain. And every module I toss in there…
I hear you on this. A lot of that stack is very new and still changes quickly enough that I have a hard time finding good examples to work from.
I've had a very hard time getting things like react+react-router+reflux to all work together as expected. It's not been super fun as a way of working.
And I dunno if your situation is the same as mine, but all the "contemporary" JS stuff I work with (react, etc) is for side work, that is, stuff that I am building explicitly because I want to play with the stack.
So the reaction that "you don't need all that" is probably missing the point (at least if your situation is like mine): I do things like that because I want to see how stuff works, and it's better than doing it on my $$$ projects.
Re: jQuery 3.0 Release Candidate
#43Earlier quoted context omitted.
> I honestly loathe how much crap I'm loading for two pages: sign-up / register. Sorry, but this is entirely your fault. You don't need any of what you mentioned to do this. You can just use jQuery if that works for you. No one except really bad junior devs on here or Reddit will say you are doing things "wrong". PS: Use fetch instead of superagent.
Fetch support is awful. Rachel McAdams knew the future.
+1 for fetch. Use the good github fetch polyfill for old browsers https://github.com/github/fetch
Re: jQuery 3.0 Release Candidate
#44Earlier quoted context omitted.
> I honestly loathe how much crap I'm loading for two pages: sign-up / register. Sorry, but this is entirely your fault. You don't need any of what you mentioned to do this. You can just use jQuery if that works for you. No one except really bad junior devs on here or Reddit will say you are doing things "wrong". PS: Use fetch instead of superagent.
Fetch support is awful. Rachel McAdams knew the future.
If someone else (like me) misses the Rachel McAdams reference: https://jakearchibald.com/static/posts/thats-so-fetch/fetch....
Blog post - https://jakearchibald.com/2015/thats-so-fetch/
Re: jQuery 3.0 Release Candidate
#45Exciting news for jQuery. Last night, I was working on a side project. For the front-end, I'm using React, React-Route, and I'm working on figuring out Fluxible. superagent to wrap XmlHttpRequest. browserify to compile what I serve to the front-end. I don't run a reverse-proxy with a node backend since the API is in PHP, I just served the minified JS files. Honestly, it's a huge pain. And every module I toss in there…
I hear you on this. A lot of that stack is very new and still changes quickly enough that I have a hard time finding good examples to work from. I've had a very hard time getting things like react+react-router+reflux to all work together as expected. It's not been super fun as a way of working. And I dunno if your situation is the same as mine, but all the "contemporary" JS stuff I work with (react, etc) is for side…
Our situations are very similar. For me it's just a way to play with React. I don't expect to use it at work or to make me any money.
Re: jQuery 3.0 Release Candidate
#46I'm finding I don't need jQuery anymore. What are the reasons people still use it?
I'm surprised you're asking for "reasons people still use it" when that is already quite obvious. How about telling us why you don't need the most popular JS library?
Re: jQuery 3.0 Release Candidate
#47I'm finding I don't need jQuery anymore. What are the reasons people still use it?
I use it for a couple of (related) reasons. 1. A few other libraries still depend on jQuery in turn, so I find that I still usually have it available in every app I work on anyway, so I might as well use it. 2. It "just works" and I already know it, and since it's already there, anyway (see (1) above) it just makes sense to use it. IOW, I don't feel enough pain from using jQuery to justify going off and learning what…
And, why should a new developer on fresh projects use it? It seems ES6 and latest CSS specs should cover everything JQuery used to be used for.
Plus, wouldn't actually using Vanilla JS be faster?
Right now it looks like people use JQuery for legacy code. But, they give no reason to use it for new projects, except if they need it for other libraries they're going to use. (based on legacy code anyways...)
JQuery looks redundant in the modern Javascript era on evergreen browsers.
Re: jQuery 3.0 Release Candidate
#48Exciting news for jQuery. Last night, I was working on a side project. For the front-end, I'm using React, React-Route, and I'm working on figuring out Fluxible. superagent to wrap XmlHttpRequest. browserify to compile what I serve to the front-end. I don't run a reverse-proxy with a node backend since the API is in PHP, I just served the minified JS files. Honestly, it's a huge pain. And every module I toss in there…
Curious - why are you using React and all of that for a simple 2 page project? Is it for the learning experience? Seems like way overkill unless its for the learning experience.
Re: jQuery 3.0 Release Candidate
#49Exciting news for jQuery. Last night, I was working on a side project. For the front-end, I'm using React, React-Route, and I'm working on figuring out Fluxible. superagent to wrap XmlHttpRequest. browserify to compile what I serve to the front-end. I don't run a reverse-proxy with a node backend since the API is in PHP, I just served the minified JS files. Honestly, it's a huge pain. And every module I toss in there…
You may have a look on VueJs as a lightweight alternative to React/Angular when you need simple apps to create like the one you mentioned , it is like jQuery but with very exciting features https://vuejs.org/
https://vuejs.org/guide/comparison.html
https://hashnode.com/post/choose-between-reactjs-and-vuejs-f...
Re: jQuery 3.0 Release Candidate
#50Earlier quoted context omitted.
I use it for a couple of (related) reasons. 1. A few other libraries still depend on jQuery in turn, so I find that I still usually have it available in every app I work on anyway, so I might as well use it. 2. It "just works" and I already know it, and since it's already there, anyway (see (1) above) it just makes sense to use it. IOW, I don't feel enough pain from using jQuery to justify going off and learning what…
And, why should a new developer on fresh projects use it? It seems ES6 and latest CSS specs should cover everything JQuery used to be used for. Plus, wouldn't actually using Vanilla JS be faster? Right now it looks like people use JQuery for legacy code. But, they give no reason to use it for new projects, except if they need it for other libraries they're going to use. (based on legacy code anyways...) JQuery looks…
jQuery is still much more pleasant to use than native methods when working with collections of DOM elements. If you do much DOM manipulation, you'll end up writing helpers that replicate aspects of jQuery to grease your workflow. The real issue is that trying to manage state by directly manipulating the DOM becomes a nightmare as the project grows, and newer frameworks can mostly take care of that for you.
So jQuery is still wonderful at what it does, but there isn't much reason to be directly manipulating the DOM now that there are alternatives.