Aaron
@demello.dev
From my hikes this weekends!
August 24, 2025 at 12:29 AM
From my hikes this weekends!
Yeah this is definitely what I love about typescript. Done right, it can provide an awesome developer experience.
March 2, 2025 at 3:00 AM
Yeah this is definitely what I love about typescript. Done right, it can provide an awesome developer experience.
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.
Attempting to go 0-100? I found no success with that. It’s the most successful when I’ve written code and I need help: transforming, refactoring and writing tests. It does better with having code context, but not amazing.
January 2, 2025 at 2:06 PM
Attempting to go 0-100? I found no success with that. It’s the most successful when I’ve written code and I need help: transforming, refactoring and writing tests. It does better with having code context, but not amazing.
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.
answer: cursor's rules for AI - though unless you have yolo commands enabled, you'll have to manually hit the run test commands.
December 30, 2024 at 8:28 PM
answer: cursor's rules for AI - though unless you have yolo commands enabled, you'll have to manually hit the run test commands.
I’m wondering if I just need an extension that runs the tests and surfaces the errors in the editor. It seems to be able to detect and fix lint errors without issue!
December 30, 2024 at 4:36 PM
I’m wondering if I just need an extension that runs the tests and surfaces the errors in the editor. It seems to be able to detect and fix lint errors without issue!
I would not say struggle, but it doesn’t seem to be using the context of previous tests well.
For example, I have a Go test that requires passing in a typed nil value instead of “nil” into some methods. It for some reason never picks that up on the first go in generating tests, always uses nil.
For example, I have a Go test that requires passing in a typed nil value instead of “nil” into some methods. It for some reason never picks that up on the first go in generating tests, always uses nil.
December 30, 2024 at 4:34 PM
I would not say struggle, but it doesn’t seem to be using the context of previous tests well.
For example, I have a Go test that requires passing in a typed nil value instead of “nil” into some methods. It for some reason never picks that up on the first go in generating tests, always uses nil.
For example, I have a Go test that requires passing in a typed nil value instead of “nil” into some methods. It for some reason never picks that up on the first go in generating tests, always uses nil.
The transformer use cases are the best, probably the most common use case for me with regard to LLM generated code. That and generating tests. But tests still need so much wrangling, even if I have context of previously written tests.
December 30, 2024 at 4:27 PM
The transformer use cases are the best, probably the most common use case for me with regard to LLM generated code. That and generating tests. But tests still need so much wrangling, even if I have context of previously written tests.
Only lately have I felt that this is probably very true. Hasn’t always been the case, I never used to think it mattered much before. But maybe the boring is now so ubiquitous!
December 28, 2024 at 9:29 PM
Only lately have I felt that this is probably very true. Hasn’t always been the case, I never used to think it mattered much before. But maybe the boring is now so ubiquitous!
This is what I assumed is happening (excluding the transform flag). For node-only code, shouldn’t this be better? No transpiling necessary. You write modern JS with types. Unless I am misunderstanding how this works.
December 28, 2024 at 4:25 PM
This is what I assumed is happening (excluding the transform flag). For node-only code, shouldn’t this be better? No transpiling necessary. You write modern JS with types. Unless I am misunderstanding how this works.
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 ✨)
This is pretty cool - love it.
December 22, 2024 at 9:37 PM
This is pretty cool - love it.
tailwindcss.com/blog/tailwin...
With tailwinds making it easier to style with “just css”, this make shadow dom style encapsulation less compelling to me. Less to wrangle with, and probably easier styling DX. I’ve yet to experiment though.
With tailwinds making it easier to style with “just css”, this make shadow dom style encapsulation less compelling to me. Less to wrangle with, and probably easier styling DX. I’ve yet to experiment though.
Tailwind CSS v4.0 Beta 1 - Tailwind CSS
After a long alpha period, we're excited to release the first public beta of Tailwind CSS v4.0.
tailwindcss.com
December 21, 2024 at 4:54 PM
tailwindcss.com/blog/tailwin...
With tailwinds making it easier to style with “just css”, this make shadow dom style encapsulation less compelling to me. Less to wrangle with, and probably easier styling DX. I’ve yet to experiment though.
With tailwinds making it easier to style with “just css”, this make shadow dom style encapsulation less compelling to me. Less to wrangle with, and probably easier styling DX. I’ve yet to experiment though.
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.
It’s amazing that things like this cause so much commotion. Yet things like easy foot guns people are less noisy about (e.g crazy reactive hell in previous svelte versions had. Or react hooks…). Build large code bases with various exp levels, then these seem like such nonissues.
December 19, 2024 at 2:31 AM
It’s amazing that things like this cause so much commotion. Yet things like easy foot guns people are less noisy about (e.g crazy reactive hell in previous svelte versions had. Or react hooks…). Build large code bases with various exp levels, then these seem like such nonissues.
I think you guys got the price point right on. Loving the ad free experience.
December 4, 2024 at 12:34 AM
I think you guys got the price point right on. Loving the ad free experience.
So who, in your opinion, does this well?
November 30, 2024 at 1:21 AM
So who, in your opinion, does this well?
Splitting out products makes sense to me. But something like forcing an open access API, that seems off - I’m not sure why. Something about forcing companies to grant access to user generated data feels off.
November 20, 2024 at 1:38 AM
Splitting out products makes sense to me. But something like forcing an open access API, that seems off - I’m not sure why. Something about forcing companies to grant access to user generated data feels off.
Had that same feeling when building an email viewer component! Shadow dom encapsulation made style isolation a lot simpler. Of course, it broke other things (like custom fonts :))
November 17, 2024 at 3:48 PM
Had that same feeling when building an email viewer component! Shadow dom encapsulation made style isolation a lot simpler. Of course, it broke other things (like custom fonts :))
Is there a market for AI services that upgrade these apps to modern versions? I feel like the cost to make such an upgrade might be significantly reduced. Cheaper than a specialized dev!
November 17, 2024 at 3:52 AM
Is there a market for AI services that upgrade these apps to modern versions? I feel like the cost to make such an upgrade might be significantly reduced. Cheaper than a specialized dev!
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