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…
> 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…
Gov.uk drops jQuery from their front end
351–360 of 458 posts
Re: Gov.uk drops jQuery from their front end
#352Earlier quoted context omitted.
> I mean, you normally abstract these things with a helper fn or two, without importing the whole jQuery anyway. Add enough helper functions are you're at jQuery anyway. Looking at the jQuery source code, it manages a lot of edge cases that I don't really have time to figure out on my own. The DOM API isn't really designed that well for human consumption. https://developer.mozilla.org/en-US/docs/Web/API/Node/nodeTy..…
> Add enough helper functions are you're at jQuery anyway. I really hate these exaggerations. jQuery is, last I checked, over 200k unminified. Anyone writing enough helper functions to get to a fraction of that is already a pathological case.
It's kind of like how you can comparing languages using simple example code isn't relevant because proper code with full error handling and edge case handling can be very different from a naive example.
Re: Gov.uk drops jQuery from their front end
#353Earlier quoted context omitted.
Do you see a lot of age discrimination it tech? What I have seen is awkward situations where you have two developers of roughly equal competence. One happens to be 45 and the other 28. Fine, nobody would care about that. Except that due to automatic annual raises, job switches, seniority bumps etc, the 45 year old developer is paid twice as much as the junior. The rational response to this would be to say to align th…
If the 45-year old developer has been with the firm for 15 years, they may have roughly equal competence in writing code, but unless they spent the past decade with their eyes and ears closed, the 45-year old should have vastly more institutional knowledge. Seniority bumps, x-weeks-vacation-after-y-years-of-service reward that intangible.
Re: Gov.uk drops jQuery from their front end
#354Earlier quoted context omitted.
Creating an array, populating it with however many elements just to be able to call some methods and destroying it immediately afterwards. And doing it all over the app, just because it's syntactically convenient. (all while you already have an iterable collection in the form of NodeList)
It is a bit weird to consume an iterator into an array when a NodeList is already iterable. Not sure why it caught on.
Might also have something to do with Redux and immutable patterns. (the use of spread operator in general)
Re: Gov.uk drops jQuery from their front end
#355When 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…
> 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…
Re: Gov.uk drops jQuery from their front end
#356Earlier quoted context omitted.
So why describe him as a "greybeard" then? It are you claiming to have met many younger and/or female 'greybeards'? If your answer is that 'it's just part of the story'. Well that's precisely the complaint.
The meaning of "greybeard" have moved from being literally, to current be figuratively. It doesn't mean that the person is A) old, B) man C) have a beard and D) that the beard is grey. It simply means someone experienced/being at something for a long time. The greybeards at a company can be all women of the age 26, but if they been with the company for 5 years when the company got started 5 years ago, they are the gr…
Re: Gov.uk drops jQuery from their front end
#357When 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…
Re: Gov.uk drops jQuery from their front end
#358Earlier quoted context omitted.
So why describe him as a "greybeard" then? It are you claiming to have met many younger and/or female 'greybeards'? If your answer is that 'it's just part of the story'. Well that's precisely the complaint.
It's 2022. Men can get pregnant and women can have a beard. Greybeards is an inclusive term and it's a well known term.
Re: Gov.uk drops jQuery from their front end
#359Earlier quoted context omitted.
I rather not write 10 lines of Vanilla JS when I can write a line using jQuery. And I do prefer jQuery-style syntax for manipulating the DOM.
As somwone who constantly replaces jquey with vanilla js the difference is more like two lines of jquery against 3 lines of vannila js. One line more. But you have one dependency less, which is quite beneficial
var xs = document.querySelectorAll('.x');
for (var i = 0; i
jQuery: $('.x').on('click', function() { $(this).hide() });
ಠ_ಠRe: Gov.uk drops jQuery from their front end
#360Earlier quoted context omitted.
Though for that little work, I'd rather have a small local library that implements what I need over standard DOM & JS parts instead of the full weight of jQuery. Unless of course I need to support legacy browsers, then jQ is a no-brainer - that crap is solved there and I don't want to have to deal with it myself. And while jQ is large compared to my little home-grown set of wrappers, it is small compared to all the o…
There are tools like babel (even typescript) which can help you support older browsers.