roblh
Joined 4 years ago
Joined 4 years ago
- “I made doom run with only css functions!”
- “CSS function vulnerability exposes api keys in NextJs server side rendering”
- “css function used for fingerprinting violates EU laws”
- “Facebook/Meta caught tracking users using CSS function exploit”
I’m being facetious, mostly.
That means you have to await the accumulator at some point before you return it, but anything you do before that call all gets fired off immediately. Then each invidivual iteration waits for the one before it to finish before finishing itself.
It's a pretty niche pattern, but it's a good way to make your coworkers do a double take while giving you quite a bit of control over exactly how it behaves. Similar to Promise.all, but more expressive I feel.
Also, an aside. I would love an image editor that would let you build your own chain of editing modules in an arbitrary order. Like audio plugins, with the ability to have more than one instance of each one.
I think that’s one of the things that’s jumped out at me in this latest slop wave from the last few weeks. Part of releasing meaningful software is the time investment by the creator is at least the barest of assurances that it’ll get some kind of support going forwards. Obviously not always, but the bigger the scope the more likely that is I think. If somebody spends 6 months on a project then it means it was worth at least 6 months to them and I believe there’s a higher chance they will continue to support it.
With stuff like this, it’s unusable and unmaintainable, and it got crapped out so fast that the creator has absolutely no emotional or personal investment in it beyond the token costs. I’m not suggesting every project needs a minimum amount of time spent on it, but it’s certainly a factor in how I judge software now, and choose what I want to interact with.