Nothing against React Suspense here, but… y’all realize that waiting a set delay before showing a loader is do-able with just a few lines of CSS, right?
I wish everybody arguing about the cascade (on both sides) understood the difference between cascade & inheritance, and was more explicit which one they mean when.
The lack of clarity is certainly not helping the discussion.
I have made a cocktail with London dry gin, lemon juice, and habanero cucumber syrup. And it is one of the best drinks I've ever created.
Currently chewing on this idea:
Many frustrations with CSS come from unexpected behavior when we ask it to do conflicting things. Part of this stems from not fully understanding the default behavior, and how our code might fight against that.
Building a React SPA with a top-level App component, routing, centralized application state, & API data fetching.
And it renders to static HTML and works without JavaScript.
The whole “docs vs. apps” thing is nonsense
Giving next.js a try
Typed up several new drinks & added them to Sidecar over lunch. Check out the lemon bomb!
https://sidecar.us/drinks/lemon-bomb/
When one browser dominates the market, bugs become features and open standards take a back seat. When IE6 became the dominant browser, we had to live with the consequences for a decade.
It is certainly plausible that Microsoft just doomed us to another decade of fallout.
We finished a re-watch of all six seasons of Community last night (though it was our first time seeing season 6, since it originally only appeared on a weird Yahoo streaming service). Such a phenomenal show. And the final episode was the perfect way to end it.
I still say there’s something fundamentally wrong with our food distribution practices when one outbreak/incident means the entire country has to beware an entire product.