It’s much more than just inline styles. It’s also design constants (e.g. color palettes, sizing etc.) and utilities (e.g. ring).

No, it’s of course not just aria attributes. But it’s definitely not “how easy can I create user CSS”. Accessibility is a term of art, you can’t just expand its meaning to whatever you want.

https://en.wikipedia.org/wiki/Accessibility

Except that you learn the class names once and re-use them across all your projects, whereas CSS classes are different for every single project.

That’s not accessibility.

How *some JS UI libraries handle scoped CSS. Vue for example uses data- attributes instead.

How are class names relevant for accessibility?

Yeah, can’t recommend Aurora enough. It’s awesome to have literally 0 driver issues, since the system image already contains the drivers pre-installed.

My issue with Python is that so many “pythonic” practices lead to horrible-to-read code. List comprehensions are nice, except for when they go more than one level deep. kwargs leads to horrible code. Lots of valid Python code cannot be typed correctly, which makes editor inference far worse. Don’t get me started on metaclasses and the like.

Python right now is basically what JavaScript was before TS.

I like the cut of your jib

Except for necessary modern features like different fractional scaling on multiple monitors…

If it’s only in the type checker, can IDEs/editors correctly show the type information of inferred types then?

Yep, and some (e.g. Pycharm) do. They have to be a bit careful with not assuming too much since lots of legacy code is written in fairly terrible ways, so e.g. default parameter values don’t necessarily set the type of their respective parameters, but it’s definitely possible and mostly a choice by the editor/IDE.

Do they call the type checker themselves to retrieve that info?

Depends on the editor! Pycharm is built on a custom engine by Jetbrains, whereas e.g. the Python VS code plugin by Microsoft (Pylance) is based on Microsofts type checker (pyright).

Type inference is a feature of the type checker, not of Python itself. I’m fairly sure the type checker that’s being developed by the Astral team will have proper inference, and I’ve also had good experiences with pyright in the past.

Though it doesn’t come close to e.g. Typescript, which is a shame - Python could really use the advanced dynamic type checking features TS has.

I’ve had good experiences with my Nvidia card on Aurora (same basis as e.g. Bazzite), but HDR is indeed still an issue.

Right now, all you have to do is go to the settings of your non-steam game, go to compatibility, and choose a Proton version. I’m not sure if this change will automate it, but it’s pretty much as easy as it can be already.

I’d interpret that as a local social network app, not map/navigation.

Oh, you should have mentioned that - or do you think that fsck is Memtest? It is not.

Hm, unfortunately nothing obvious. And your last boot ended with a crash?

Nevertheless you could try running a Memtest (this can take a while) - it will check whether any of your RAM modules are faulty: https://www.memtest.org/

That’s unfortunately a bit cut off. Could you run this again with the following command? sudo journalctl -xeb -1 --no-pager

Sure, though the immutable design makes it very safe to touch these things.

OP, do this - it’s the best way to figure out what’s happening. It could be any number of issues, e.g. faulty RAM. With the output of the command above people can tell you what to test for.