I wonder what happened to Tails - the one that started it all.

Google has discovered that FOSS software under their full control is better than pure proprietary software for monopoly abuse and rent seeking. With FOSS software, they enjoy the automatic popularity that they otherwise would have had to market very hard for. At the same time, none of Google's free software is truly free. Google devs regularly neglect and reject overwhelming user requirements (jpegxl in chrome is probably the best example of this) and choose designs that clearly favor the company monetarily. It isn't even practical for normal people to fork their projects.

Google often uses their 'FOSS' projects to twist open standards or the market to their advantage. Android and Chrome are very significant players in this regard. Using Chrome, Google even managed to make the W3C standard too complicated for others to make alternative browsers easily. Google has similar ambitions in the multimedia market. They want to replace the monopolistic media formats with quasi-monopolistic formats like webp and av1 instead of truly open ones like jpegxl.

No problem!

Python is one of my primary languages (the other one being Rust). But it honestly isn't the easiest language to teach - I'm saying this from experience. There are so many concepts at play - name binding, iterators, generators, exception chains, context managers, decorators, ... . I could go on and on. Teaching becomes hard because any basic question could become a journey into the rabbit hole of python semantics.

Python is, however, a good first language for self learners. (Note: teaching vs learning). Python behaves intuitively. It's designed in such a way that if you guess something about the language, you'll probably be right.

How about YouTube? Video dislikes were a reliable indicator as to which videos to avoid. Now it's full of shitty clickbaits like 'NASA lied'. What was their excuse again?

Same with Reddit. They are now selling user data happily after their entire userbase revolted. Now nobody has a problem.

Looks like a good set of advice.

Matrix clients are slow and clunky because the protocol is heavy and overloaded. Upcoming sliding-sync feature will make them a bit more responsive.

Talking about specific clients, my favorite is Fractal. It's still missing some features though (like spaces). But it's getting updated fast.

I had the fortune of being the trainer for my company in all things git. I made sure that my colleagues (most of whom were straight out of universities) were introduced to git CLI and git concepts. No git GUIs were introduced. Consequently, the mess they made was easy to rectify. And then I occasionally read about horror stories like these where GUIs are allowed.

The PM?

The proper way to organize a branch is as a logical sequence of sub-features - each represented by a commit. Ideally, the commits should not break the build while introducing its feature. In many such cases, each commit may have a back story - the tests you did, your decision process, online references (that apply only to that commit - something like stackoverflow answers), etc.

Branch messages don't have the fidelity to capture such information. You may question the need for such detailed info. However, along with git blame and bisect, those commit messages are invaluable. I have lost count of how many times my own detailed commit messages helped me. And while I don't usually look at others' commits in such detail, I do read the details of commits that I'm interested in.

Git (and other VCSs) isn't just a snapshot tool. It's a history tool with the ability to capture history documentation. Honestly, Git is extremely underutilized in that capacity.

Neither has reached 1.0. They're perpetually unstable.