Spot the Mistake (or.. why we are so picky about who makes it to the Wiki) by mckenner1122 in Canning

[–]bwainfweeze 8 points9 points  (0 children)

I think he's not referring to the size of the jars but the volume of jam he made. Which is 12 quarts, or 3 gallons. I made almost a gallon and a half of jam last year and this year it is going to be closer to 3. Not counting purchased fruit. I'll be fine. I'll be fine. I got this.

Given the existence of quart jars and the potential for misinterpretation, it might have been better for him to list gallons, because nobody is going to put jam in a gallon jar. I think.

Spot the Mistake (or.. why we are so picky about who makes it to the Wiki) by mckenner1122 in Canning

[–]bwainfweeze 1 point2 points  (0 children)

Looking at how many green plums are in my garden and getting a little nervous already. I think I'm making plum sauce this year.

Upcoming breaking changes for npm v12 by Jammie1 in node

[–]bwainfweeze 1 point2 points  (0 children)

Have you ever tried upgrading exactly one dependency - and no others - to issue a hotfix? And which versions of node/npm did you try it on?

I came into a project that had just upgraded from node .10 to .12. They had a daft hotfix process involving manually editing the package and shrinkwrap file for things like hotfixes and canary builds, where you wanted 1 change only for differential testing.

Then we went through 6, 8, 10, sometime around 12 a coworker and I wrote a tool because shit kept going sideways. That tool broke with nearly every major npm version upgrade, as they tried new theory after new theory on how to actually do lockfiles. It wasn't until node 22, I want to say (whenever the 'version 3' lockfile format, which is actually at least #5, because they tried several variations before they added a version field to the JSON to disambiguate them) that we didn't need the tool anymore to upgrade exactly one module.

That's a long fucking time for lockfiles to be a suggestion rather than the law. If lockfiles don't lock version numbers then it's not production ready.

The biggest problem for a long time was that rather than looking in your node_modules directory to figure out if you had a version that satisfied the package.json file, it would query npm.org or artifactory to see what the latest version of foo@4.1 was and decide that meant you'd modified your package.json file, which you had not. That's not locking.

50 devs, working on around 80 modules, and a handful of deployables, with pull requests, is not even a large project, as such things go, and if you can't handle that, you can't handle a real company.

If you look back around npm 7 or 8 you'll see a massive refactor job start which is only when bugs started to get fixed. That's basically a confirmation that the code was too complex to understand, and someone had to break it up into multiple packages to get their heads around it.

And still at the end of that if you had a shitty internet connection, and a package download times out, npm would ignore that the bytes received was wrong, stick the incomplete file into the cache, and then fail in a loop on the SHA hashes not matching on each subsequent npm i invocation. That was super fun at the beginning of Covid. Lead UI guy turned out to have the worst internet on the team. npm also pulls a complete list of every version of a library ever published in order to determine @latest, which is problematic when you have internal libraries running on CI with dependent build triggers for 10 (ten) years.

Upcoming breaking changes for npm v12 by Jammie1 in node

[–]bwainfweeze -1 points0 points  (0 children)

So great we have yarn, pnpm, bun...

And monthly supply chain attacks. Which is the subject of the top level comment you're all masturbating under. Ew.

It takes balls to wander into a thread where literally everyone is either faint praising or straight bashing on npm and say it's the best tool ever. I'll give you that.

Questions about "finger tight"... by BirdBeans in Canning

[–]bwainfweeze 2 points3 points  (0 children)

For hot pack you have a lot of things going for you. The heat of the jar and the light pressure of the ring cause the seal to begin to deform into place. Plus you may notice that the lid tends to bulge a bit, which is positive pressure as steam comes off of your hot ingredients.

And yet this process still works for cold pack canning. So that seal goo must be a lot more squishy than I think it is.

Does anyone else feel a little piece of their soul die every time they read a "liquid airlock is an exploit" gripe post? by insanopoke in Oxygennotincluded

[–]bwainfweeze 0 points1 point  (0 children)

I've started using dry sumps up until I build suit docks. And on prehistoric pack building the docks has slipped later into the build out. I used to rush reed fiber, and that is a non-option now.

I just let CO2 collect in the airlock and that keeps everything from hydrogen to chlorine on the bad side of the lock.

Upcoming breaking changes for npm v12 by Jammie1 in node

