Dominik Meca

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.

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.

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...

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.

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.

Next.js Is Infuriating

I've finally managed to fulfill one of my goals. I've joined the mass of people rambling pointlessly about useless things online.

This one is about my recent frustration with Next.js. Hope you enjoy it!

steveklabnik1's comment on "Towards Understanding the Runtime Performance of Rust | Proceedings of the 37th IEEE/ACM International Conference on Automated Software Engineering" Explore this conversation and more from the rust community

You have: www.reddit.com/r/rust/comme...

It's both terrible C and terrible Rust.

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

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.

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?

Comment from the layout source: This layout conforms to a new Czech compromise standard designed to satisfy most Unix, Windows and Mac users. Name censored since I don't actually want to strangle anyone and I don't think the person deserves any hate.

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.

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.

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.

Nah. You at least get some good games. Try being a Stargate fan ...

I think I just got monkey-pawed by YouTube. I reported the new miniplayer as completely useless and buggy.

To fulfill my wishes YouTube decided to break the app in such a way that the miniplayer doesn't show up but the video still plays in the background.

Amazing engineering going on at Google.

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.