I can’t vouch for this particular playlist / series since I haven’t watched it, but the channel (Crosstalk Solutions) is great, and so I expect that their home networking 101 is as well.

https://youtube.com/playlist?list=PL1fn6oC5ndU9l3eYa7S_s206JUpbIa-8m

Do you throw away all your cables when new features are added?

Only when you start to own a device that uses one of those new features?

this

Development of the Wayland specification and multiple Wayland compositors is funded by the X.org foundation, and done largely by current and former Xorg developers / maintainers.

So it still works!

I should have guessed.

Thank you 🤣

Bash scripts are rarely the best choice for large, complicated, programs or for software that requires complex data structures. (Git is very much in both categories)

In bash there are so many ways to accidentally shoot yourself in the foot that it’s absurd. That can lead to bizarre seeming behavior, which may break your script, or even lead to a security vulnerability.

There are things that make it a bit more manageable, like “[[]]” instead of “[]”, but a frustrating number of such things are bash specific and this is written for the subset that is POSIX shell, meaning you don’t even get those token niceties.

Where you generally “want” to use POSIX sh is for relatively simple scripts where the same file needs to run on Linux with bash, Linux with only BusyBox sh, OSX with zfs (and an outdated version of bash which will never be updated because Apple refuses to ship any GPLv3 software in MacOS).

This is not that, and so one would expect that:

1. The developer of this git implementation has poor / foolish judgement.

2. Shit will be buggy

3. Shit will be insecure

4. Shit will be a PITA to try to troubleshoot or fix

5. And shit will be slow, because bash is slow and this isn’t a job that you can just hand off all of the heavy lifting to grep / sed / awk*, because the data structures don’t lend themselves to that.

* You could write the entire program in awk, and maybe even end up with something almost as fast as a python implementation done in ⅒ the time, but that would be terrible in other ways.

It has already been translated into rust. Python wasn’t ever intended to be used in the “real” driver, but I thought it was a fun anecdote none the less.

Fun fact!

The Asahi Linux drivers for the Apple M1 GPU were originally written in Python: https://asahilinux.org/2022/11/tales-of-the-m1-gpu/

GPU drivers in Python?!

Since getting all these structures right is critical for the GPU to work and the firmware to not crash, I needed a way of quickly experimenting with them while I reverse engineered things. Thankfully, the Asahi Linux project already has a tool for this: The m1n1 Python framework! Since I was already writing a GPU tracer for the m1n1 hypervisor and filling out structure definitions in Python, I decided to just flip it on its head and start writing a Python GPU kernel driver, using the same structure definitions. Python is great for this, since it is very easy to iterate with! Even better, it can already talk the basic RTKit protocols and parse crash logs, and I improved the tools for that so I could see exactly what the firmware was doing when it crashes. This is all done by running scripts on a development machine which connects to the M1 machine via USB, so you can easily reboot it every time you want to test something and the test cycle is very fast!

Roma.

G* has always been a slur.

I know it’s really hard to tell, especially with flat earthers, but I think this post by “gerwin” screenshat here (with extra jpeg) was satire.

There are a lot of silly explanations that flat earthers have for things, but this doesn’t appear to be one of them.

(Googling for “water mountain” just gives this screenshot and people making fun of this screenshot.)

Re-write, please let me know if I misunderstood:

I spoke about suicide in the venting sub and got permabanned from all of reddit for “advocating violence”.