webdevladder

Higher friction and fragmentation are Fediverse features (not bugs) that give it a different grain. ATProto has different tradeoffs that lead to a different form of social media. I'm glad both exist, and bridging efforts are worth paying attention to for anyone frustrated with the distinctions.

You've missed the point, it's inherent in any serialized communication, and the gains are far greater than a type system. Protobuf and friends, and every type system in existence, pale in comparison to runtime capabilities and guarantees.

Full-stack rich schemas, not the poor lossy JSON Schema or other language-agnostic ones, are so nice for long-term quality and development velocity. You get to categorically avoid bugs that drag teams down. Zod 4, ArkType, and Valibot are all great.

I believe I was the target of employment-flavored spear phishing a few months ago. Could have been a researcher like the OP.

- 3 new email chains from different sources in a couple weeks, all similar inquiries to see if I was interested in work (I wasn't at the time, and I receive these very rarely)

- escalating specificity, all referencing my online presence, the third of which I was thinking about a month later because it hit my interests squarely

- only the third acknowledged my polite declining

- for the third, a month after, the email and website were offline

- the inquiries were quite restrained, having no links, and only asking if I was interested, and followed up tersely with an open door to my declining

I have no idea what's authentic online anymore, and I think it's dangerous to operate your online life with the belief that you can discern malicious written communications with any certainty, without very strong signals like known domains. Even realtime video content is going to be a problem eventually.

I suppose we'll continue to see VPN sponsorships prop up a disproportionate share of the creator economy.

In other news Google routed my mom to a misleading passport renewal service. She didn't know to look for .gov. Oh well.

Reminder that malicious impersonation is common and easily automated with LLMs.

Counterfactual invisibility is a real bummer.

Also the heuristic used to collapse file diffs makes it so that the most important change in a PR often can't be seen or ctrl-f'd without clicking first.

A more broad observation, I'm being pointed in the parent comment - web components need to win over framework authors. The signs are not trending well here from what I've seen consistently. That community is on X and web components are not addressing their problems and they're not used in optimal scenarios. I hope web components can win them over but they're mostly saying they've been a failure, arguably on balance bad for the web.

The point being made is that web components can pay this cost per-component, and this problem will compound over time. This is an unprecendented cost to frontend framworks and it's the expected usage pattern.

Look at the thread you've created here - I'm arguing that the article minimizes the antipattern cost they impose, and your response brings up React as if it somehow changes that.

You're ignoring page bloat as a performance cost. That's hugely impactful for UX on the web.

React is irrelevant for me and my users. This is not an argument in favor of web components over Svelte. Adopting web components would mean an objectively worse UX for my users - for example requiring them to enable JS.

You won't get a Svelte to look past the flaws of web components by saying "React is bad".

You can judge React, but like I said, not frontend. You're responding to an argument I didn't make.