Since I'm not otherwise productive today here's a thread on how my CSS preprocessor is going.

What happened to @codesandbox it's gone from a super convenient in-browser editor and scratchpad to a bloated mess that almost never works. I have completely stopped recommending or using it.

RT @diegozaks: I'm hiring designers for @tryramp. Who should I talk to? . If I hire them, your bonus would be enough to buy 50 @figma Cre….

hey @sebmarkbage hard to get find an answer for this, Will React ever start to mount a component, run a render, then bail without running effects? Suspense is involved. .

For no reason: found is a production ready SPA router that handles data fetching out of the box and with a TON of optional knobs to match your use cases

I resent that NextJs and @reactjs for forcing libraries to go add "use client" top the top of every file or deal will with a constant influx of GH issues from people telling me how lazy I am. I shouldn't need to opt out of new features in a minor react version for Next.

RT @nzgb: hiring frontend eng all levels @ dm me <3.

RT @zloirock: So, what's next?

A lot of opinions from folks who haven't built a web app for actual users in years. That's fine it's a valid perspective but would be great if some of the thought leaders were building the things they are trying to enable.

Does anyone know why frameworks like @nextjs, et all don't use HTTP2 push for priming client data fetches, instead of fetching the data and encoding it in/next to the HTML? Does it not work like that?.

Like i'm really trying to build a router that lets Suspense do all the annoying data loading tracking but nothing i can come up is better along multiple fronts, UX, DX, etc. it's either inflexible or spinner cascade city.

where "worse" means, less flexible, worse UX, or more bespoke apis' and patterns to do the same thing.

I keep trying to be open, but every example of using Suspense for data fetching I've seen seems worse than the version without it, for anything but trivial examples.

Hey @Twitter I liked the top tweets timeline, but it's indiscernible noise now. Every other tweet is from someone i don't follow or a topic i don't want to see. I want twitter to surface stuff I told it I care about, not guess.

My hungry fat cat is trying to open the bathroom door in order to better complain at me.

Saying this on endless repeat: folks using GraphQL without Relay are missing most of the benefits GQL can offer.

Do any of the popular or new SPA routers support code splitting by route as a first-class concept or just via lazy components? Does that approach allow fetching components in parallel with data?.

Please i'm begging every framework, stop making me use filesystem routing. It's cool for small things, it's absolutely unmanageable for more complicated apps. I'm happy to write a route config, just let me write a route config.

My excitement at New Bundler news is immediately tempered by needing to run a bunch of core tools as sidecars processes. which feels like a big step back. hopefully just a function of it being early still?.

Are there any SPA routing solutions that support rich page transitions like the new native page transition API allows? Where both route DOMs are on screen at once. Still seems like everyone punts on this….

What the hell @NJTRANSIT you can’t just cancel the RVL train and tell the packed platform to just get the next one in an hour.