Parece que con AV1 se puede hacer de todo. Tenemos:

1. AVIF para las imágenes individuales
2. AVIFS (la S es de Stream) para secuencias de imágenes
3. MP4 para vídeos, pero usando AV1 de codec (en vez de p. ej. H264).

Sería top si se pudiese sincronizar AVIFS con la API de Scroll Driven Animations

Respecto a esto último – permitiría efectos como el de esta página en móvil al hacer scroll, sin necesidad de JS:

www.apple.com/es/airpods-p...

Respecto a esto último – permitiría efectos como el de esta página en móvil al hacer scroll, sin necesidad de JS:

www.apple.com/es/airpods-p...

Parece que con AV1 se puede hacer de todo. Tenemos:

1. AVIF para las imágenes individuales
2. AVIFS (la S es de Stream) para secuencias de imágenes
3. MP4 para vídeos, pero usando AV1 de codec (en vez de p. ej. H264).

Sería top si se pudiese sincronizar AVIFS con la API de Scroll Driven Animations

@manz.dev

Nevermind

Out of curiosity, do you think there’s a way to make selection only wrap the individual characters?

Fantastic idea of using the monospace character width with a repeating gradient.

(2/2)
To see that something I fully made works and is valuable to someone is one of the things that makes me keep pushing hard when I need it the most.

Additionally, if I can set env vars for functions, why do I have to run hacks like this when I want to run an edge function from a SQL trigger or function?

stackoverflow.com/questions/78...

I'd be begging for a leaner DX on this matter..

A better approach for calling edge functions from SQL code that also plays nice for local dev.

And a helper for sending user auth from a SQL trigger to an edge function. Like, seamless RLS all the way through.

Don't know if I'm explaining myself well at all, feel free to ask me to elaborate.

relevant (meme by @shenanigansen.bsky.social)

Una pena que no pusieran #Unmusking de hashtag…

(4/4)
Other than this, it's been an outstanding DX everywhere else, making it a competitive choice for "codebase-first" projects where the ORM defines the DB.

I'm now switching to @kysely.dev, which provides first-class introspection support and type-safe SQL. Not an ORM, yet still very promising.

(3/4)
As of now, this is only documented in the release note that features it. github.com/drizzle-team... . (Please, add this to the docs!)

These aren't still referenced when introspecting, which means the generated schemas and relations have to be patched each time you apply a new migration.

(2/4)
It also keeps generating its own migrations and adding them to a "drizzle" schema, which doesn't align with keeping the database as the source of truth.

There have been some efforts to improve support, such as a new `drizzle-orm/supabase` import that includes predefined Supabase intrinsics.

Looks so clean and appealing! A shame it's not supported in FF yet, though 😕

Does anyone know if there are any polyfills available for this property?

To end, we have a fantastic community dinner and swag party with current and old people from different GSoC organizations, including alumni, mentors, admin, and world managers. Here our Mr Worldwide mascot had a cake-like appearance

6 mentors from our community travel a total of 10.000 kms to attend and collaborate, including Víctor Carreras (Flutter), Mario_Ezquerro (GDE Cloud), IreneRuizPozo
(WTM), Moisés Martínez (GDE AI), @oxca.be (code) and me (admin at the LG project)