6 ms·

Exciting 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 Fluxibl

Exciting 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 seems to limit compatibility with the next one. The barrier of entry to doing things right is HUGE. Also, if you disable JS the site would be useless, 100%. If I were to go with angular it would be even worse. I honestly may go back to jQuery on this project yet. I don't expect it to be huge, and since most Foundation plugins use jQuery anyway it should work. I honestly loathe how much crap I'm loading for two pages: sign-up / register.

therealmarv 10y ago
If you know the site is small why do you do the pain and go react, router and fluxible etc. etc. ? The investment in this (huge) toolchain will be beneficial when you start making things more complicated... then you may hit a wall with normal jQuery/JS. But not every project needs a big React based toolchain. This is definitely a JS platform problem. I'm currently looking at Elm because it makes life easier in comparison... but there you have other gaps like not good jQuery plugin interaction.
cityzen 10y ago
"doing things right"... by whose standards? It blows my mind how convoluted everything has become due to "doing things right" and "best practices". It's a side project, keep it in perspective. The faster it gets done, the sooner you can refactor IF you need to refactor.
sotojuan 10y ago
> 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.
- criswell 10y ago
  Fetch support is awful. Rachel McAdams knew the future.
  - sotojuan 10y ago
    Plenty of polyfills out there. I mentioned it because it's a lot lighter than superagent or worse, request.
    - icecube 10y ago
      Honest question, what is wrong with request (and superagent)? Is it just size or something more? I am only asking because yesterday I was looking for a promise supported library and I was comparing superagent (with its promise wrapper), request-promise, axios and node-fetch. I have narrowed it down to axios and fetch but I would like to hear your opinion on the matter.
      - sotojuan 10y ago
        The size. For a Node app, maybe not so bad (though I'd use node-fetch or got[1] which are smaller). For a browser app, loading all of superagent (which is almost 2 megabytes) just to make a few GET and POST calls is silly. Never used axios but I've heard good things about it and its creator is awesome. I just use fetch because it does what I want. [1] https://github.com/sindresorhus/got https://github.com/sindresorhus/got
        icecube 10y ago
        Wow, had no idea that request was so bloated. And thanks for mentioning got. I just checked it out and I think that is the lib I will be going with on the backend. I love the stream support, very cool.
  - therealmarv 10y ago
    +1 for fetch. Use the good github fetch polyfill for old browsers https://github.com/github/fetch https://github.com/github/fetch
scarecrowbob 10y ago
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.
- arenaninja 10y ago
  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.
  - scarecrowbob 10y ago
    I do expect to use it for my work. But at this rate it seems like it needs to mature a bit and settle down before I should use it.
20years 10y ago
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.
- y4mi 10y ago
  how did you get that idea? he needs most of the libraries only on two pages: login and register. i sincerely doubt his site only has these two.
mohsinr 10y ago
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/ https://vuejs.org/guide/comparison.html https://vuejs.org/guide/comparison.html https://hashnode.com/post/choose-between-reactjs-and-vuejs-for-frontend-project-using-laravel-ciibz8fof01fnj3xt7xs8tnrx https://hashnode.com/post/choose-between-reactjs-and-vuejs-f...
formula1 10y ago
This sounds like a big deal but that is effectively what you have to learn either way. The difference is that one is built in a competitive landscape and the other is done in a big god object.

therealmarv 10y ago

If you know the site is small why do you do the pain and go react, router and fluxible etc. etc. ? The investment in this (huge) toolchain will be beneficial when you start making things more complicated... then you may hit a wall with normal jQuery/JS. But not every project needs a big React based toolchain. This is definitely a JS platform problem. I'm currently looking at Elm because it makes life easier in comparison... but there you have other gaps like not good jQuery plugin interaction.

cityzen 10y ago

"doing things right"... by whose standards? It blows my mind how convoluted everything has become due to "doing things right" and "best practices". It's a side project, keep it in perspective. The faster it gets done, the sooner you can refactor IF you need to refactor.

sotojuan 10y ago

> 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.

criswell 10y ago
Fetch support is awful. Rachel McAdams knew the future.
- sotojuan 10y ago
  Plenty of polyfills out there. I mentioned it because it's a lot lighter than superagent or worse, request.
  - icecube 10y ago
    Honest question, what is wrong with request (and superagent)? Is it just size or something more? I am only asking because yesterday I was looking for a promise supported library and I was comparing superagent (with its promise wrapper), request-promise, axios and node-fetch. I have narrowed it down to axios and fetch but I would like to hear your opinion on the matter.
    - sotojuan 10y ago
      The size. For a Node app, maybe not so bad (though I'd use node-fetch or got[1] which are smaller). For a browser app, loading all of superagent (which is almost 2 megabytes) just to make a few GET and POST calls is silly. Never used axios but I've heard good things about it and its creator is awesome. I just use fetch because it does what I want. [1] https://github.com/sindresorhus/got https://github.com/sindresorhus/got
      - icecube 10y ago
        Wow, had no idea that request was so bloated. And thanks for mentioning got. I just checked it out and I think that is the lib I will be going with on the backend. I love the stream support, very cool.
- therealmarv 10y ago
  +1 for fetch. Use the good github fetch polyfill for old browsers https://github.com/github/fetch https://github.com/github/fetch

scarecrowbob 10y ago

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.

arenaninja 10y ago
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.
- scarecrowbob 10y ago
  I do expect to use it for my work. But at this rate it seems like it needs to mature a bit and settle down before I should use it.

20years 10y ago

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.

y4mi 10y ago
how did you get that idea? he needs most of the libraries only on two pages: login and register. i sincerely doubt his site only has these two.

mohsinr 10y ago

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/ https://vuejs.org/guide/comparison.html https://vuejs.org/guide/comparison.html https://hashnode.com/post/choose-between-reactjs-and-vuejs-for-frontend-project-using-laravel-ciibz8fof01fnj3xt7xs8tnrx https://hashnode.com/post/choose-between-reactjs-and-vuejs-f...

formula1 10y ago

This sounds like a big deal but that is effectively what you have to learn either way. The difference is that one is built in a competitive landscape and the other is done in a big god object.