3 ms·

I must be honest, my experience with node was very short but this article suggests me that working with js may be really more complicated than working with java

by andretti1977 10y ago

I must be honest, my experience with node was very short but this article suggests me that working with js may be really more complicated than working with java. Too many frameworks (which often lives too shortly), too many things to learn, it's overwhelming...sometimes it seems to me that working with js has become so difficult that working with java and jquery is still easier and better (i know lot of people will throw me hate for this comment!)

tambourine_man 10y ago
I have no problem with difficulty (if interesting), but I get completely blocked by, what seems to me, needless complexity. The will to learn vanishes completely.
- andretti1977 10y ago
  I agree and this is exactly what i feel: too much complexity that seems needless. I hardly have cases where i can't develop reasonably complex frontend and must use angular or react so i can't stand all this javascript frameworks useless (imo) complexity.
- jim_d 10y ago
  I think the interesting thing is that for 90% of what is being built most tools are overkill and JQuery is really good enough. I say that as someone that started using React/Flux almost 2 years ago, and as someone in the midst of moving from Flux stores to Redux. The power of these tools is when there are large teams involved, when the complexity of the state on the FrontEnd is extremely high, and when you absolutely need a Single Page Application. Most of the time all 3 of those conditions aren't true, and in those cases you're better off using something like jQuery which is boring, easy to reason about, and everybody already knows it well.
erik14th 10y ago
Apples and oranges. You're comparing SPA paraphernalia with a library that basically gives you a sane cross browser JS API's and some goodies. Yes, you can develop highly interactive, reasonably complex web apps with jQuery, but then you would have to develop a lot of abstractions, guidelines and whatnot to keep the thing from exploding. That's pretty much what those SPA libraries and frameworks are. About server side, IMO there's no inherent advantage on picking node over java other than the fact you'll have one less language in your stack(or not, since you may end up using TypeScript or some other compile-to-js language).
jasonthevillain 10y ago
I agree. The explosion of new ideas is also an explosion of learning curves. I suppose that's fine for people who just want to learn something new every day. I want to make stuff, and the less maintenance it needs the better. Most of what's on the hype train isn't too appealing for that.

tambourine_man 10y ago

I have no problem with difficulty (if interesting), but I get completely blocked by, what seems to me, needless complexity. The will to learn vanishes completely.

andretti1977 10y ago
I agree and this is exactly what i feel: too much complexity that seems needless. I hardly have cases where i can't develop reasonably complex frontend and must use angular or react so i can't stand all this javascript frameworks useless (imo) complexity.
jim_d 10y ago
I think the interesting thing is that for 90% of what is being built most tools are overkill and JQuery is really good enough. I say that as someone that started using React/Flux almost 2 years ago, and as someone in the midst of moving from Flux stores to Redux. The power of these tools is when there are large teams involved, when the complexity of the state on the FrontEnd is extremely high, and when you absolutely need a Single Page Application. Most of the time all 3 of those conditions aren't true, and in those cases you're better off using something like jQuery which is boring, easy to reason about, and everybody already knows it well.

erik14th 10y ago

Apples and oranges. You're comparing SPA paraphernalia with a library that basically gives you a sane cross browser JS API's and some goodies. Yes, you can develop highly interactive, reasonably complex web apps with jQuery, but then you would have to develop a lot of abstractions, guidelines and whatnot to keep the thing from exploding. That's pretty much what those SPA libraries and frameworks are. About server side, IMO there's no inherent advantage on picking node over java other than the fact you'll have one less language in your stack(or not, since you may end up using TypeScript or some other compile-to-js language).

jasonthevillain 10y ago

I agree. The explosion of new ideas is also an explosion of learning curves. I suppose that's fine for people who just want to learn something new every day. I want to make stuff, and the less maintenance it needs the better. Most of what's on the hype train isn't too appealing for that.