Gov.uk drops jQuery from their front end

Post by moffkalast » Thu, May 19, 2022, 7:47 PM UTC

icedchai wrote: post #115

SemanticStrengh wrote: post #65

Earlier quoted context omitted.

I really don't get this discourse, jQuery API is much more ergonomic, concise and clearer than the DOM api. Sure you can do it but that doesn't mean you should

Yes, the DOM API is painful to work with.

Post by tinco » Thu, May 19, 2022, 7:53 PM UTC

SEJeff wrote: post #241

reggieband wrote: post #137

When I first started programming I was pretty lucky to get a job at a games company. My first lead was a veteran who had shipped a lot of AAA titles and he loved his war stories. He was personally interested in performance and he would often cite hardware timings for specific cpu instructions. One story he told a couple of times was about some grey beard who was before his time. The grey beard was once a legend in th…

Amusingly, I always joke that I'm fluent in jQuery, but no absolutely no javascript. As a mostly backend go/python/non-javascript developer that has always held true. It is just a tool in the belt for an engineer. Can you use jQuery in 2022 or later to solve really amazing problems that impact user experience? You sure can! Would you be better off to use a modern javascript variant and stuff like react instead? You a…

Post by moffkalast » Thu, May 19, 2022, 7:55 PM UTC

d1sxeyes wrote: post #82

err4nt wrote: post #71

Earlier quoted context omitted.

There is .forEach() on NodeLists, so you can do stuff like this in every browser, no lib, no helper functions needed: document.querySelectorAll('a').forEach(tag => { // operate on tag })

I think it's just for brevity, rather than because a helper is needed . OP listed the entire source code of their module in their comment.

    document.querySelectorAll('#rabbit .green').forEach(tag => {
      
    })

    for (const rabbit of dqsA('#rabbits .green')) {

    }

Post by zimpenfish » Thu, May 19, 2022, 7:56 PM UTC

CraigJPerry wrote: post #186

zimpenfish wrote: post #169

Earlier quoted context omitted.

That's not exactly the same, I don't think, because jQuery will give you all the `ul` that are closest to `.sth`, not just the first. You'd have to write a loop over the list returned from `document.getElementsByClassName('sth')` to get the same behaviour (because it doesn't look like the standardised `closest` works on lists.)

If i'm following right, i think this expression would match? Array.from(document.getElementsByClassName("sth")).map(e => e.closest("ul")) The jQuery is definitely nicer to read than this though

Post by giobox » Thu, May 19, 2022, 7:58 PM UTC

armchairhacker wrote: post #280

dlandis wrote: post #234

Earlier quoted context omitted.

> But to me, they are like the old grey beard who didn't update his knowledge as the times changed. Maybe it's just me but with all the rampant age discrimination nowadays in tech, I really don't like to see the continued propagation of this stereotype. All sorts of people of all ages are unwilling or unable to update their knowledge of new tech, there is no reason to link this characteristic to someones advanced age…

I sympathize with older devs, my dad is an older software dev. But you kind of do have to be old in order to have outdated knowledge: nobody young is going to learn assembly tricks which worked on MIPS and other past architectures. Older devs and companies not constantly learning new things and updating to best practices is a real phenomenon. On the other hand, anecdotally most older developers actually do keep up to…