Aaron
@demello.dev
Reposted by Aaron
Preact Signals just got a huge performance boost:
Signals rendered as text/props & effects only "pull" as fast as needed for rendering. Since computeds run as-needed, they now only re-run as often as their downstream DOM output can be painted.
H/t to @jovidecroock.com for making this happen.
Signals rendered as text/props & effects only "pull" as fast as needed for rendering. Since computeds run as-needed, they now only re-run as often as their downstream DOM output can be painted.
H/t to @jovidecroock.com for making this happen.
January 10, 2025 at 6:50 PM
Preact Signals just got a huge performance boost:
Signals rendered as text/props & effects only "pull" as fast as needed for rendering. Since computeds run as-needed, they now only re-run as often as their downstream DOM output can be painted.
H/t to @jovidecroock.com for making this happen.
Signals rendered as text/props & effects only "pull" as fast as needed for rendering. Since computeds run as-needed, they now only re-run as often as their downstream DOM output can be painted.
H/t to @jovidecroock.com for making this happen.
Running into JSX type errors after upgrading #astro, make sure to upgrade your tsconfig’s excluded list to exclude dist, node_modules, and .astro folders. Then make sure you point React types to a specific version you support.
Spent too much time on this.
Spent too much time on this.
January 8, 2025 at 9:38 PM
Running into JSX type errors after upgrading #astro, make sure to upgrade your tsconfig’s excluded list to exclude dist, node_modules, and .astro folders. Then make sure you point React types to a specific version you support.
Spent too much time on this.
Spent too much time on this.
Getting #cursorai to auto run tests and fix failure has been awesome. Too bad it’s also pretty inefficient. It continues to repeat previous mistakes only to fix them on a second run.
Example: running a go test command, it seems to get the directory wrong on the first try and works on the second.
Example: running a go test command, it seems to get the directory wrong on the first try and works on the second.
December 31, 2024 at 3:31 PM
Getting #cursorai to auto run tests and fix failure has been awesome. Too bad it’s also pretty inefficient. It continues to repeat previous mistakes only to fix them on a second run.
Example: running a go test command, it seems to get the directory wrong on the first try and works on the second.
Example: running a go test command, it seems to get the directory wrong on the first try and works on the second.
Reposted by Aaron
Finally, the @preactjs.com team exposed as a bunch of shameless bloat peddlers!
(Check out the Standalone Preact Builder at standalonepreact.satge.net, it's really cool ✨)
(Check out the Standalone Preact Builder at standalonepreact.satge.net, it's really cool ✨)
December 20, 2024 at 9:45 PM
Finally, the @preactjs.com team exposed as a bunch of shameless bloat peddlers!
(Check out the Standalone Preact Builder at standalonepreact.satge.net, it's really cool ✨)
(Check out the Standalone Preact Builder at standalonepreact.satge.net, it's really cool ✨)
I love refactoring in Go. It's just a joy.
December 19, 2024 at 4:10 AM
I love refactoring in Go. It's just a joy.
Bsky feeds: would be nice to have a tweak setting
November 14, 2024 at 12:25 PM
Bsky feeds: would be nice to have a tweak setting
I have been looking into dynamic image generation after a long time. Last time I worked on something similar was back with PHP ImageMagick. It’s amazing what’s available now! Vercel’s Satori library looks awesome.
November 5, 2024 at 3:29 AM
I have been looking into dynamic image generation after a long time. Last time I worked on something similar was back with PHP ImageMagick. It’s amazing what’s available now! Vercel’s Satori library looks awesome.