Reading about the new useEffectEvent in react.
This is throwing more stuff at trying to improve a bad fundamental pattern (reactive effects via useEffect).
If you use TEA (the Elm architecture) none of this is necessary.
stately.ai/docs/xstate-... in a great implementation for React.
This is throwing more stuff at trying to improve a bad fundamental pattern (reactive effects via useEffect).
If you use TEA (the Elm architecture) none of this is necessary.
stately.ai/docs/xstate-... in a great implementation for React.
@xstate/store | Stately
Version 3.x (Version 2.x docs)
stately.ai
October 2, 2025 at 10:49 PM
Reading about the new useEffectEvent in react.
This is throwing more stuff at trying to improve a bad fundamental pattern (reactive effects via useEffect).
If you use TEA (the Elm architecture) none of this is necessary.
stately.ai/docs/xstate-... in a great implementation for React.
This is throwing more stuff at trying to improve a bad fundamental pattern (reactive effects via useEffect).
If you use TEA (the Elm architecture) none of this is necessary.
stately.ai/docs/xstate-... in a great implementation for React.
I find the automatic ghost text behaviour when using copilot very distracting.
So a couple of months ago I changed that to be an explicit shortcut.
But I noticed that since then, I hardly use it. Maybe it wasn't that useful.
So a couple of months ago I changed that to be an explicit shortcut.
But I noticed that since then, I hardly use it. Maybe it wasn't that useful.
June 13, 2025 at 11:12 PM
I find the automatic ghost text behaviour when using copilot very distracting.
So a couple of months ago I changed that to be an explicit shortcut.
But I noticed that since then, I hardly use it. Maybe it wasn't that useful.
So a couple of months ago I changed that to be an explicit shortcut.
But I noticed that since then, I hardly use it. Maybe it wasn't that useful.
Disillusioned on the new Fujifilm X-E5. Reading the specs the viewfinder is quite disappointing. As I only use the EVF this is really important to me. I was really hoping that they would make a small camera with a great EVF.
June 12, 2025 at 11:31 PM
Disillusioned on the new Fujifilm X-E5. Reading the specs the viewfinder is quite disappointing. As I only use the EVF this is really important to me. I was really hoping that they would make a small camera with a great EVF.
I looked at xstate/store before for React state management. stately.ai/docs/xstate-...
But in V3 they added side effects handling. With this addition is mostly the perfect state management solution I want. Trying it in our app.
Pretty much what I'm looking for is Elm TEA in react.
But in V3 they added side effects handling. With this addition is mostly the perfect state management solution I want. Trying it in our app.
Pretty much what I'm looking for is Elm TEA in react.
@xstate/store | Stately
Version 3.x (Version 2.x docs)
stately.ai
June 6, 2025 at 10:55 PM
I looked at xstate/store before for React state management. stately.ai/docs/xstate-...
But in V3 they added side effects handling. With this addition is mostly the perfect state management solution I want. Trying it in our app.
Pretty much what I'm looking for is Elm TEA in react.
But in V3 they added side effects handling. With this addition is mostly the perfect state management solution I want. Trying it in our app.
Pretty much what I'm looking for is Elm TEA in react.
The previous Mission impossible was pretty good, I really liked it. So I went with high expectations to the new one. Unfortunately it was quite mid. A lot of nonsense, completely unbelievable stunts, very brain dead.
June 1, 2025 at 9:48 AM
The previous Mission impossible was pretty good, I really liked it. So I went with high expectations to the new one. Unfortunately it was quite mid. A lot of nonsense, completely unbelievable stunts, very brain dead.
Definitely some pros of the microservice architecture like
- Failure isolation
- Independent scaling, versioning and deploys
But there are huge tradeoffs for me:
- Lots of incidental complexity and repetition
- Weak contracts
- Very high maintenance burden
- Harder to work with and refactor
- Failure isolation
- Independent scaling, versioning and deploys
But there are huge tradeoffs for me:
- Lots of incidental complexity and repetition
- Weak contracts
- Very high maintenance burden
- Harder to work with and refactor
May 23, 2025 at 4:11 AM
Definitely some pros of the microservice architecture like
- Failure isolation
- Independent scaling, versioning and deploys
But there are huge tradeoffs for me:
- Lots of incidental complexity and repetition
- Weak contracts
- Very high maintenance burden
- Harder to work with and refactor
- Failure isolation
- Independent scaling, versioning and deploys
But there are huge tradeoffs for me:
- Lots of incidental complexity and repetition
- Weak contracts
- Very high maintenance burden
- Harder to work with and refactor
Geez, we have gone so far on the microservices path that a lot of our business logic is in freaking cloudformation yaml files.
Do we process x for a customer? Need to look at CF yaml. It is like a terrible and untested programming language. I hate it.
Do we process x for a customer? Need to look at CF yaml. It is like a terrible and untested programming language. I hate it.
May 23, 2025 at 4:03 AM
Geez, we have gone so far on the microservices path that a lot of our business logic is in freaking cloudformation yaml files.
Do we process x for a customer? Need to look at CF yaml. It is like a terrible and untested programming language. I hate it.
Do we process x for a customer? Need to look at CF yaml. It is like a terrible and untested programming language. I hate it.
People keep repeating that React is "functional". Maybe at the beginning it was or I just don't understand their definition of functional.
Components can have lots of non explicit inputs with hooks. Which can get global mutable state from lots of spaces.
Components can have lots of non explicit inputs with hooks. Which can get global mutable state from lots of spaces.
May 10, 2025 at 12:16 AM
People keep repeating that React is "functional". Maybe at the beginning it was or I just don't understand their definition of functional.
Components can have lots of non explicit inputs with hooks. Which can get global mutable state from lots of spaces.
Components can have lots of non explicit inputs with hooks. Which can get global mutable state from lots of spaces.
We use conventional commits everywhere.
www.conventionalcommits.org/en/v1.0.0/
However 'feat' is often used for user facing features and internal features. Gets confusing.
We need a distinction. I rather not use the scope for this.
Trying to find a good word for 'internal feature'.
www.conventionalcommits.org/en/v1.0.0/
However 'feat' is often used for user facing features and internal features. Gets confusing.
We need a distinction. I rather not use the scope for this.
Trying to find a good word for 'internal feature'.
Conventional Commits
A specification for adding human and machine readable meaning to commit messages
www.conventionalcommits.org
April 20, 2025 at 3:38 AM
We use conventional commits everywhere.
www.conventionalcommits.org/en/v1.0.0/
However 'feat' is often used for user facing features and internal features. Gets confusing.
We need a distinction. I rather not use the scope for this.
Trying to find a good word for 'internal feature'.
www.conventionalcommits.org/en/v1.0.0/
However 'feat' is often used for user facing features and internal features. Gets confusing.
We need a distinction. I rather not use the scope for this.
Trying to find a good word for 'internal feature'.
I have been refactoring our React forms to use TanStack Form. Our current lib is poor at type safety.
I found it interesting that you need to explicitly subscribe to state all over the place (to avoid re-renders). Otherwise the view is stale.
One big promise of React was not having to do this.
I found it interesting that you need to explicitly subscribe to state all over the place (to avoid re-renders). Otherwise the view is stale.
One big promise of React was not having to do this.
April 12, 2025 at 2:41 AM
I have been refactoring our React forms to use TanStack Form. Our current lib is poor at type safety.
I found it interesting that you need to explicitly subscribe to state all over the place (to avoid re-renders). Otherwise the view is stale.
One big promise of React was not having to do this.
I found it interesting that you need to explicitly subscribe to state all over the place (to avoid re-renders). Otherwise the view is stale.
One big promise of React was not having to do this.
I have been building an app with Datastar. I'm quite happy with it.
This is a great intro chrismalek.me/posts/data-s...
I still have one complex interaction in my app where a front-end framework like Elm is better.
But for the majority of interactions Datastar is excellent.
This is a great intro chrismalek.me/posts/data-s...
I still have one complex interaction in my app where a front-end framework like Elm is better.
But for the majority of interactions Datastar is excellent.
April 12, 2025 at 12:52 AM
I have been building an app with Datastar. I'm quite happy with it.
This is a great intro chrismalek.me/posts/data-s...
I still have one complex interaction in my app where a front-end framework like Elm is better.
But for the majority of interactions Datastar is excellent.
This is a great intro chrismalek.me/posts/data-s...
I still have one complex interaction in my app where a front-end framework like Elm is better.
But for the majority of interactions Datastar is excellent.
Having a go at building an app with data-star.dev
It is like htmx but can do more things.
It took me a while to understand how to send responses from the server.
So far I'm quite happy with this.
It is like htmx but can do more things.
It took me a while to understand how to send responses from the server.
So far I'm quite happy with this.
Datastar - The hypermedia framework.
Datastar helps you build reactive web applications with the simplicity of server-side rendering and the power of a full-stack SPA framework.
data-star.dev
February 22, 2025 at 3:55 AM
Having a go at building an app with data-star.dev
It is like htmx but can do more things.
It took me a while to understand how to send responses from the server.
So far I'm quite happy with this.
It is like htmx but can do more things.
It took me a while to understand how to send responses from the server.
So far I'm quite happy with this.
Somedays, like today, I attempt to use Helix for editing. As Helix is great for navigation and many other things.
But the lack of a file tree is a huge downside. I don't want to figure out how to configure helix and zellij and yazi together in order to have a file tree.
But the lack of a file tree is a huge downside. I don't want to figure out how to configure helix and zellij and yazi together in order to have a file tree.
February 5, 2025 at 3:38 AM
Somedays, like today, I attempt to use Helix for editing. As Helix is great for navigation and many other things.
But the lack of a file tree is a huge downside. I don't want to figure out how to configure helix and zellij and yazi together in order to have a file tree.
But the lack of a file tree is a huge downside. I don't want to figure out how to configure helix and zellij and yazi together in order to have a file tree.
Now I need to deal with Headless UI too which is also outdated. At some point someone decided to use a new component lib (headless UI) but they couldn't be bothered removing the old one (material UI).
January 17, 2025 at 11:36 PM
Now I need to deal with Headless UI too which is also outdated. At some point someone decided to use a new component lib (headless UI) but they couldn't be bothered removing the old one (material UI).
Just finished a grueling two months of work removing Material UI from this app.
Leaning so heavily on a component lib like this was a huge liability. Made it impossible to upgrade other things.
Now it is mostly vanilla html and some Radix components for the hard stuff.
Leaning so heavily on a component lib like this was a huge liability. Made it impossible to upgrade other things.
Now it is mostly vanilla html and some Radix components for the hard stuff.
January 17, 2025 at 11:29 PM
Just finished a grueling two months of work removing Material UI from this app.
Leaning so heavily on a component lib like this was a huge liability. Made it impossible to upgrade other things.
Now it is mostly vanilla html and some Radix components for the hard stuff.
Leaning so heavily on a component lib like this was a huge liability. Made it impossible to upgrade other things.
Now it is mostly vanilla html and some Radix components for the hard stuff.
Off for a holiday for three weeks. Don't need to look at Typescript for a while, win :).
December 14, 2024 at 12:54 AM
Off for a holiday for three weeks. Don't need to look at Typescript for a while, win :).
Each year the kids' school change the required books or editions. Making us buy new books. They just tell us to discard the books we already have from the older kids. Incredible waste (and spend), so annoying.
December 8, 2024 at 6:35 AM
Each year the kids' school change the required books or editions. Making us buy new books. They just tell us to discard the books we already have from the older kids. Incredible waste (and spend), so annoying.
blog.erodriguez.de/dependency-m...
I empathize a lot with this. But moving to a different stack is not an immediate possibility for us. So instead my strategy has been to replace libs with of our own implementations. E.g. our own router, query string parser, form lib, etc.
I empathize a lot with this. But moving to a different stack is not an immediate possibility for us. So instead my strategy has been to replace libs with of our own implementations. E.g. our own router, query string parser, form lib, etc.
Dependency management fatigue, or why I forever ditched React for Go+HTMX+Templ
After getting to work on some personal projects using Go+HTMX+Templ this year, I have decided to give up on using React on any personal projects.
You can actually find a lot of compelling arguments fo...
blog.erodriguez.de
December 3, 2024 at 10:46 PM
blog.erodriguez.de/dependency-m...
I empathize a lot with this. But moving to a different stack is not an immediate possibility for us. So instead my strategy has been to replace libs with of our own implementations. E.g. our own router, query string parser, form lib, etc.
I empathize a lot with this. But moving to a different stack is not an immediate possibility for us. So instead my strategy has been to replace libs with of our own implementations. E.g. our own router, query string parser, form lib, etc.
I listen to a few podcasts about crypto coins. Some very pro, some very against.
Based on the same facts One says that this stuff will run everything in the future. The other says that it is all just cons and frauds.
They just see the part they want. Hard to get balanced views.
Based on the same facts One says that this stuff will run everything in the future. The other says that it is all just cons and frauds.
They just see the part they want. Hard to get balanced views.
December 2, 2024 at 1:28 AM
I listen to a few podcasts about crypto coins. Some very pro, some very against.
Based on the same facts One says that this stuff will run everything in the future. The other says that it is all just cons and frauds.
They just see the part they want. Hard to get balanced views.
Based on the same facts One says that this stuff will run everything in the future. The other says that it is all just cons and frauds.
They just see the part they want. Hard to get balanced views.
This episode was very interesting to understand what has been going with Elm the last four years, I really appreciate Evan being more public about it lately.
Also this other one is a great listen m.youtube.com/watch?v=qtoe...
Also this other one is a great listen m.youtube.com/watch?v=qtoe...
November 29, 2024 at 10:05 PM
This episode was very interesting to understand what has been going with Elm the last four years, I really appreciate Evan being more public about it lately.
Also this other one is a great listen m.youtube.com/watch?v=qtoe...
Also this other one is a great listen m.youtube.com/watch?v=qtoe...
"Rendered more hooks than during the previous render."
Sorry, React just frustrates me, the fact that this error is a thing, is for me a clear symptom of the terrible design of hooks.
Sorry, React just frustrates me, the fact that this error is a thing, is for me a clear symptom of the terrible design of hooks.
November 28, 2024 at 11:46 PM
"Rendered more hooks than during the previous render."
Sorry, React just frustrates me, the fact that this error is a thing, is for me a clear symptom of the terrible design of hooks.
Sorry, React just frustrates me, the fact that this error is a thing, is for me a clear symptom of the terrible design of hooks.
I'm finding copilot quite distracting sometimes.
I really like when it gives a one line suggestion.
But when it tries to suggest a whole function body, it just gets in the way.
I need to learn if it is possible to disable longer suggestions.
I really like when it gives a one line suggestion.
But when it tries to suggest a whole function body, it just gets in the way.
I need to learn if it is possible to disable longer suggestions.
November 28, 2024 at 11:47 AM
I'm finding copilot quite distracting sometimes.
I really like when it gives a one line suggestion.
But when it tries to suggest a whole function body, it just gets in the way.
I need to learn if it is possible to disable longer suggestions.
I really like when it gives a one line suggestion.
But when it tries to suggest a whole function body, it just gets in the way.
I need to learn if it is possible to disable longer suggestions.
In the process of removing Material UI a second time.
A UI component library is a very heavy dependency, that is hard to remove or swap.
takeaways for me:
- resist using a lib like this as much as possible
- if using one, create a small layer in the app that wraps that lib
A UI component library is a very heavy dependency, that is hard to remove or swap.
takeaways for me:
- resist using a lib like this as much as possible
- if using one, create a small layer in the app that wraps that lib
November 28, 2024 at 8:38 AM
In the process of removing Material UI a second time.
A UI component library is a very heavy dependency, that is hard to remove or swap.
takeaways for me:
- resist using a lib like this as much as possible
- if using one, create a small layer in the app that wraps that lib
A UI component library is a very heavy dependency, that is hard to remove or swap.
takeaways for me:
- resist using a lib like this as much as possible
- if using one, create a small layer in the app that wraps that lib
Rabbit hole day today, can't install the lib we need because react is outdated, can't update react because material UI is outdated.
Need to spend days updating things before starting what we need. Hopefully there isn't more things that need updating.
Need to spend days updating things before starting what we need. Hopefully there isn't more things that need updating.
November 26, 2024 at 7:11 AM
Rabbit hole day today, can't install the lib we need because react is outdated, can't update react because material UI is outdated.
Need to spend days updating things before starting what we need. Hopefully there isn't more things that need updating.
Need to spend days updating things before starting what we need. Hopefully there isn't more things that need updating.
The Australian gov wants to ban social media to under 16ths. I can't see that working.
It is going to make using social media harder for everyone and the kids will bypass the ban anyway.
It is going to make using social media harder for everyone and the kids will bypass the ban anyway.
November 26, 2024 at 7:02 AM
The Australian gov wants to ban social media to under 16ths. I can't see that working.
It is going to make using social media harder for everyone and the kids will bypass the ban anyway.
It is going to make using social media harder for everyone and the kids will bypass the ban anyway.