Live data from Hacker News

Stepping Backwards from AngularJS to JQuery – An Experiment

hundredminutehack.blogspot.com

61–68 of 68 posts

Re: Stepping Backwards from AngularJS to JQuery – An Experiment

#61

Earlier quoted context omitted.

Can you give me your browser/OS combo?

Mac OSX El Capitan, Chrome 52

Heh, that's exactly what I'm using. It must be some settings. Do you see anything in the console?

Re: Stepping Backwards from AngularJS to JQuery – An Experiment

#62

Earlier quoted context omitted.

Mac OSX El Capitan, Chrome 52

Heh, that's exactly what I'm using. It must be some settings. Do you see anything in the console?

Yes: "intercooler-0.9.7.js:1507 Uncaught SecurityError: Failed to read the 'localStorage' property from 'Window': Access is denied for this document."

(As mentioned above, I have cookies and localStorage disabled via my browser settings.)

Re: Stepping Backwards from AngularJS to JQuery – An Experiment

#63

Earlier quoted context omitted.

Heh, that's exactly what I'm using. It must be some settings. Do you see anything in the console?

Yes: "intercooler-0.9.7.js:1507 Uncaught SecurityError: Failed to read the 'localStorage' property from 'Window': Access is denied for this document." (As mentioned above, I have cookies and localStorage disabled via my browser settings.)

Perfect. I'll try to get that fixed for the next release. History support won't work, but there is no reason that the rest of the examples shouldn't.

Re: Stepping Backwards from AngularJS to JQuery – An Experiment

#64

Earlier quoted context omitted.

Yes: "intercooler-0.9.7.js:1507 Uncaught SecurityError: Failed to read the 'localStorage' property from 'Window': Access is denied for this document." (As mentioned above, I have cookies and localStorage disabled via my browser settings.)

Perfect. I'll try to get that fixed for the next release. History support won't work, but there is no reason that the rest of the examples shouldn't.

Thanks, much appreciated (by me and others who like this simple/easy method to avoid cross-domain tracking on sites we're just browsing and not logging into).

Out of curiosity, what is it about intercooler's history support that requires localStorage? Can't it just use history.pushState? (I assume there's more robust functionality involved, but as I'm not yet familiar with how intercooler works figured I ask).

Re: Stepping Backwards from AngularJS to JQuery – An Experiment

#65

Earlier quoted context omitted.

Perfect. I'll try to get that fixed for the next release. History support won't work, but there is no reason that the rest of the examples shouldn't.

Thanks, much appreciated (by me and others who like this simple/easy method to avoid cross-domain tracking on sites we're just browsing and not logging into). Out of curiosity, what is it about intercooler's history support that requires localStorage? Can't it just use history.pushState? (I assume there's more robust functionality involved, but as I'm not yet familiar with how intercooler works figured I ask).

We snapshot DOM state so that when the user clicks the back button we can dump the old content back in. We stick it into localstorage.

It should be an opt-in feature, but if it is breaking the other examples that's an ugly bug.

Re: Stepping Backwards from AngularJS to JQuery – An Experiment

#66

Earlier quoted context omitted.

> Angular is difficult to grok because it makes computer programming second class and limited to what you can cram into HTML tags. ...say what? I've done a lot of work with Angular, and a lot of work without it, and it's possible that I might agree with what you're saying here if I understood it, but I don't. Can you elaborate?

I'm just saying that everything that Angular makes convenient via the hints it throws in HTML is handled behind the scenes by calling Javascript libraries. I would much rather the QooxDoo approach of writing apps in pure Javascript and using Javascript libraries instead of the HTML/JS/CSS soup that Angular tries to serve up to me as convenience. It might be more convenient for someone who cant write computer programs…

> I'm just saying that everything that Angular makes convenient via the hints it throws in HTML is handled behind the scenes by calling Javascript libraries.

Well, of course, but I'm not sure why this would be an issue. Earlier, less well implemented versions of Angular sometimes produced headaches this way. Current versions really don't. Considering the amount of boilerplate I find this saves me having to write and maintain - thus freeing me to spend effort on those parts of my application which are essentially complex, not just accidentally so - I find Angular a pretty clear win there.

Of course, maybe I just can't write computer programs, and my now almost two-decade-long professional career doing so is simply a preposterously unlikely fluke. Who knows?

Re: Stepping Backwards from AngularJS to JQuery – An Experiment

#67

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.

Wait a minute. So you've got a down on Angular for turning HTML elements and attributes into JS-driven behaviors, but you're fine with Intercooler, which does literally nothing but that thing? You confuse me, sir.

Re: Stepping Backwards from AngularJS to JQuery – An Experiment

#68

Earlier quoted context omitted.

Perfect. I'll try to get that fixed for the next release. History support won't work, but there is no reason that the rest of the examples shouldn't.

Thanks, much appreciated (by me and others who like this simple/easy method to avoid cross-domain tracking on sites we're just browsing and not logging into). Out of curiosity, what is it about intercooler's history support that requires localStorage? Can't it just use history.pushState? (I assume there's more robust functionality involved, but as I'm not yet familiar with how intercooler works figured I ask).

Fixed in dev, will be part of 1.0 release:

https://github.com/LeadDyno/intercooler-js/commit/1cd5809126...

Post reply on HN