Simon
@skagedal.tech
Another tech change: I was going to use oauth2-proxy to handle the Google authentication, but I’m realizing it’s probably much easier to just use Auth.js/next-auth…
May 25, 2025 at 1:43 PM
Another tech change: I was going to use oauth2-proxy to handle the Google authentication, but I’m realizing it’s probably much easier to just use Auth.js/next-auth…
In other “welcome to 2025” news, I am now deploying with a Docker container. Still running as a systemd service, ain’t got time to set up a Kubernetes cluster.
May 25, 2025 at 12:00 PM
In other “welcome to 2025” news, I am now deploying with a Docker container. Still running as a systemd service, ain’t got time to set up a Kubernetes cluster.
3. And… I am starting to think that React Server Components are really cool. 😎
May 25, 2025 at 8:28 AM
3. And… I am starting to think that React Server Components are really cool. 😎
2. JSX (TSX). Writing web UI this way is just way better than anything you have in any other programming language (that I know of). All html-as-DSL (like kotlinx.html etc) approaches just feel wrong.
May 25, 2025 at 8:28 AM
2. JSX (TSX). Writing web UI this way is just way better than anything you have in any other programming language (that I know of). All html-as-DSL (like kotlinx.html etc) approaches just feel wrong.
The things that switched me over sound obvious, but basically:
1. The larger ecosystem. For example, I couldn’t find a decent syntax highlighting system for the JVM. JS ecosystem has such a rich set of tools for that kind of stuff.
1. The larger ecosystem. For example, I couldn’t find a decent syntax highlighting system for the JVM. JS ecosystem has such a rich set of tools for that kind of stuff.
May 25, 2025 at 8:27 AM
The things that switched me over sound obvious, but basically:
1. The larger ecosystem. For example, I couldn’t find a decent syntax highlighting system for the JVM. JS ecosystem has such a rich set of tools for that kind of stuff.
1. The larger ecosystem. For example, I couldn’t find a decent syntax highlighting system for the JVM. JS ecosystem has such a rich set of tools for that kind of stuff.
That’s now what’s live on skagedal.tech. A bit too much fighting with Tailwind, and far too much general complexity for a simple blog, but I think it’ll be worthwhile. And I also want to get more deep into that tech stack (also. I want a lot of stuff).
skagedal.tech
Thoughts on software development, technology and the future.
skagedal.tech
May 25, 2025 at 8:23 AM
That’s now what’s live on skagedal.tech. A bit too much fighting with Tailwind, and far too much general complexity for a simple blog, but I think it’ll be worthwhile. And I also want to get more deep into that tech stack (also. I want a lot of stuff).
Well, its so happened that I scrapped this whole approach and instead rewrote things again in Next.js 😄
May 25, 2025 at 8:20 AM
Well, its so happened that I scrapped this whole approach and instead rewrote things again in Next.js 😄
Is something missing on the code line under “// Interact with UI”? Shouldn’t there be a `user.click(button)` or such?
May 24, 2025 at 4:18 AM
Is something missing on the code line under “// Interact with UI”? Shouldn’t there be a `user.click(button)` or such?
I do sometimes like to drop the .sh extension on shell scripts because “it’s cleaner”: tools should be able to identify it using shebang for syntax highlighting etc, I don’t need to expose the implementation detail just like with any executable, etc.
But sometimes I wonder what I do with my life.
But sometimes I wonder what I do with my life.
May 20, 2025 at 3:10 AM
I do sometimes like to drop the .sh extension on shell scripts because “it’s cleaner”: tools should be able to identify it using shebang for syntax highlighting etc, I don’t need to expose the implementation detail just like with any executable, etc.
But sometimes I wonder what I do with my life.
But sometimes I wonder what I do with my life.
It really is a very different claim from those others. The claim isn’t that “non-programmers will be able to make software”, it is that there will be a new kind of programmer, whose brain is silicon-based rather than meat-based.
May 18, 2025 at 5:47 PM
It really is a very different claim from those others. The claim isn’t that “non-programmers will be able to make software”, it is that there will be a new kind of programmer, whose brain is silicon-based rather than meat-based.
What if you say something that gets interpreted as ”>
If that also isn’t properly escaped, you could affect the xhtml payload in unexpected ways?
If that also isn’t properly escaped, you could affect the xhtml payload in unexpected ways?
May 14, 2025 at 5:56 AM
What if you say something that gets interpreted as ”>
If that also isn’t properly escaped, you could affect the xhtml payload in unexpected ways?
If that also isn’t properly escaped, you could affect the xhtml payload in unexpected ways?
Very interesting! Although I don’t quite understand your argument that this couldn’t be a security vulnerability. Of course, the invalid XHTML is refused. But the issue is that it’s there in the first place, rather than the ampersand having been properly escaped. >>
May 14, 2025 at 5:55 AM
Very interesting! Although I don’t quite understand your argument that this couldn’t be a security vulnerability. Of course, the invalid XHTML is refused. But the issue is that it’s there in the first place, rather than the ampersand having been properly escaped. >>
They’re most likely potheads.
May 5, 2025 at 4:42 AM
They’re most likely potheads.