@[email protected] Edward Faulkner

With apologies to Dr. Seuss.

Literally an order of monks using Italian-made stone carving CNC machines to more efficiently carve beautiful cathedrals carmelitegothic.com/cnc-stone-carv…

Some personal news: I’m thrilled (and admittedly, somewhat surprised) to announce that as of Friday, @substack is now officially powered by @ghost! Keep reading for an exclusive behind the scenes look at the engineering around the launch of THE TWITTER FILES PT2: 🧵

Something that both “intro to programming” materials and chatgpt thoughleading gets wrong is misunderstanding what is hard about programming. People think that coming up with a code snippet is the hard part. It’s just… not. It only feels that way when you’re still a beginner.

@amatchneer … there’s not that function/component distinction, so you would have two different *components* each rendering the same tree of child components, but since the parents are themselves part of the components hierarchy, the component hierarchy isn’t stable.

@amatchneer But glimmer *does* have this property, and copied it pretty deliberately from react. The difference isn’t in how they do stability, it’s that in your react example you have two different functions returning the same tree of components. But in glimmer…

@luminousfinn @NeolithicSheep @cstross If he hadn’t, it would be easy for other instances to defederate with him.

@eaf4 @NeolithicSheep @cstross Yeah because asking people nicely not to act in a malicious fashion has a great track record of working. Glad the guy behind the thing proved to be a decent lad and took it down, but how many times do you think that'll prove to be the case?

@not_runspired @stefanpenner Constructing the different thenable is a synchronous action. It must be, or as you said we'd need to await and then the wrapping in Promise is unavoidable.

@not_runspired @stefanpenner If that's the behavior you want you can still have it by doing the synchronous work in a synchronous function, before passing off to an async one. Wanting a synchronous early exit from an async function is a misuse of async functions.

@not_runspired @stefanpenner But the async return case would not and that inconsistency would be pretty weird!

@stefanpenner @not_runspired ...the same effect by having a plain function to handle this case before invoking an async function for the work that actually involves awaits.

@stefanpenner @not_runspired One could imagine special casing async functions that return before ever awaiting, but that's a pretty weird exception to carve out (making "return" behave differently depending on whether somebody has added an await somewhere above it) and it's not needed because you can get...

@luminousfinn @NeolithicSheep @cstross Some instances might still have it cached in search results, but if anybody clicks on those to go look at it they fill find nothing but a "502 Bad Gateway".

@luminousfinn @NeolithicSheep @cstross Finally: the server that people are objecting to in this thread was ALREADY TAKEN DOWN as soon as it became clear people weren't cool with it. So the real story here is the opposite of what's being implied: the system worked, the mirror is no more!

@not_runspired @infinitsummer @dan_abramov Junior dev: oh wow, this one guy is building so much. Senior dev: uh oh, this one guy is building so much.

So, if we're not safe in there... behind closed doors... where they say they want us... we have no choice but to fight to make it safe everywhere, for all LGBT people.