yeah. stopping support helps end it, but in russia's favor

that is a can of Folgers. I'd argue that incriminating a kitchen scale in the process makes it even worse

llvm exists. it might be a bit of effort if you've used too many proprietary gcc extensions, but for most things I don't think it's terrible to just switch between gcc and clang

👍

they're not the government but they are a political party with 15 seats in the parliament.

Don't give in to greed. Throw your car battery into the ocean to feed the electric eels

one is giving the permission to manage the system service to a specific user, the other is running the service as the current user so they have permission to manage it by default

it felt to me like coffeescript solved problems that people had, then js got equivalent features. arguably that could happen to ts as well

it's ironic with all this that Google fi messages on Android still doesn't support rcs without losing a bunch of other features

this guy writes shitty code

try element x, on android it opens almost instantly. still in beta though

do you have anything to back this up other than a fuzzy claim of authority? so far when I see people say things like this they're always talking about a handful of since fixed vulnerabilities early on in the project