Gordon Freeman steps out of the clean room

“ ”

Other scientist: “What?”

Gordon pulls a shotgun from his locker and starts loading it

“ ”

Gordon cocks it and steps back into the clean room

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?

It’s fairly common knowledge that SSDs outperform HDDs in both sequential and random reads, and while the file size & number of files have an impact, it doesn’t negate this difference.

A quick search confirmed that SSDs perform better in your scenario than HDDs. I don’t care enough to spend time finding proper references, because again - this is simply common knowledge.

Of course SSDs are still much faster reading massive amounts of tiny files than HDDs are. Obviously random read speeds are much, much better, but even sequential reads of tiny files are a lot faster.

If you disagree, please provide numbers or references.

Yet HDDs were also much slower than SSDs

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

When the second issue happens, does the reload button & address bar also no longer work? Then I have the same issue, it’s pretty annoying. It can be fixed by pulling the tab out into a separate window & merging it back into the previous one, but still very annoying.

I’ve unfortunately had the same happen on LibreWolf.

Sadly people literally write that and mean it. See the other reply:

They really don’t seem to be bothered by it.

Sorry, classic case of Poe’s law! There are plenty of people who write what you said without any sarcasm, so without any indicators there’s no way to know.

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).

And how do you know that?

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.