Fukkaudeku

Sorry cop

I bet you feel very clever

The Nazis were so socialist they invented the term "privatisation" https://pubs.aeaweb.org/doi/pdf/10.1257/jep.20.3.187

I am against free speech and a free society and I am proud to say that.

Except Nim doesn't make you copy/paste constantly.

For when you need to develop RSI in an emergency.

LNER (the public operator that replaced it) is pretty good, too; my train from King's Cross to Edinburgh was only 6 minutes late to arrive (very little jitter for a 4.5hr service) and the service onboard was great too.

The people who sell the computers in your country.

This, but unironically.

> If your state has bad laws, you can go to a different state.

Uprooting your life and moving is nowhere near as trivial as dipshit market fetishists make it out to be for the majority of people.

The Model M keyboard is the "I use arch btw" of keyboards.

Your houses are also made of tracing paper, which don't retain any heat, and have air con. Our houses are made of brick and insulation and are practically giant heatsinks. Being 23-25C inside and outside and absolutely no way to cool off is hell.

I've used IRC for ~10 years, but sure.

Let IRC die. Shit protocol, horrible usability.

Because the generation that gets all high and mighty about their childhood being more fun and outside (i.e. Gen Xers) are now the ones that are raising the next generation of children to be safe and are also complaining about it.

With old age comes your brain dribbling out of your ears.

Depends, how much do you like RSI?

Making more buttons into the retweet button.

Ironically, it looks very generic.

There are other implementations, such as Curio (https://github.com/dabeaz/curio) or Trio (https://github.com/python-trio/trio). Both are simpler and more hand-holdy (and less footgun) than asyncio.

Disclaimer: I am a trio dev, though.

> Python's going to have a bit of an awkward time with two completely different sets of ecosystem for threaded vs. asyncio approaches, but it's necessary progress.

It's threaded vs async/await (and even then projects like https://github.com/dabeaz/curio bridge that gap really well), rather than threaded vs asyncio. asyncio is just one (really really poor) implementation of async/await coroutines on Python.

> One thing I'd be really keen to see is asyncio frameworks starting to consider adopting ASGI as a common interface.

From what I've seen of the ASGI spec, it makes it incredibly easy (like most asyncio stuff) to DoS yourself with lack of backpressure. You get your callback called with data, and like all callback systems you can't exactly not get called.

Afaik they moved to Monero, because having the ability to see all transactions publicly from an address isn't very anonymous at all.