Martin Kype
@angular2react.com
I'm a family man. I like to program. I love the web. I freelance. Got stuck with my sci-fi and fantasy hobbies since I was a kid. I __DO__ like Bitcoin and AI.
Ping me if you need a programmer or want to talk Heroquest, Star Trek or HTMX.
https://kype.at
Ping me if you need a programmer or want to talk Heroquest, Star Trek or HTMX.
https://kype.at
I'm using pure Preact and have no need for routing. I keep it very minimalistic and use fetch for data loading, and build my own hooks for state management. I also rolled my own i18n solution this time and I'm quite happy so far.
December 8, 2025 at 9:39 AM
I'm using pure Preact and have no need for routing. I keep it very minimalistic and use fetch for data loading, and build my own hooks for state management. I also rolled my own i18n solution this time and I'm quite happy so far.
Win 7 was the last Microsoft desktop OS I actually thought worth using. Windows 8 pushed me over the cliff into Linux land.
a meme of ice cube says he is resisting the urge to install linux in every computer he sees
ALT: a meme of ice cube says he is resisting the urge to install linux in every computer he sees
media.tenor.com
December 5, 2025 at 11:47 AM
Win 7 was the last Microsoft desktop OS I actually thought worth using. Windows 8 pushed me over the cliff into Linux land.
After reading the docs. A question for you: In what scenario did that help you? It's only for static content, in any other instance I'd still require a server especially for the "tension" mentioned in the original post.
December 4, 2025 at 3:16 PM
After reading the docs. A question for you: In what scenario did that help you? It's only for static content, in any other instance I'd still require a server especially for the "tension" mentioned in the original post.
I read it and correlated it with my experience working with it 1 year ago with NextJS. My mistake.
December 4, 2025 at 3:10 PM
I read it and correlated it with my experience working with it 1 year ago with NextJS. My mistake.
I really am. I stand corrected.
react.dev/reference/rs...
react.dev/reference/rs...
Server Components – React
The library for web and native user interfaces
react.dev
December 4, 2025 at 3:09 PM
I really am. I stand corrected.
react.dev/reference/rs...
react.dev/reference/rs...
I'm not exactly sure what you're concerned with currently. If you do not control the server, neither HTMX nor RSCs are an option.
If they are an option, you still need to handle additional problems yourself.
Fetching data and rendering it is the easy part, the rest is still to be solved, or not?
If they are an option, you still need to handle additional problems yourself.
Fetching data and rendering it is the easy part, the rest is still to be solved, or not?
December 4, 2025 at 2:57 PM
I'm not exactly sure what you're concerned with currently. If you do not control the server, neither HTMX nor RSCs are an option.
If they are an option, you still need to handle additional problems yourself.
Fetching data and rendering it is the easy part, the rest is still to be solved, or not?
If they are an option, you still need to handle additional problems yourself.
Fetching data and rendering it is the easy part, the rest is still to be solved, or not?
I really do think fetching data and rendering it is a minor problem nowadays. At least for the last 15 years.
Getting all the data flow right is a bigger problem, both techs do not really address (well).
HTMX has at least properly SSR, though.
Getting all the data flow right is a bigger problem, both techs do not really address (well).
HTMX has at least properly SSR, though.
December 4, 2025 at 2:34 PM
I really do think fetching data and rendering it is a minor problem nowadays. At least for the last 15 years.
Getting all the data flow right is a bigger problem, both techs do not really address (well).
HTMX has at least properly SSR, though.
Getting all the data flow right is a bigger problem, both techs do not really address (well).
HTMX has at least properly SSR, though.
Not sure we're talking about the same. RSCs, aswell as HTMX, solve the issue of fetching only those parts of data from the backend you actually want to render.
The whole "client-server dance" contain a much bigger problem set (authentication, authorization, CORS, etc.)
The whole "client-server dance" contain a much bigger problem set (authentication, authorization, CORS, etc.)
December 4, 2025 at 2:34 PM
Not sure we're talking about the same. RSCs, aswell as HTMX, solve the issue of fetching only those parts of data from the backend you actually want to render.
The whole "client-server dance" contain a much bigger problem set (authentication, authorization, CORS, etc.)
The whole "client-server dance" contain a much bigger problem set (authentication, authorization, CORS, etc.)
That's exactly right!
It's a much simpler tech solving the same issue. But it pushes most of its complexity into the endpoints and how they're wired, making it less opaque and more developer/source code and less framework/lib driven. With all shortcomings, idiosyncrasies and headache that entails.
It's a much simpler tech solving the same issue. But it pushes most of its complexity into the endpoints and how they're wired, making it less opaque and more developer/source code and less framework/lib driven. With all shortcomings, idiosyncrasies and headache that entails.
December 4, 2025 at 2:21 PM
That's exactly right!
It's a much simpler tech solving the same issue. But it pushes most of its complexity into the endpoints and how they're wired, making it less opaque and more developer/source code and less framework/lib driven. With all shortcomings, idiosyncrasies and headache that entails.
It's a much simpler tech solving the same issue. But it pushes most of its complexity into the endpoints and how they're wired, making it less opaque and more developer/source code and less framework/lib driven. With all shortcomings, idiosyncrasies and headache that entails.
As an old, grumpy dev I tend to judge a solution by it's benefit and complexity, not by the seniority of its developers. A complex solution has to solve an even more challenging problem to be worth it.
December 4, 2025 at 2:16 PM
As an old, grumpy dev I tend to judge a solution by it's benefit and complexity, not by the seniority of its developers. A complex solution has to solve an even more challenging problem to be worth it.
RSCs are another proof that frontend engineers over-engineer everything.
This resolves a minor problem to introduce major headache.
This resolves a minor problem to introduce major headache.
December 4, 2025 at 1:53 PM
RSCs are another proof that frontend engineers over-engineer everything.
This resolves a minor problem to introduce major headache.
This resolves a minor problem to introduce major headache.
RSCs were a mistake.
I went back to a client-side only solution using Preact for my latest project because the complexity you buy into is simply not worth the benefit of RSCs.
I went back to a client-side only solution using Preact for my latest project because the complexity you buy into is simply not worth the benefit of RSCs.
December 4, 2025 at 9:34 AM
RSCs were a mistake.
I went back to a client-side only solution using Preact for my latest project because the complexity you buy into is simply not worth the benefit of RSCs.
I went back to a client-side only solution using Preact for my latest project because the complexity you buy into is simply not worth the benefit of RSCs.
I see what you did there.
December 3, 2025 at 7:39 AM
I see what you did there.
Isn't this whole "OOP is bad" shtick __old and tired__? I remember these discussions from back in 2009 when I was still a junior dev.
Then we got C# lambdas, linq, etc. and Java 8 with lambdas, streams and this nonesense went away from my feeds and we continued to build 🤷♂️
Then we got C# lambdas, linq, etc. and Java 8 with lambdas, streams and this nonesense went away from my feeds and we continued to build 🤷♂️
December 3, 2025 at 7:31 AM
Isn't this whole "OOP is bad" shtick __old and tired__? I remember these discussions from back in 2009 when I was still a junior dev.
Then we got C# lambdas, linq, etc. and Java 8 with lambdas, streams and this nonesense went away from my feeds and we continued to build 🤷♂️
Then we got C# lambdas, linq, etc. and Java 8 with lambdas, streams and this nonesense went away from my feeds and we continued to build 🤷♂️
Die müssen dann dann die häufiger auftretenden Javascript Bugs fixen.
December 2, 2025 at 8:20 AM
Die müssen dann dann die häufiger auftretenden Javascript Bugs fixen.
Bei Nummer 9 geht's nicht nur ums Geld, sondern auch ganz simpel um Mannstärke. Wäre natürlich besser das wie die Schweizer im Rotationsprinzip zu organisieren, damit die Reserve auch in Übung bleibt - aber so ein Milizheer ist dennoch auf jeden Fall leistungsstärker bei der Raumverteidigung.
November 26, 2025 at 5:09 PM
Bei Nummer 9 geht's nicht nur ums Geld, sondern auch ganz simpel um Mannstärke. Wäre natürlich besser das wie die Schweizer im Rotationsprinzip zu organisieren, damit die Reserve auch in Übung bleibt - aber so ein Milizheer ist dennoch auf jeden Fall leistungsstärker bei der Raumverteidigung.
Women requiring men with 6 figures income were right all along. That's barely scraping by, apparently.
November 25, 2025 at 3:14 PM
Women requiring men with 6 figures income were right all along. That's barely scraping by, apparently.
Probably a Germanic-Language trade? In German it's also "verdienen" (to earn) and "gewinnen" (to win).
November 25, 2025 at 1:40 PM
Probably a Germanic-Language trade? In German it's also "verdienen" (to earn) and "gewinnen" (to win).
Love that opener. Now I need to check it out.
November 25, 2025 at 8:40 AM
Love that opener. Now I need to check it out.
Just 1 year ago, there was a lot of excitment for the image generation. We made a bunch of pokemon cards with the generator. That excitment seems to be gone.
November 24, 2025 at 10:03 AM
Just 1 year ago, there was a lot of excitment for the image generation. We made a bunch of pokemon cards with the generator. That excitment seems to be gone.