Dominik Meca
dominik.meca.sh
Dominik Meca
@dominik.meca.sh
Hi. I know that there's been some effort to de-Vercelify Next in the past, including OpenNext. I think it would be great if these efforts succeed.

Thankfully we avoided a lot of the lock in with the standalone node deployment. But it does mean we're locked out of a lot of interesting stuff.
September 2, 2025 at 1:12 PM
Short term, probably nowhere. Our apps are already written and getting frustrated every other week isn't a good enough excuse for rewriting them.

Longer term, I think TanStack Start looks good for dashboard-shaped apps. Possibly Remix for user facing apps? Will have to take a look.
September 2, 2025 at 12:47 PM
Interesting. I had another person saying the same thing. I can add comments myself though. I guess this is a price I pay for not writing my own blogging platform.

bsky.app/profile/mig4...
@dominik.meca.sh I feel you regarding Next.js
What other options have you tried?

Btw, I couldn't comment in the post itself using bsky integration. Something may be broken with Leaflet or your config :)
September 2, 2025 at 12:45 PM
Unfortunately, we are a React shop, so I don't think we could move to Svelte even if I tried very hard to convince everyone.

I think TanStack Start looks solid for future dashboard projects. And maybe remix for user-facing stuff? I'll have to take a look to form a proper opinion.
September 2, 2025 at 10:42 AM
Interesting. I may compile a list of Leaflet improvements I would like to see in the future. That would definitely go on there.

Personally, I have great experience with SvelteKit. I'm worried about some of the changes that have happened/might happen in the future though.
September 2, 2025 at 10:42 AM
While I can't speak to Marcan getting into another drama, I do find it interesting that there is an open issue from 2020 alleging another piece of stolen code: github.com/devkitPro/li...

The defense seems to be that it's used for debugging and so it is fine. That doesn't really fly for me.
kprintf is GPL · Issue #75 · devkitPro/libogc
libogc includes a copy of kprintf, which was distributed under the GPL, despite libogc having a license most closely matching MIT. https://github.com/devkitPro/libogc/blob/master/libogc/kprintf.c
github.com
April 28, 2025 at 12:00 PM
I feel I should clarify that I don't actually want to strangle anyone.

It does get more ridiculous though. All(?) European layouts extend the base latin layout. That one is also a compromise.

That's an area of ~400m people that all have wrong keyboard layouts. Why? To save a few KBs?
March 12, 2025 at 9:43 AM
I wanted to disagree, but your keyboard comment got me.

I switched to Linux about a year ago and found the Czech Windows layout completely unusable. I spent a lot of time figuring out custom layouts and reproducing the actual Windows layout.

I want to strangle whoever wrote this dumb comment.
March 12, 2025 at 9:27 AM
This reminds me of your Animal Well stream where you were solving the windings puzzle and said something like "I can read the runes" but you were actually reading a walkthrough.
January 25, 2025 at 9:49 AM
There's a script section in the package.json file. You can define an entry with a name and a shell command. The command has access to CLIs installed in node_modules.

npx does some weird stuff in the background making it slow. VSCode should have support for running npm scripts from tasks.
January 9, 2025 at 1:46 PM
Nah. You at least get some good games. Try being a Stargate fan ...
December 29, 2024 at 5:28 PM
Since opening an image from the feed doesn't create a history entry, trying to close the image using the back button boots me out of the page (either back to the home screen or whichever site I was on before). This is on Firefox for Android.
November 5, 2024 at 8:58 AM