Surely I can't be the first person to come up with this:

Microsoft
Amazon
Google
Apple

The most upsetting thing for me about the whole #Framework/DHH drama is how its going to absolutely destroy the biggest push towards right to repair and open computing in probably the last 20 years

Its no secret how difficult it is to do what Framework is doing, and the fact that they've been this successful yet are now squandering the opportunity at a pivotal moment when things like Win11, Google "developer verification" and more are attacking our freedoms...so disappointing

By: @PaulNoth

To all those saying @pluralistic's keynote is going to cause facebook et al to pull out of sponsoring #pyconus:

1. I doubt zuck gives a 💩if he even hears about it
2. Cory wasn't dunking on these corps without reason - he has receipts

But most importantly: if they decide to go nuclear, it says a lot more about them than us. I'm proud that keynote speakers like Cory and Margaret Mitchell from 2023 are able to get up and speak without being told to "bend the knee".

We need it now more than ever.

However, they all seem not great and am curious to see what more experienced folks have to say.

It does make me beg the question of why using `global` is seen as such evil but if I do

class Foo:
var: str

@classmethod
def init(cls, val):
cls.var = val

init = Foo.init

That's somehow ok? All you're doing is adding an extra namespace to have to drill down into.

As a followup to @treyhunner's recent post about using modules as singletons in Python (which I originally encountered from one of @chrisjrn's talks), I sometimes find myself needing to update a global module variable in one of these cases as part of app startup. I've come up with 3 options:

- Use `global` inside the "init" function
- Use `globals()['var'] = ` inside the function
- Use either a single class instance/a class with all `@classmethod`s with module-level aliases ala `random`.