I faced this problem numerous times. This is mostly a problem with parsing the text.

Most often the solution is to translate the text into how other people think through a problem and replicate their mental model of the world in your head. This sounds tough but when you read, you should pay attention at various levels: Phrases -> Sentences -> Paragraph. Construct the mental model as numerous Cause->Effect relations. Identify other types of relations that the author wants to convey.

Often also change the way you parse the text. What I described above is Bottom-Up approach where you construct the big picture from smaller pieces. The other way would be to start Top-Down, construct a big picture view by reading only the start and end of a specific paragraph/technique, understand the transformation that is happening to code/data/control flow, then move on to the next big chunk. Eventually you will get the general idea. Then you can drill down on specific paragraphs/ideas and focus on the details.

Regarding Python itself, The sentence "reinstall it and use the pure python version, it's the only way you'll learn it properly" is assuming that one would easily figure out one among the the numerous ways of installing a python environment. It's not an easy thing to do given that you as a beginner won't understand all the nuances of what each method achieves.

Easiest way to proceed is to pick one way to setup your python environment and be done with it.

Tl; Dr

I am on Linux, so my personal stack is:

1. pyenv -> a. curl -fsSL https://pyenv.run/ | bash b. ~/.pyenv/bin/pyenv init --install

2. Install a python version -> a. pyenv install 3.14

3. Create my workspace and set the python version to the one I installed: a. mkdir workspace b. cd workspace c. pyenv local 3.14

4. Create a venv so I have a local python virtual environment: a. python3 -m venv .venv b. source .venv/bin/activate

5. Start working on my project/code.

(Note for others: I don't recommend uv here as I don't use it myself and haven't tried to properly use it for an extended duration of time)

On Windows, use python install manager + Venv.

This is a good tutorial:

https://www.youtube.com/watch?v=6e3WLhPLiZQ

Edit: I forgot to mention that the python docs are an excellent starting point for learning python in general: https://docs.python.org/3/

Ooh, It does sound interesting. My wild conspiracy is that Nintendo has made hardware offloaded functions that run with sub-microsecond latencies so this 20 us looks more like blocking non-DS hardware from communicating with the DS.

Sure but the title sounds interesting on it's own and prompted me to learn what it was. It's clickbait but there's no bait and switch when you visit the article.

And the description gives enough clue for me what the article is going to be about:

What happens when a large open source project dies.

Edit:

And I find that focusing too much about upvotes won't make for a good community experience. If the material is good the upvotes will eventually arrive.

or you can just read an actually interesting article

hey accumulating stuff that you still find use for is better than throwing them away. And you said you give away stuff to other people for their use.. which probably saves even more devices from a landfill.

I give up if there is no one tool but a million of them. Come back later and repeat.

Eventually just write it in python.

which makes sense to me. params is passing the reference to the dict into the function. Whereas, **params is expanding the dict into the scope of the function before calling the first line of the body.

You can update the content of the former in-place, while the latter is just syntactic sugar for variadic function arguments.

You're ignoring 20+ years of how it was the only player when web wasn't so big as it is today. It was a major reason windows became the default OS in many offices, and as an extension of that, in the majority of homes in the 2000s to 2015. Thus majority of software industry and video gaming companies made their home in windows. Adobe Photoshop, AutoCAD, and many other industry software was made to work in Windows first.

There was also the case of Microsoft tilting the playing field by significantly discounting laptop and Desktop OEMs for Windows license keys just to be the sole OS installed on many computers. The concept of a PC was one which was running some version of Windows.

This also lead to another compounding aspect: Piracy of windows software made the windows AD/Server experts of today. Since Linux was free, there wasn't as much of an intrigue on running it vs. A pirated copy of windows running pirated copy of many software.

Oh sorry for that. Meant to reply to the asshole not your comment.

Going away depends on a lot more things happening in the background like VCs stopping AI funding. Your assumption that demand matches supply lacks nuance like the fact that humans are not rational consumers.

The horrors of compiling stuff take me back to my corporate job where I had to compile linux 2.x because a certain hardware vendor only had their driver tested on that.

"Overstepping its purpose" is key for "you were supposed to pretend to punish capitalists, not actually do it"