@kim Far as I can tell, most implementations *do* call this hashing (often something like "object hash" or "structural hash"), it's just not *cryptographic* hashing
Keep in mind the hopelessness you feel at times is the desired result of the capitalist society we exist in, so we don't fight it.
Every act we do, from calling it out to housing unhoused people and creating sustainable methods to how we feed each other, matters.
We are limiting ourselves if we fight how bigots fight.
And there are more of us than them.
@welshpixie Ah, one of Those Days
@wmd@chaos.social Here's another! https://www.google.com/maps/@51.7085689,5.3237457,3a,60y,269.06h,88.61t/data=!3m6!1e1!3m4!1sNP_gAPsNuIYhtfgA6g6H2Q!2e0!7i13312!8i6656
re: certified maia moment, ph bad (i am ok tho), idk what to cw this as tbh
@maia Ah okay, good to hear :)
re: certified maia moment, ph bad (i am ok tho), idk what to cw this as tbh
@maia No really, if you're experiencing symptoms from it, you should go to emergency services, even if you think you're fine, because clearly some threshold somewhere was exceeded
re: certified maia moment, ph bad (i am ok tho), idk what to cw this as tbh
@maia That's uh, basically a "go to emergency services NOW" kind of thing, AFAIK
@rune Likely Discord; it's most likely reprocessing a lot of state that it's unloaded from memory
@reinderdijkhuis @molly0xfff@mastodon.social Yeah, that was also the view I held, until I learned that "nazis recruiting" is actually far far more dangerous than "nazis existing"...
@maia Goals
@f0x Ooooof
@aral Oh yeah, sometimes you *do* actually need to clear the module cache for legitimate reasons, that's why I'm still seeing it as a deficiency in ESM. Just sharing the warning because this is something a lot of people aren't aware of, and most hot-reloading tools don't warn you about it :)
Personally I'm still stubbornly sticking with CJS and refusing to switch over to ESM, because of how broken and ill-designed ESM turned out to be - CJS is not going anywhere, too much of the ecosystem uses it and will never swap it out.
That having been said, I generally handle reload usecases by just restarting the process entirely (eg. via nodemon) or, in a browser context, LiveReloading the page; and working on some sort of (rudimentary) state persistence early in the development process.
It's a little more upfront work, but the resulting DX is honestly not that different from hot-reloading, and in the end I can trust the state to be consistent (ie. if I observe bugs, they are actually bugs, and not just a hot-reloading oddity).
In the process of moving to @joepie91. This account will stay active for the foreseeable future! But please also follow the other one.
Technical debt collector and general hype-hater. Early 30s, non-binary, ND, poly, relationship anarchist, generally queer.
- No alt text (request) = no boost.
- Boosts OK for all boostable posts.
- DMs are open.
- Flirting welcome, but be explicit if you want something out of it!
- The devil doesn't need an advocate; no combative arguing in my mentions.
Sometimes horny on main (behind CW), very much into kink (bondage, freeuse, CNC, and other stuff), and believe it or not, very much a submissive bottom :p
My spoons are limited, so I may not always have the energy to respond to messages.
Strong views about abolishing oppression, hierarchy, agency, and self-governance - but I also trust people by default and give them room to grow, unless they give me reason not to. That all also applies to technology and how it's built.