We do migrations for schema on app startup (built into the app).

Any general data changes are done outside the pipeline as a pre or post deployment step.

Migrations on startup aren’t perfect, you have to be careful that it doesn’t take too long on startup.

Honestly the pros outweighs the cons. You can fire up a new site/db without much effort which is something we do often.

Aaaah I understand.

What do you mean by the cost? Because you didn’t want to wipe out your Windows OS? I’ve been running distros on my personal PC for 23 years now. Can’t say I’ve ever spent money on it except for some cheap CDs. I think I even got distro cds for cheap that came with linux magazines.

You and me both. The worst is I have to use Teams for work and Ctrl+Shift+C is the shortcut to call the person you’re chatting with.

Agreed. I laugh at these peasant frivolities.

No, I’m grateful for the rant. It’s been driving me nuts and with the apps I need to use for work not supporting Wayland whatsoever it basically makes me stuck on X, which sucks because Wayland feels much better for me other than XWayland.

It’s a really bad issue for me, it makes XWayland completely unusable. Like, characters appear in different order as I’m typing. The cursor sometimes looks like it’s a character behind. It’s obnoxious that such a huge bug is stuck in politics.

Sorry I have to laugh at this. If you have to write a script for it even if the script is easy there’s no way I can consider it “not hard”. Not hard is just being able buy it like anything else.

I get what you’re saying though.

I’m not super sure what exactly causes the XWayland funkiness on Wayland with NVIDIA’s driver. The Phoronix article mentions “DMA-BUF v4 Wayland protocol support”

Is that possible this would help with that?