Notices by Rich Felker (dalias@hachyderm.io)

@n8 AWS margins are more like 95-99%/20x-100x markup.

@r I would think there'd be triggers made for use in contexts where there's a battery present too...

@r I mean the point is to avoid more junk to source & assemble & house safely. I have giant power diodes on hand and don't care about the loss, but for a published design I'd like to minimize BOM, so a good trigger module with integrated reverse protection (which is a lot simpler than fancy ideal diode made for use in settings with real AC components) would be nice.

@froztbyte @hipsterelectron You can't automate generation of contract from implementation.

Inline diode works as expected. It's a stupid & inefficient hack vs proper reverse current protection, but all that's practical to do without finding or making new PCBs. I'd love to find an off the shelf trigger module with builtin reverse current protection before publishing design tho. If anyone knows of one, let me know. (Boost for reach.)

@froztbyte @hipsterelectron Writing formal specs is hard and ppl are bad at it.

@hipsterelectron I don't follow. I think you need a declarative meta language defining contracts, not the language of the code, to do this. Unless the language itself has a type system that fully represents contracts (afaik no real world ones do) but even in that case it should be a separate subset of the language I'd think).

@hipsterelectron It'd get old really quick repeating that in every package. So you could have libraries of such specifications. And write dependencies on those libraries. Using a rigorous language to express what qualities the specifications you're depending on need to have, rather than referencing them by name...

What's that? Wha..? Oh. Oh. Oh....

@hipsterelectron Imagine having the full text of POSIX, but written in a rigorous manner with all ambiguities and contradictions fixed, embedded in your package file. 😲 Repeat for every third party dep that didn't even have a halfway decent contract specification to begin with. 😫

@hipsterelectron I think you're vastly under appreciating that doing this would be rigorously specifying the *complete* contract of the dependency, or at least the parts you want to depend on. Which is in some sense equivalent to implementing it yourself in an idealized high level language.

Hey the broligarchs didn't specific which "things" to break. 🙃

Move fast and break nazis' bones.

@alexsaezm My concept was that it's the same "storyline" (or more like "premise") as DOOM's, but Elon's asshats were the ones who opened up the gate to Hell trying to colonize Mars.

The origin story of the name X really needs to be constantly out there, because it makes him look so weird and whiny and pathetic and this is exactly how nazis hate to be perceived.

Also, somehow I only just realized SpaceX means "X, Space Department, but Thiel wouldn't let me call it X and I'm still bitter."

@mcc @sakurina I thought I understood the question but came to ask the same. Then went back and answered your question as best I could, not having identified with any of them, by which one upset me when something bad happened to them.. and guess I learned a small bit about myself at the time in the process, tho not sure if it has anything to do with what you were getting at.

@lanodan It's just MAP31 repeated 30 times.

Opening a portal to Hell is totally on-brand.

Hear me out.

DOOM, but with all the instances of "UAC" in the textures replaced with "SpaceX" or even just "𝕏".

@ekis I mean that's basically how we got the Y2K and Y2038 bugs, no?