tried to collapse my argument from “jsx over the wire” into a few paragraphs. maybe this should be its own post? as a quick reference. [www.reddit.com/r/webdev/com...](https://www.reddit.com/r/webdev/comments/1khwk0v/comment/mrkeoai/ ) [gaearon's comment on "Static a...](https://www.reddit.com/r/webdev/comments/1khwk0v/comment/mrkeoai/ )
great tip if you’re running coding interviews (and good thing to be aware of as an interviewee) RE:
wut. clicking this image crashes the app on ios RE:
oh my god i just figured out how youtubers make speech believable despite gluing together separate takes, i bet they retry the last sentence to keep the flow intact and then cut off the repetition at the start so it flows seamless. signed, me who didn't think about this technique before
react flight was such a good codename. should've just kept that branding. (50% kidding)
this is important but tricky to talk about because it’s about delta of code over time. not “how it looks now” but “how will this feature request change the shape of my code” RE:
do people generally understand this or is it worth its own article? i can’t tell tbh RE:
i like many things about this one (maybe more than the original) but one of my favorite things is how they switched up the chord progression to be warm https://morel.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:fpruhuo22xkm5o7ttr2ktxdo&cid=bafkreicfyivsdrxjamhmju53b7f66ghxbf5wux55cwe2mfmgeobn3bbppy
it’s kind of obvious how this happened — export to web was bolted onto an existing product that doesn’t respect the web and doesn’t speak the web’s primitives. another way to approach this would be to introduce first-class web concepts (and limitations) into the editor. but that’s a lot more work. RE:
i was on a podcast! we talk about my recent “jsx over the wire” post, the separation between the backend and the frontend, and what React is doing and why RE: