Griever

Correct. Nothing else comes close.

Personally I don’t mind them and sometimes find them quite tasteful. Fortunately a lot respect ‘prefers-reduced-motion’ these days.

Yup, thankfully most federate through InCommon so it’s less painful than it used to be, but that’s not saying much.

Great question. We rarely rely on shared utility classes these days. Historically we'd end up going the @apply route, but lately we just add a new style to the root-level css file and call it a day. We may prefix it with "@layer" so that it gets tree-shaken, but that's about it.

I've found that in component-driven UI, the need for these kinds of utility classes becomes less and less necessary. The utility CSS may be defined in the component, and the component is ultimately what gets reused.

Could you elaborate more on the reason for your interest? I've used Tailwind to implement several well-defined design languages, and always had great success. In fact, compared to other design systems, Material for example, I found it to be far simpler to manage over time.

I’m a strong advocate for Tailwind, and I believe that this approach is truly effective. In my experience, this subset of Tailwind has been sufficient for every project I've worked on that used it. Moreover, I've observed that it often converts skeptics into supporters.

Cyan (Myst developers) is still going strong. Their latest title Firmament is quite enjoyable!

A base price of $50k?! Not a chance.

Mostly echoing everyone else’s appreciation for the film in the thread. I was sucked in when I saw it the first time, and it’s one of the few movies I regret not seeing in theaters when it was available. If Alamo ever decides to do a special showing of it, I’d be there in a heartbeat.

It’s upsetting how as the years go on, I’m seeing more and more similarities to the world that the film depicts. But in a strange way, that makes the film all the more important to me.

To address your point about the lack of fragments: It's not as clean as React's implementation, but you can set a component to "ViewEncapsulation.None" to help address this.

Within a components template though, I frequently use <ng-container> to execute async pipes, or to perform simple conditional logic without adding unnecessary divs.

I was in a similar situation, and ultimately decided to reimplement the state management using NGXS. Fortunately the app was relatively small at that point, but I found that it held the developers hands a bit more, which lead to significantly more readable code.

Things can still get tangled up once you start using "ofActionDispatched" lifecycle handlers, but overall I found them to be far more manageable over time than NGXS.

I too can vouch for Tech Ingredients! Fantastic channel with some really interesting experiments on there.

The "Spec House" series is incredibly valuable if you're even remotely interested in building your own home. I'm incredibly excited to see how that series continues!

I consider Essential Craftsman to be one of the best YouTube channels out there. If you're interested in tools, construction or history in heavy industry, definitely give it a look.

Gmail now contains ads within each of the "category" tabs. Ad blockers seem to mostly block them, so that's most likely why you haven't seen anything.