Viewing profile — 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…

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, …

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 …

ArkType is a really interesting library that has a difficult time marketing itself. More than being a schema validator, it brings TS types into the runtime, so you can programmatic…

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…

Location: United States Remote: in-office/hybrid preferred, open to remote Willing to relocate: yes Technologies: TypeScript, Svelte, HTML/CSS/JS, Postgres, SQL/NoSQL, Node/Deno/Bu…

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 cons…

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…

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 - f…

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

As a Svelte user this argument rings hollow. You can't judge frontend by React and the way it's badly used.

I think this minimizes the fact that interop - the main selling point to me as a user - comes at a performance cost where every component you use could have its own unnecessary run…

This looks incredibly well-designed and documented, can't wait to watch some speed runs!

My experience tells me the opposite, it's an incredibly thoughtful and useful evolution IMO.

As a potential dev user this looks really intriguing, hitting all of the main points I was looking for. I build apps in this space, and the open source alternatives I've evaluated …

I tend to agree but I think toasts can still be useful and good UX. Putting useful and actionable feedback in context instead of toasts is a rule of thumb that I try to follow but …

I wrote this blog post about how Svelte 5 (currently a release candidate) uses signals to fix two problems with its former reactivity system that was introduced 5 years ago. If you…