Yes I know what you mean now, I didn’t know what you meant when you fabricated your own definition and didn’t inform me of your special definition that nobody else uses.
In the future, when talking to people, it’s best to either use widely accepted definitions or make it clear that you’re using your own for god-knows what reason.
By the actual definition of bourgeoise, which is what I was talking about, I’m obviously correct. If we adopt your definition where you’re just using it as a synonym for “ruler”, I won’t claim to know the future. Maybe AI will be a benevolent dictator, or maybe we’ll have a proper dictatorship of the proletariat, or maybe we’ll have a proper free society. Who knows. But capitalist realism is still an absurd and stupid position considering it’s only been a thing for 200 years (unless you’re also redefining capitalism in your world where you just make up your own definitions of everything).
Python’s disdain for the industry standard is wild. Every other language made in the last 20 years has proper filtering that doesn’t require collecting the results back into a list after filtering like Java (granted it’s even more verbose in Java but that’s a low bar).
If Python had modern lambdas and filter was written in an inclusion or parametric polymorphic way, then you could write:
new_results = results.filter(x -> x)
Many languages have shorthands to refer to variables too, so it wouldn’t be impossible to see:
new_results = results.filter(_)
Of course in actual Python you’d instead see:
new_results = list(filter(lambda x: x, results))
which is arguably worse than
new_results = [x for x in results if x]