This is an *excellent* summary of the tension between being welcoming to new contributors and staving off maintainer burnout. Because if there was a bug / deliberate nefarious thing hidden in that "innocent" 300-line refactoring patch, the maintainer's the one who's gonna be on the hook for it, not the contributor who may be long gone. :\

Whereas, if you take work *off* a maintainer's plate by doing a "thankless" task like improving docs or writing test cases, it's good things all around.

Yep. That is exactly the point of Codes of Conduct, so that **everyone** can just have fun and not worry about being harassed, berated, singled out for some immutable trait, and so on.

If having fun for you necessitates having the freedom to do this to other people, maybe carefully sit down and consider your life choices. ;)

Sometimes you're too immersed in things and forget what assumptions you're making! :)

I actually think the comment by Pseudonymous Powers at https://developers.slashdot.or... does a *fantastic* job of laying out some of those pitfalls, but to be more explicit, I've now added a new section towards the bottom of the article that itemizes them more explicitly: https://webchick.hashnode.dev/...

Hope that helps, and thanks again the candid feedback!

There isn't really any proof that Waymo vehicles are driverless, only that the driver isn't in the vehicle. If you compare a dozen dubiously driverless vehicles to a million collecting data every moment and already doing a pretty good job at autonomy, which do you think will succeed?

The fact that the driver is not in the vehicle does not mean that there is no driver.

I believe that this was figured out in the amateur observer community before NASA confirmed it. I saw it go by in my twitter feed. Not sure I can find it now...

Linear Energy Transfer

It's not radioactive. When high-energy particles strike it, they break apart into lower-energy particles that are more harmful. So, you need enough shielding to catch the particles that break apart in the top layer of your shielding.

While radiation mostly results in transient errors, it can also cause latch-ups that blow a gate off of the die. For rad-hard equipment in space this is mitigated by silicon-on-insulator fabrication, so that you can't have a latch-up between the substrate and a silicon feature.

We could have REAL ZOMBIES! YEAH!

:-)

I hear you. Going to be an interesting future, if we live.

Someone who broke their neck and was suffering from paralysis. You can control a chair or exoskeleton. People who can not hear today have cochlear implants, this is not all that different and might (eventually) work better. Or speak, or see. Other people who are disabled in various ways.

Oops. To continue: I'm just not seeing that it is so hard to access. But then, I use a Linux desktop, which has always come with a proper PDF renderer, there has never been a need to download "Acrobat".

Web pages use SVG to render vector graphics. It uses the exact same imaging model as PDF and is implemented in all modern browsers. The web in general has taken a lot of lessons from Adobe because Warnock and Geshke, in the PostScript Red Book, got so much right about how to build an image model that many GUI developers are still learning today. If you start with a PDF, it should be possible to machine-translate it to SVG and present it as a web page.

PDF exists because it is trivial to generate it from the document renderer meant for printing. Although I have once in a while run into an improperly scaled PDF meant to be printed 8-up, I'm just not

Lithium battery fires are in the news because they are new. There are many more gasoline fires every day.

Pistons? We don't need no stinking pistons! Next thing, they'll be adding a bridle and a bit!