Sven Slootweg (soft-deprecated) @joepie91@pixie.town

@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

@uint8_t@chaos.social Yes!

@maia Ah okay, good to hear :)

@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

@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

@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).

(ID&T Radio used to broadcast hour+ long mixes by serious DJs over FM in the Netherlands, but when they rebranded to SLAM!FM, it all changed to the standard format of "guy talking about bullshit and a bunch of ads interspersed with some EDM tracks")

It's interesting how SLAM! has been kinda redeeming itself lately with their mixes on YouTube... I remember the ID&T Radio days when it was still really good, and then it turned into a crappy vaguely EDM-y standard radio station, but now they seem to be going back to their roots again

@rune I... think so? I know very little about snaps and how they work (as I have a bit of a distaste for the "wrap it all into a container" approach to 'solving' package management woes)

@rune I think that popup is actually produced *by* the package manager? I've seen a virtually identical popup for other snaps

@dysfun@treehouse.systems Oh yeah, to expand on my earlier comment about teaching problem decomposition to programmers: my approach to teaching it is somewhat non-standard, in that I let students pick *their own* projects to work on, regardless of what its total complexity would be (explicitly stating that it's completely okay if they never actually *complete* it fully), and then help them break down their own project into smaller bits and pieces.

I do this instead of giving them 'example projects' because with their *own* projects, they would already fully understand all the details of what they want to achieve, so the only unknown is "how to approach it". If I used sample projects, they'd have to simultaneously understand (and probably misunderstand) what the goals of the sample project are.

Overall this makes it much much easier to learn problem decomposition because they 100% understand the frame of reference 100% of the time, ie. they have a stable base to work from, and so they can actually reason about the smaller pieces and why they're chopped up like that.

After doing that a few times, they eventually learn the patterns and how to identify sensible problem boundaries, and start being able to do it independently.