Ray Thurn Void
@ray-thurn-void.bsky.social
Dev ❤️ Svelte, Deno ⚔️ Bun, 💻 Cursor @ sybill.ai
TS becoming an official "first class target" nice!
They should also rename remix 3 to remix TS honestly 😅
They should also rename remix 3 to remix TS honestly 😅
November 3, 2025 at 10:33 PM
TS becoming an official "first class target" nice!
They should also rename remix 3 to remix TS honestly 😅
They should also rename remix 3 to remix TS honestly 😅
A common UI challenge is to show tooltips only if text is overflowing (when using ellipses)
November 3, 2025 at 10:27 PM
A common UI challenge is to show tooltips only if text is overflowing (when using ellipses)
Where is runed 😱
October 2, 2025 at 9:24 PM
Where is runed 😱
But none of these people (the trusted ones like Jared Summer, Ryan Florence, Theo, etc.) uses VSCode Copilot.
Somehow copilot performs very bad at gathering and managing context I guess.
Most of the people use Cursor or Claude Code.
Somehow copilot performs very bad at gathering and managing context I guess.
Most of the people use Cursor or Claude Code.
September 1, 2025 at 11:24 AM
But none of these people (the trusted ones like Jared Summer, Ryan Florence, Theo, etc.) uses VSCode Copilot.
Somehow copilot performs very bad at gathering and managing context I guess.
Most of the people use Cursor or Claude Code.
Somehow copilot performs very bad at gathering and managing context I guess.
Most of the people use Cursor or Claude Code.
i want to try so bad!
btw is this a doc error?
shoudn't this be post.current instead of post.content?
btw is this a doc error?
shoudn't this be post.current instead of post.content?
August 1, 2025 at 12:08 AM
i want to try so bad!
btw is this a doc error?
shoudn't this be post.current instead of post.content?
btw is this a doc error?
shoudn't this be post.current instead of post.content?
Yeah I have the same in cursor, to workaround when I already know it might fail I ask it to re-read the files because I did some changes.
July 23, 2025 at 8:47 PM
Yeah I have the same in cursor, to workaround when I already know it might fail I ask it to re-read the files because I did some changes.
They are like bun I suppose, they do not make money, we'll see what they both do to monetize in some years. They need a huge user base now.
July 23, 2025 at 1:50 AM
They are like bun I suppose, they do not make money, we'll see what they both do to monetize in some years. They need a huge user base now.
Nice discovery, I feel I can trust them because they openly says humans are involved.
There's now way in the current state you can give tests to AI alone.
And they probably hire in India/Pakistan so they act as an HR company for you lol
There's now way in the current state you can give tests to AI alone.
And they probably hire in India/Pakistan so they act as an HR company for you lol
July 17, 2025 at 9:31 PM
Nice discovery, I feel I can trust them because they openly says humans are involved.
There's now way in the current state you can give tests to AI alone.
And they probably hire in India/Pakistan so they act as an HR company for you lol
There's now way in the current state you can give tests to AI alone.
And they probably hire in India/Pakistan so they act as an HR company for you lol
The only thing that is stopping me from writing svelte is that blocknote and assistant-ui are only for react.
The idea of porting them is always there but I must focus on 1 thing at a time lol.
The idea of porting them is always there but I must focus on 1 thing at a time lol.
July 10, 2025 at 9:20 PM
The only thing that is stopping me from writing svelte is that blocknote and assistant-ui are only for react.
The idea of porting them is always there but I must focus on 1 thing at a time lol.
The idea of porting them is always there but I must focus on 1 thing at a time lol.
Many AI products will be replaced by Open Source counterparts, or by companies that will wrap a marketing campaign around Open Source stuff that powers their products.
July 10, 2025 at 9:18 PM
Many AI products will be replaced by Open Source counterparts, or by companies that will wrap a marketing campaign around Open Source stuff that powers their products.
Yeah 100% whoever is spreading the idea that you can replace thinking with AI is because is selling his "AI" product.
To me AI always was about setting up patterns to speed up repetitive parts of dev, and brainstorming, even If AI responds with wrong stuff it helps you to have better intuitions.
To me AI always was about setting up patterns to speed up repetitive parts of dev, and brainstorming, even If AI responds with wrong stuff it helps you to have better intuitions.
July 10, 2025 at 9:14 PM
Yeah 100% whoever is spreading the idea that you can replace thinking with AI is because is selling his "AI" product.
To me AI always was about setting up patterns to speed up repetitive parts of dev, and brainstorming, even If AI responds with wrong stuff it helps you to have better intuitions.
To me AI always was about setting up patterns to speed up repetitive parts of dev, and brainstorming, even If AI responds with wrong stuff it helps you to have better intuitions.
Wow if you can find some unit tests on GitHub of other lower quality libraries you can copy ask Claude to adapt them to your code.
Ai is great at: do the same thing of this but with this style/format/differences
Ai is great at: do the same thing of this but with this style/format/differences
July 9, 2025 at 9:31 PM
Wow if you can find some unit tests on GitHub of other lower quality libraries you can copy ask Claude to adapt them to your code.
Ai is great at: do the same thing of this but with this style/format/differences
Ai is great at: do the same thing of this but with this style/format/differences
I'm disappointed that they are useless lol!
I've been working on highly functional teams that had no rituals and processes and in very inefficient ones that have lot of PR reviews, processes a s coding philosophy.
I learned that the only thing that matters is ship code with people that have fun.
I've been working on highly functional teams that had no rituals and processes and in very inefficient ones that have lot of PR reviews, processes a s coding philosophy.
I learned that the only thing that matters is ship code with people that have fun.
July 8, 2025 at 9:45 PM
I'm disappointed that they are useless lol!
I've been working on highly functional teams that had no rituals and processes and in very inefficient ones that have lot of PR reviews, processes a s coding philosophy.
I learned that the only thing that matters is ship code with people that have fun.
I've been working on highly functional teams that had no rituals and processes and in very inefficient ones that have lot of PR reviews, processes a s coding philosophy.
I learned that the only thing that matters is ship code with people that have fun.
Yes it looks amazing!
The only thing I hate of boundaries/suspense in react is that you have to wrap your component in them, so the fallback UI has to be in parent rather than in the component itself.
It would be cool to have a way to show fallback UIs by defining them in the component itself.
The only thing I hate of boundaries/suspense in react is that you have to wrap your component in them, so the fallback UI has to be in parent rather than in the component itself.
It would be cool to have a way to show fallback UIs by defining them in the component itself.
July 5, 2025 at 2:24 AM
Yes it looks amazing!
The only thing I hate of boundaries/suspense in react is that you have to wrap your component in them, so the fallback UI has to be in parent rather than in the component itself.
It would be cool to have a way to show fallback UIs by defining them in the component itself.
The only thing I hate of boundaries/suspense in react is that you have to wrap your component in them, so the fallback UI has to be in parent rather than in the component itself.
It would be cool to have a way to show fallback UIs by defining them in the component itself.
The promise is ignored in useEffect as well no? The real diff is useEffect triggers when state changes while event handlers trigger when the user interact with the ui
July 3, 2025 at 3:50 PM
The promise is ignored in useEffect as well no? The real diff is useEffect triggers when state changes while event handlers trigger when the user interact with the ui
To me it looks like event handler + set state + state, not useEffect
July 3, 2025 at 1:09 PM
To me it looks like event handler + set state + state, not useEffect
I did for a custom tab indicator with it! Preventing the page to become not interactive required some dark magic though
June 26, 2025 at 9:48 PM
I did for a custom tab indicator with it! Preventing the page to become not interactive required some dark magic though
A thing I always loved of svelte that doesn't get enough credit is how easier is to debug svelte vs react when you clash with the framework, the distance between your code and the hooks/effects is much shorter in sv while in react all is buried under a mountain of calls to the internal scheduler.
June 18, 2025 at 9:27 PM
A thing I always loved of svelte that doesn't get enough credit is how easier is to debug svelte vs react when you clash with the framework, the distance between your code and the hooks/effects is much shorter in sv while in react all is buried under a mountain of calls to the internal scheduler.
It makes perfect sense, JS was not created to be used In such a declarative way but a language for UIs in the modern days needs this paradigm.
June 18, 2025 at 9:27 PM
It makes perfect sense, JS was not created to be used In such a declarative way but a language for UIs in the modern days needs this paradigm.
This looks amazing!
June 17, 2025 at 9:18 PM
This looks amazing!
I stopped using restful conventions a long ago and just use GET POST for everything, and I name my endpoint like this: updateThing, deleteThing.
So I guess I'm already doing RPC? :)
So I guess I'm already doing RPC? :)
June 17, 2025 at 9:14 PM
I stopped using restful conventions a long ago and just use GET POST for everything, and I name my endpoint like this: updateThing, deleteThing.
So I guess I'm already doing RPC? :)
So I guess I'm already doing RPC? :)
However is definitely not what people imagine there's no 10x productivity gain.
I guess if models becomes smarter and have real 1M context windows (not like now that after 200-150K they become useless) then you can teach them the workflow of writing tests and auto validate the results locally.
I guess if models becomes smarter and have real 1M context windows (not like now that after 200-150K they become useless) then you can teach them the workflow of writing tests and auto validate the results locally.
June 15, 2025 at 3:10 AM
However is definitely not what people imagine there's no 10x productivity gain.
I guess if models becomes smarter and have real 1M context windows (not like now that after 200-150K they become useless) then you can teach them the workflow of writing tests and auto validate the results locally.
I guess if models becomes smarter and have real 1M context windows (not like now that after 200-150K they become useless) then you can teach them the workflow of writing tests and auto validate the results locally.