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

Stepping Backwards from AngularJS to JQuery – An Experiment

hundredminutehack.blogspot.com

Post reply on HN
Print view View original

11–20 of 68 posts

Re: Stepping Backwards from AngularJS to JQuery – An Experiment

#11

Post by greenshackle »

andybak wrote: post #10
impostervt wrote: post #4

I found this interesting because it seems to have been written by a person who learned Angular before jQuery. I haven't run into that before. Maybe I'm getting old.

I found that odd. I do worry that many people use technologies because other people working at a completely different scale or in a completely different domain have hit a ceiling which wouldn't really apply to most people. They are convinced to start with a more complex and more difficult technology that's solving problems they are unlikely to be facing any time soon. 1. NoSQL traditional RDMS because of scaling/shar…

My friend was brought in by a client after the previous contractor had spent 300+ hours coding a simple organizational website - here is who we are, here is our phone number - using node.js. I doubt the website will ever see more than 20 concurrent visitors.

Re: Stepping Backwards from AngularJS to JQuery – An Experiment

#12

Post by bdcravens »

impostervt wrote: post #4

I found this interesting because it seems to have been written by a person who learned Angular before jQuery. I haven't run into that before. Maybe I'm getting old.

Well, I actually learned Angular 2 before I learned Angular 1.

Re: Stepping Backwards from AngularJS to JQuery – An Experiment

#13

Post by talmand »

jnbiche wrote: post #7

Next time, try dropping jQuery, too, and just using vanilla JavaScript. Just for fun. Simple DOM manipulation is now as simple in vanilla JavaScript as jQuery, with the only big advantage jQuery has now is if you're animating. You may find you're not missing much. You'd have to get used to slightly more involved Ajax syntax, unless you can target only new browsers, in which case the `fetch` API is just as convenient…

What's the big advantage of jQuery with animating? Are you referring to the animation built into jQuery?

Re: Stepping Backwards from AngularJS to JQuery – An Experiment

#14

Post by quantumhobbit »

pbreit wrote: post #6

Caveat: novice programmer here. Even Angular is still difficult for me to grok and sometimes I wonder if stuff that comes out of Google "suffers" (for me) from Google having unlimited resources and employing superior engineers? Would Google have a difficult time empathizing with "average" programmers with limited resources?

If angular were produced by superior engineers, it would be easier, not harder, for lesser engineers to grok it.

The problem is not with you, but with a those that made angular more complicated than it could have been.

Re: Stepping Backwards from AngularJS to JQuery – An Experiment

#15

Post by bdcravens »

pbreit wrote: post #6

Caveat: novice programmer here. Even Angular is still difficult for me to grok and sometimes I wonder if stuff that comes out of Google "suffers" (for me) from Google having unlimited resources and employing superior engineers? Would Google have a difficult time empathizing with "average" programmers with limited resources?

For Angular 1, I'd recommend sitting through Dan Wahlin's hour intro to Angular. Don't code, just watch. It really helped me get that initial chunk of knowledge in my head.

https://www.youtube.com/watch?v=i9MHigUZKEM

Re: Stepping Backwards from AngularJS to JQuery – An Experiment

#16

Post by quantumhobbit »

andybak wrote: post #5
carsongross wrote: post #2

Giving up Angular did force me to think more about the DOM. Vanilla jQuery doesn't insert itself as readily into HTML code as an Angular directive can. And that's why you should use http://intercoolerjs.org for most of your stuff, and a bit of jQuery where necessary for more exotic UX needs. The people who got sick of a mess of jQuery code were right, but they went the wrong direction to fix it. We have to go back. I…

I am personally fully behind your shilling and try to shill on your behalf whenever possible. It's sad how little interest intercooler has managed to garner when it's a fantastic antidote to so many things that are wrong with client-side development. I recently used a touch of intercooler on a Django project and it just felt so right. Once I'd included intercooler.js itself, everything else was done via normal http a…

Keep shilling. I had never hard about it until now. I love the simplicity.

We need more libraries that just do one thing well instead of kitchen sink frameworks like angular.

Re: Stepping Backwards from AngularJS to JQuery – An Experiment

#17

Post by asciihacker »

carsongross wrote: post #2

Giving up Angular did force me to think more about the DOM. Vanilla jQuery doesn't insert itself as readily into HTML code as an Angular directive can. And that's why you should use http://intercoolerjs.org for most of your stuff, and a bit of jQuery where necessary for more exotic UX needs. The people who got sick of a mess of jQuery code were right, but they went the wrong direction to fix it. We have to go back. I…

Intercooler.js is quite cool.

Re: Stepping Backwards from AngularJS to JQuery – An Experiment

#18

Post by ariabuckles »

pbreit wrote: post #6

Caveat: novice programmer here. Even Angular is still difficult for me to grok and sometimes I wonder if stuff that comes out of Google "suffers" (for me) from Google having unlimited resources and employing superior engineers? Would Google have a difficult time empathizing with "average" programmers with limited resources?

I've run into a lot of people who found angular hard to pick up; it's not just you.

One of them now works on the React team, and I found it pretty easy to pick up from the official docs: https://facebook.github.io/react/ . I recommend not bothering with stuff other than the base react library at first (although jsx/babel is nice); you can use react without it and potentially learn that later.

It's also totally valid to just start with basic js/html/jquery. The Mozilla's MDN docs for most html/js things are decent, and jQuery's api docs are pretty good in my experience.

Re: Stepping Backwards from AngularJS to JQuery – An Experiment

#19

Post by asciihacker »

pbreit wrote: post #6

Caveat: novice programmer here. Even Angular is still difficult for me to grok and sometimes I wonder if stuff that comes out of Google "suffers" (for me) from Google having unlimited resources and employing superior engineers? Would Google have a difficult time empathizing with "average" programmers with limited resources?

Angular is difficult to grok because it makes computer programming second class and limited to what you can cram into HTML tags.

Angular isnt really a Google product - Misko Hevery and another guy (both Google SW Engineers) developed in their free time.

Dart is a Google product and I would say is much easier to grok than Angular.

Re: Stepping Backwards from AngularJS to JQuery – An Experiment

#20

Post by beebs93 »

jnbiche wrote: post #7

Next time, try dropping jQuery, too, and just using vanilla JavaScript. Just for fun. Simple DOM manipulation is now as simple in vanilla JavaScript as jQuery, with the only big advantage jQuery has now is if you're animating. You may find you're not missing much. You'd have to get used to slightly more involved Ajax syntax, unless you can target only new browsers, in which case the `fetch` API is just as convenient…

> ...with the only big advantage jQuery has now is if you're animating.

While you can probably get away with using $.animate for very simple animations, you'll run into jQuery's animation performance problems before too long.

See: - http://wilsonpage.co.uk/preventing-layout-thrashing/ - http://velocityjs.org/

Post reply on HN