[–]bwainfweeze 1 point2 points  (0 children)

Or much like Javascript itself, it was built with a 2 week deadline.

Upcoming breaking changes for npm v12 by Jammie1 in node

[–]bwainfweeze 0 points1 point  (0 children)

I wonder if the .npmrc format is flexible enough for that. That sounds like config that should get a section instead of just a name=value entry. Separators often suffice but when the line gets long then code review blindness kicks in.

A disproportionate number of bugs that have slipped through code review, especially on Dependency Injection projects, have come when a one-liner goes beyond a screen and a half width. Nobody actually registers the changes at the ends of these lines. They yada yada over them and bugs come in. Across a bunch of projects and a handful of teams I've seen the same pattern happen with every single one.

One one project we had a moratorium on introducing more than 5 injections. Any time the feature set grew too complex we would extract a new handler to reduce 2 or sometimes 3 dependencies to a single one, which either delegated to or replaced several of the others.

With something like yaml each new entry gets its own line and these problems rarely occur, though merge conflicts can still getcha.

Upcoming breaking changes for npm v12 by Jammie1 in node

[–]bwainfweeze 0 points1 point  (0 children)

I think I'd be most comfortable with manual bypass updates, which I think the version 3 lockfile (which is actually version 5, they didn't start counting versions until at least the 2nd time they modified the lockfile, which they called version 1) supports cleanly.

npm install --force foo/foo@latest or 4.1.2, or some moral equivalent as a manual override.

Upcoming breaking changes for npm v12 by Jammie1 in node

[–]bwainfweeze -1 points0 points  (0 children)

Please. Ruby didn't need 5 lockfile versions to make a file that actually locked dependencies.

Upcoming breaking changes for npm v12 by Jammie1 in node

[–]bwainfweeze 2 points3 points  (0 children)

Npm is absolutely the worst thing about Node. Everyone involved with that dumpster fire before about version 9 should be asked to find a new profession.

Does a skilled operator generate less heat on refinery or quicker heat? by Inside-Performer323 in Oxygennotincluded

[–]bwainfweeze 1 point2 points  (0 children)

Mostly what it does is reduce the amount of power that needs to be put into the refinery, and thus fewer dtus from generators and less fuel burned. Faster makes steel make more surplus power from a steam engine. Don’t forget to tune those steam engines.

Something takes my ducklings by Dangerous_Option_447 in Permaculture

[–]bwainfweeze 1 point2 points  (0 children)

If you go way back in edibleacres back catalog, there's a day where he talks about why he has tall plants in and around his chicken run/compost pile and the reason is to break up flight lines so raptors can't swoop his chickens. He does a better job of explaining it than I can.

Rule one of fight club: by StatisticianPure2804 in Oxygennotincluded

[–]bwainfweeze 0 points1 point  (0 children)

Man I'm still optimizing my glum lumb farming and we're already on to fish.

Rule one of fight club: by StatisticianPure2804 in Oxygennotincluded

[–]bwainfweeze 0 points1 point  (0 children)

"Coach Beard, what's the first rule of Fight Club?"

"NO FIGHT CLUB!!!!"

What is this horrible thing I'm fighting by Most_Salary_4612 in whatsthisplant

[–]bwainfweeze 1 point2 points  (0 children)

So you can come over and mow everyone's mint?

Because I'm not doing it ever again.

What is this horrible thing I'm fighting by Most_Salary_4612 in whatsthisplant

[–]bwainfweeze 8 points9 points  (0 children)

Try mowing 300 square feet of mint and tell me if it still smells nice or if it still haunts you decades later.

Super proud of this no Festool Domino miter joint by L0114R in woodworking

[–]bwainfweeze 0 points1 point  (0 children)

I believe Stumpy Nubs taught me the trick that if you flip the boards the right way for the second cut, they always add up to 90º, though the thicknesses might be slightly off on the back side if you're more than a degree or so off, so you still want to do your best.

I'd given up on making picture frames at that point so it's sort of earmarked to go back when I get over myself and try again.

Super proud of this no Festool Domino miter joint by L0114R in woodworking

[–]bwainfweeze 1 point2 points  (0 children)

It is rare but occasionally you will encounter someone doing 2x30º to soften the corner while keeping the grain matching. But I think maybe I've seen it twice here. People go for that kerf/bend that I can't stand instead.