*caveat I have only built _one_ full Solid app to production grade and it also needed a sync engine (Zero) Love Zero, but admitting bias here that my experience is with complicated applications and this could be skill issue + types of problems I'm working on. YMMV.

Show Post

The complexity feels like a natural consequence of the scale of problems we're trying to solve. But if we want the web to succeed, we should continuously ask ourselves if our solutions are actually helping developers succeed.

Show Post

This comes back to the reason I have, in the past year, started gravitating away from modern TS frameworks. It is hard to see how complex it is when you're deep in it every day. When you have to take a step back and work with developers trying to build stuff on undisciplined teams, it falls down.

Show Post

My goal right now is to help more intermediate developers (across the stack) build better software on the web. Much is education: folks not understanding the tradeoffs and pitfalls, using abstractions they read about on LinkedIn for the wrong problem, not understanding the web as a platform, etc.

Show Post

IMO it is in the best of current TS frameworks. I raved on release about the consolidation of the metaframework into the framework. My main complaint is abstraction complexity and onboarding. Solid2 feels like a framework targeted at people who are already experts in modern JS frameworks.

Show Post