@QuinnyPig Isn’t this all kinda pointless anyway since they’re still controlled by US corporations? Are any of them really actually “sovereign” in a meaningful sense, or is this just marketing?
@matteocollina@nodejs Are you able to share clear repro steps? I tried feeding that sample payload to an app of mine and I did not get a stack overflow or a crash - it was just rejected by Express - so I’m not sure what I’m missing or whether I’m affected
Fiscal rules are relatively new. They didn't exist until the Maastricht Treaty in 1992. They spread across the globe following neoliberal politics. They are purely political in nature and are not based on any solid economics.
@simonw@obie I care a lot about how individual choices will lead to understandability and malleability over time
I tend to work on long-lived software owned by small teams
I’m not entirely anti-coding-agent, but I struggle to justify spending the time to really invest in learning the tools
@mitsuhiko We use ULIDs and this is a major reason I dislike them
Imo, much like UUIDv7 they’re too big, don’t fit into URLs nicely, and aren’t recognizable enough
Back when we just used autoinc you got to know the numbers for your most pathological customers - that’s much harder now
@simonw@mitsuhiko And it hasn’t even improved at being internally consistent within a page! Which is one of the core principles of react data architecture!
@ProCyclingStats the design tweaks look nice, especially on mobile - but I ran into a small bug:
When filtering by team you don’t get the actual times anymore, you just get “ for everyone unless they were at the front of a group
@bostonou I’ve hit 100% of my deadlines in the last decade, it’s not that hard.
The key is that almost none of my work has real deadlines, but when it does, we take them seriously
@csswizardry@ChaponFlo That’s the idea, yeah - most releases should only touch a few files, and it tries to group them together through some heuristics
node_modules should change rarely, for example
@csswizardry@ChaponFlo When configured correctly, webpack splits the bundle into a number of “chunks” each chunk contains a bunch of source files, and has its own name and hash.
The idea is then that any change only invalidates a subset of chunks
@csswizardry A correctly configured bundler is supposed to put the same files into the same named chunks, so most releases shouldn’t modify most chunks