84 points petecooper 1 hour ago 35 comments
kyleee 51 minutes ago | parent
hinkley 46 minutes ago | parent
The three biggest problems with JQuery UI:
1) The quality wasn't anywhere near as good as jquery, so many times I had to correct people whose opinion of jquery encompassed jquery UI
2) They declared bankruptcy on managing the call tree spaghetti and decided to rewrite the entire thing one component at a time, which meant that simultaneously some things were changing a lot and everything else they refused to entertain bug reports on the parts that were still in the queue.
3) It took them three times as long to do the work as they expected, and the original ask was already a bit much.
Angular became a thing before they finished the work.
simlevesque 41 minutes ago | parent
Unrelated, but it blew my mind when I learned that Elrond is half-man.
LVB 44 minutes ago | parent
askbjoernhansen 17 minutes ago | parent
frabjoused 51 minutes ago | parent
gosen 49 minutes ago | parent
squidsoup 49 minutes ago | parent
ddalcino 38 minutes ago | parent
There's a list of large legacy sites that use jquery behind that link, including:
* Microsoft.com * Pinterest.com * Adobe.com * Yahoo.com * Wordpress.org * Digicert.com * Samsung.com * Archive.org
buildwrangler 19 minutes ago | parent
maxpert 49 minutes ago | parent
Gualdrapo 46 minutes ago | parent
elondaits 43 minutes ago | parent
hirvi74 39 minutes ago | parent
bryanlarsen 19 minutes ago | parent
pjmlp 16 minutes ago | parent
whalesalad 46 minutes ago | parent
FAA ground stop: initiated
Microsoft 365: down
United Airlines: down
Github actions: down
Apple: down
Nvidia CEO: owned
Clandestine NSA network: down
jQuery: 4.1.0 released :)hinkley 37 minutes ago | parent
Now that ES and CSS5 are everywhere, the biggest feature of jQuery is list comprehensions on components. Data is also still good IMO but mostly the comprehensions.
jQuery decided that calling a function on an empty list should be a no-op, but my experience using it for a very interactive application was that nearly every time we wanted something to definitely happen or it was a bug, and the handful of times where an empty list was expected were easy to anticipate.
Because the general problem was that making a selector that continued to work correctly as features were added was a black art. Two of us wrote selectors that almost always worked, the rest of the team wrote ones that almost always broke and only very slowly onboarded our advice (also all of the stuff they already wrote was a ticking time bomb).
New features and especially tweaking the DOM tree to stay compatible with old corporate browsers would break existing functionality about a quarter of the time someone had to change the DOM structure to close a ticket and it was infuriating.
So what I want is that if .hide() is a no-op, throw an exception. And if I'm implementing the 'select all/unselect all' feature I know that the list might be empty, I can add a flag or wrap a conditional around it so I ignore the error.
Because those functions work on a very tight chunk of DOM that changes structure much much slower than the overall document structure, and also that code is quite close to the point of change if someone does change it, so has better chances of being remembered than something in the header.
FartinMowler 15 minutes ago | parent
Devasta 20 minutes ago | parent
hax0ron3 20 minutes ago | parent
jgalt212 16 minutes ago | parent
coredev_ 12 minutes ago | parent
__abc 9 minutes ago | parent