The Brutal Lifecycle of JavaScript Frameworks

Post by jamra » Thu, Jan 11, 2018, 11:54 PM UTC

mythrwy wrote: post #53

jamra wrote: post #17

Earlier quoted context omitted.

I did that on a product as well. It went pretty well. The issue is with more complicated UI. The more complicated it is, the faster JQuery breaks down. That being said, it's better to have a bit of a spaghetti JQuery than to try and retrain unwilling programmers in Angular.

jQuery doesn't have to be spaghetti though. It gets that rap I think because most people that used it weren't good/experienced enough to organize bigger code. It can/usually does turn into a mess though but is faster to bang small things out in for me anyway.

Post by tvalentius » Fri, Jan 12, 2018, 1:27 AM UTC

scottmf wrote: post #109

sim0n wrote: post #108

Earlier quoted context omitted.

DOM APIs have much improved since jQuery first arrived, so while that was the case originally, it's become less true over time. It's definitely still less verbose though, for example: $('.my-component div').css({ background: 'yellow' }) vs. Array.from(document.querySelectorAll('.my-component div')).map(node => { node.style.background = 'yellow'; })

Why use map instead of forEach?

Post by esprehn » Fri, Jan 12, 2018, 5:42 AM UTC

sim0n wrote: post #108

lolive wrote: post #85

Earlier quoted context omitted.

I am not at all a front-end developper. But isn't jQuery the DOM API done right? [Which is a good thing, but only the beginning of the journey.]

DOM APIs have much improved since jQuery first arrived, so while that was the case originally, it's become less true over time. It's definitely still less verbose though, for example: $('.my-component div').css({ background: 'yellow' }) vs. Array.from(document.querySelectorAll('.my-component div')).map(node => { node.style.background = 'yellow'; })

  document.querySelectorAll('.my-component div').forEach(node => node.style.background = 'yellow');

Post by simooooo » Fri, Jan 12, 2018, 8:45 AM UTC

Post by mattmanser » Fri, Jan 12, 2018, 10:51 AM UTC

andrewem wrote: post #69

mattmanser wrote: post #67

Earlier quoted context omitted.

It's not the IP address that's the problem, it's that they're processing personally identifiable information about their users in a way they haven't asked permission for and is not related to the service they're providing. Here's the UK's ICO guidance for what you can process, as far as I can tell they've got no lawful basis for trying to match a user's IP address to a company without the user asking them to. https:/…

I skimmed that link and couldn't figure out what they mean by "processing". (It's related to compliance with a law, so I assume that the common sense meaning of a word isn't necessarily what is meant.) Do you understand what they mean by "processing" in this context? It seems like you're saying that analyzing IP addresses a user connected from in order to determine their likely employer is against the UK's GDPR guida…

    consent - there's no consent
    contract - it's not necessary to provide the Q&A answer site
    Legal obligation - there's no legal obligation
    Vital interests - nope
    Public task - nope

    Would individuals expect this processing to take place?
    Are some of the individuals concerned likely to object?
    Are you able to stop the processing at any time on request?