lemmyng

Might want to think twice. The liberal party (current party in power) is falling apart, and the populist conservatives are looking like they’ll win the next election with a majority unless something changes significantly.

Provincially things are not much better either: Ontario is being run by a drug pushing grifter, the prairies took a hard right into ultra conservatism, the eastern provinces are essentially majority owned by a few rich families…

Found the possum.

Martok learned that lesson the hard way.

Polyglottal?

Can’t focus on mental problems if you’re too busy reinstalling arch.

Ever seen a spider molting? It’s practically 2.

Is a chicken egg an egg laid by a chicken, or an egg that if fertilized would hatch into a chicken?

If you want to see what it would be like in the wrong hands: https://m.imdb.com/title/tt1213404/

I will never forgive JSON for not allowing commas after the last element in a list.

“Fry” can also mean “a very small fish.”

Zap-Em van, Men in Black.

Someone watched Iron Sky.

Most of the time it was IRQ 7 for me.

You could try Emby. It’s freemium, but the free part doesn’t (or didn’t, last time I used it) require an online account.

So TCP ACK is the backwash?

shitdown -h now

A severe lack of imagination.

Here’s a third one: They have a Welcome Stamp visa program where you can work remotely from there for a year, and it’s renewable. You can even bring your family. Under this program you only pay income tax on your country of origin.

To be fair though, the chance that every Lemmy instance goes down at the same time is so much lower than Reddit going down. Sure, my instance might be unavailable, but I’d be able to hop onto the next one and continue.

I’ve seen it successfully happen due to licensing costs and cloud migration (MSSQL->Spanner), as well as for scalability reasons (vanilla postgres->cockroach). The first one was a significant change in features, the latter did sacrifice some native plugins. In the first case the company was using vendor specific features, and rewrote the backend to fit the new vendor.

There’s vendor agnosticism, and then there’s platform agnosticism. Writing your code so that it’s not tied to one specific implementation of postgres is fine, and lets you use a compatible drop-in. Writing your code so you can swap MSSQL for Oracle or Aurora or whatever at will does not make sense. In every case of attempted platform agnosticism I’ve seen they ended up abandoning the project within a year or two with nothing to show for it.