As the victim of the one from last year, it wasn't particularly fun to read.

The implication that I don't know what I'm looking at, or that I don't know what security is (despite having a clean track record for about 15 years now) was a bit aggravating.

In fact, even months later, the lasting effects have been panicking over anything that is remotely suspicious. The most recent example was just a few days ago. Had just gotten on the plane to go on vacation when someone Liked the original "I've been pwned" post on Bluesky. I misread the notification as being a new message to me saying "You've been pwned" and started to panick. I'd have had no way to address it and it would have ruined the small chance per year I get to have a break.

The attack last year wasn't me misunderstanding security. It was the sum of many, many small things (my history with and perception of npm especially w.r.t. their security posture and poor outreach over the years, being stressed out overall, and being in a rush at that particular moment, and a few other personal things) coming together in a perfect storm that resulted in the attack.

You don't really, but the entire ecosystem is quite ergonomic for people who don't want to fiddle with software, connections, config, permissions, etc. and Just Print something.

Not defending Bambu. The UX is quite straightforward and easy, however.

[citation needed]

I don't like go as a personal preference but reducing them to "fanboys" is a bit reductive. I'm sure the same could be said about your own favorite language.

Also as far as being civil: please watch literally any Rob Pike vibe chastizing Python and Java communities to no end. It is that rhetoric. That is why Go has fanbois. They can only see what the Gopher says and what Rob Pike says. Nothing else.

Other languages have fanbois but they didn't disparage and denigrate other communities to prove themselves.

Is it reductive when its describing a group of people that like something and refusing to hear any ill of it? The comment wasn't shade at people using the language in general.

And you're right, fanboys are in every language. But resorting to changing the argument by whataboutism is a bit reductive.

I’m not a go fanboy, but I do know from other contexts that so-called “fanboy“ behaviour is frequently associated with level-headed supporters getting defensive in the face of imprecise criticism.

There’s an oft-repeated pattern where valid specific criticisms morph into broad criticism, which morphs into judgement, which breeds defensiveness, which feeds the criticism. Once you recognise this pattern, you see it everywhere.

Thats the defensive step outlined above.

This is literally what mDNS is for. Didn't even know that it was a thing until I needed it for some custom firmware I was writing recently. It's like DNS but also has service port advertisements.

The productivity increase I get overall by not having to worry so much about if my rust code will work if it compiles tends to net faster iteration speeds for me. Compile times have never bothered me.

You are missing the forest for the trees here. The goal of that's unsafe isn't to prevent you from writing unsafe code. It's to prevent you from unsafe code by accident. That was always the goal. If you reread the comments through that lens I'm sure they'll make more sense.

> Your boundary is at hue 164, greener than 94% of the population. For you, turquoise is blue.

No, turquoise is turquoise!!1

I could imagine small companies that rely on these boards and that also have their fab and sourcing pipelines set up would be able to easier source these themselves. Just have to generate the Gerbers (fabrication output format most manus need) and then send it off as part of a larger order, etc.

Especially if you're able to replace certain small/passive components with those you already have in bulk, it could be a potential cost cutting measure.

Just a guess though.

For my case, they'd be useful if I wanted to know how certain subcircuits are designed or laid out.

Even for beginners, taking it into kicad, enabling the selection of only tracks and vias and deleting them all, then doing a full re-layout of the board as practice would be a cool project if you're wanting to learn.

All of my employers have let me specify my personal projects are mine. Maybe I've been lucky but I wouldn't work at a place that doesn't allow me my own life.

This is also something I try to ask for - generally I get the "that's fine" from the hiring manager and HR, but both times I've then had to push back and get it added to the actual supplied contract. And that was very much not easy.

And even then there's normally a "Sufficiently Different Sector" requirement for those personal projects - which makes sense, but it is inevitably worded vague enough that it would likely require going to court for pretty much any project to show it's not directly related. And that would be near prohibitively expensive for me as an individual if the relationship actually became adversarial.

Yes, but you have to declare them to the company and the company must approve them. If they don’t, because it’s competitive, you’re out of luck.

I’ve seen this done as a carve-out or exception that has to be explicitly documented. Trouble is that documentation is not presented as simple.