YouTube is a _disastrously_ unhealthy recommender system, and they've let it go completely out of control.

Green energy is not necessarily the cheapest form of energy. If it were, it wouldn't even be _hard_ to stop burning fossil fuels and prevent climate change.

paganel, when you say "Sorry for the Daily Mail link" it sounds like you know you're citing a source that will be extremely untrustworthy on this topic, and then did it anyway.

Your narrative is historically incorrect. Women invented many of the things that made software engineering _less_ tedious, such as debuggers (Betty Holberton, 1945), subroutines (Kay McNulty, circa 1947), assemblers (Kathleen Booth, 1947), linkers (Grace Hopper, 1952), and compilers (Grace Hopper, 1954). Programmers have always strived to make their job easier. If you don't see these inventions as creative effort, I don't know how to help you.

Even the parts of programming that were tedious were still important. If you saw someone tediously programming in assembly code today, you might celebrate the effort.

The flowcharts that these women were handed by their managers were not "program logic". There were many difficult details to work out about how to implement a program given the limited computing power of the time. You would not describe a manager today who draws a flowchart as having "written a program".

You are doing exactly the thing the article describes.

When I release ConceptNet, I would like to follow SemVer, but it kind of has to be in a way that the second component of the version is the major version, because there are bigger things that happen in a multi-decade project than just API changes.

The project is ConceptNet 5. It is the fifth project named ConceptNet. What it has in common with ConceptNet 4 is some of the data and the spirit of the problem to be solved; the design is quite different.

It's on the sixth major version after the initial release, so I call it ConceptNet 5.6. The current version is 5.6.4. If I wanted to use tools that expect SemVer, I'd have to call it something like "ConceptNet 5 v6.4". I find that confusing, and I think other people would too.

And if I had gotten to choose the newspaper, I would have chosen one that is more friendly and more representative of the local community than the glorified blog operated out of another state that I was ordered to use

It's different everywhere and it's usually not easy.

(I mean it would be great if there were a bank that did all its customer service over text chat, but that's too much to ask for, right?)

So now some of the ad targeting networks have me targeted as "woman who's a successful professional and knows what she's doing in life", which, uh, is correct up until that last part.

The robots are just not expecting a woman in her thirties to still be baffled and overwhelmed by fashion and looking for the basics. I get my most useful recommendations by word of mouth, and yay, that sounds very nice and authentic, but it's a slow process.

So this is a different problem than the original article: we could be targeted _better_ and both we and the advertisers would be happy, for at least a moment.

But. We're trusting the advertisers to use that information responsibly. What if the kind of people who make those anti-trans reply videos on YouTube start taking out deliberately divisive ads, targeted at the trans community? On balance, I think it might be better for the ad networks to not quite understand.

The point here is to run PyTorch code without having a Python interpreter, and without having to run slow Python code.

Of course you have to "do it for" the user. That's why you are the programmer and they are the user. If you're making something half-finished for other programmers to contribute to, that's very different from making a social network.

Back on Python 2.7.5, the UTF-7 decoder didn't do range checking, so this script [1] produced a "Unicode string" containing the codepoint U+DEADBEEF. (The maximum valid codepoint is U+10FFFF.) This string would crash regexes, corrupt databases, etc., so that allowed denial-of-service attacks against any function that let you specify an arbitrary encoding.

(This is fixed in all extant versions of Python.)

[1] https://gist.github.com/rspeer/7559750