If you were to write a TV series, would you prefer to create something entirely new, or adapt something you've already written - like Threshold (14 as season 1, The Fold as season 2, etc.)? Does the idea of adapting your work to screenplays interest you, or do you prefer writing novels?

Certainly true. I just wonder if it will add to confusion as to why some part of an app isn't working as intended as a result of a CSP that results in errors. There's some overhead there of an influx of help questions, GH issues, etc. and a need of comprehensive documentation of CSP.

It seems to me that nuxt.com/modules/secu... does a fine job of handling this for those that choose to opt-in. Not sure it needs to be in Nuxt core - other than if it's a desire to force all apps to be more secure by default.

Not too shabby!

I suppose in an ideal world an infinite scroll would be virtualized like github.com/Akryum/vue-v... - so you are only fetching and rendering the minimum necessary to display purely where you're at within the paginated array of objects.

Also would recommend looking through the latest State of JS report to see popularity / sentiment / adoption trends of what actual devs are using / liking reflected in real data: 2024.stateofjs.com/en-US/librar...

The vast majority of work is in Next.js (React), but my favorites currently are Nuxt (nuxt.com) which I am currently employed building in, and Astro (astro.build), which is sort of "build it with whatever you want" framework. HTMX is also gaining momentum as a "non-framework".

Highly recommend github.com/ajeetdsouza/... - makes jumping from repo to repo, and dir to dir so... much... faster.

Knowing the total items so you don't have to fetch if you have reached the end.

If you navigate away and back, being able to get directly back to exactly where you were in the scroll position.

If you navigated to a specific position, being able to infinitely scroll in either direction up or down.

I'd imagine @supports would allow you to apply the new properties as a progressive enhancement, and then you just include fallbacks to existing ones.

All functionalities being equal, it's still not as compelling as 'collapse' as a keyword for a single property. Do we really want new item-* properties only to leave all of the grid/flex variants intact as deprecated digital artifacts? At this point, though, whatever gets us to the finish line wins.

Which framework?

We’re all just some guy (or gal) sitting behind our computers. You happen to be some guy sitting behind your computer who has a *deep* understanding of CSS through practice and effort AND can translate and transfer that knowledge to others effectively! It’s earned and appreciated!

I'd love to use Nuxt DevTools inside the browser DevTools - right along Vue DevTools.

Astro also has a lot of attention to detail in its tooling, docs, and developer experience that should be lauded. It all depends on your actual application's use case and requirements. If I were starting an app from scratch, Astro would be a highly appealing choice.

I've been using Nuxt since 2017, and it's my framework of choice, but the sheer speed of having a fully server-rendered app and the tiniest amount of JS sent to the browser combined with View Transitions API makes Astro super-compelling. Plus, you can use any components you want. Vue. React. Svelte.