What I find interesting is that my bank has kind of the opposite stance. It allows you to do a lot more things if you login via their website and I think they overall trust your actions more if you do it over the browser, but you are required to pass a lot more security checks, while on the app a PIN is enough, but it also doesn't allow you to do as much.
Saying that he praised a genocide is very dishonest. If I claimed people in the US were forced to go to universities, where they are forcibly sterilized, beaten and indoctrinated, you wouldn't be praising atrocities if you rejected that claim and praised universities for the good they actually do for society.
I wonder what sort of mitigations we can take to prevent such kind of attacks, wherein someone contributes to an open-source project to gain trust and to ultimately work towards making users of that software vulnerable. Besides analyzing with bigger scrutiny other people's contributions (as the article mentioned), I don't see what else one could do. There are many ways vulnerabilities can be introduced and a lot of them are hard to spot (especially in C with stuff like undefined behavior and lack of modern safety features) , so I don't think "being more careful" is going to be enough.
I imagine such attacks will become more common now, and that these kind of attacks could become very appealing for governments.
I wouldn't trust ChatGPT with teaching me about some tool. It in my experience very convincingly spews out stuff it invented, and if one is still learning I can see it being hard to spot those errors. I use it to fix syntax errors in SQL queries, though, since I can't be bothered to try understanding the not-so-helpful error messages I get with my queries, and because if chaptgpt tells a lie it will be caught by my syntax checker.
So, I guess you can use it, if you always assume it to be trying to mislead you until proven to the contrary.
When using git and are working on a feature, and suddenly want to work on something else, you can use git stash so git remembers your changes and is able to restore them when you are done. There is also git add -p this allows you to stage only certain lines of a file, this allows you to keep commits to a single feature if you already did another change that you didn't commit (this is kind of error prone, since you have to make sure that the commit includes exactly the things that you want it to include, so this solution should be avoided). But the easiest way is when you get the feeling that you have completed a certain task towards your goal and that you can move on to another task, to commit. But if you fail you can also change the history in git, so if you haven't pushed yet, you can move the commits around or, if you really need to, edit past commits and break them into multiple.
I think I have seen as many VGA cables as I did HDMI ones. I also have seen many people using adapters for the two standards. So I think they are still very common.
But I don't want to choose my emojis based on the colour of my skin, I'd prefer to use something "neutral", and while yellow as you said is not really neutral, it's the closest thing we have to a neutral colour from all available options. I also don't think unicode requires that the unmodified emoji be rendered as being yellow (correct me if I'm mistaken), and it's probably apple and google who just decided that their fonts should render them as being yellow. I imagine one could with another font make them be magenta or some other color.
Weirdly OSI doesn't classify the SSPL as an open-source license because it doesn't guarantee "the right to make use of the program for any field of endeavor", calling it a fauxpen license. I don't think the FSF has commented on the license, though I would be curious what they say about it.
I imagine they consider it to not give the right to make use of the program for any field of endeavor, because providing the source of the entire stack needed to run the service you provide makes it impossible for users to host their service on stuff like AWS, since it is proprietary.
What I find interesting is that my bank has kind of the opposite stance. It allows you to do a lot more things if you login via their website and I think they overall trust your actions more if you do it over the browser, but you are required to pass a lot more security checks, while on the app a PIN is enough, but it also doesn't allow you to do as much.