squaresinger

I don't think so. We've all been happily having discussions with bots online for a long time now. People just don't notice that the person they are writing to isn't a human.

We went from talking in person to talking via computer and no talking with a computer. It's not getting better.

This.

The old forums are often still up, and there are still actual humans there, sometimes. But nobody goes there, because nothing's happening there.

There was this programming forum (blitzforum.de) that I loved when I was a teenager. I spent so much time there and learned so much. I actually attribute a lot of my career to getting an early start there. But the forum is mostly dead nowadays. People still open the page every once in a while, but nobody posts there.

Trolls actually saw themselves as an art from. Everyone else saw them as annoying cretins.

I agree with your comment.

Again, support is not development. Experiences with support does not allow conclusions on development.

And having no experience in development doesn't qualify you to make statements about development.

Because there's in fact no operator overloading happening, true, but that's mostly an under-the-hood topic.

It should not happen no matter why it does happen under the hood.

Operator overloading for string - string is wrong and type coercion to implicitly cast this to int(string) - int(string) is just as wrong.

This here is apparently the original source of the markdown specification, and there it clearly says that this is the correct behaviour: https://daringfireball.net/projects/markdown/syntax#list

Ordered lists use numbers followed by periods:

1. Bird
2. McHale
3. Parish

It’s important to note that the actual numbers you use to mark the list have no effect on the HTML output Markdown produces. The > HTML Markdown produces from the above list is:

If you instead wrote the list in Markdown like this:

1. Bird
2. McHale
3. Parish

or even:

3. Bird
4. McHale
5. Parish

you’d get the exact same HTML output

Yeah, and almost all languages I know then would throw an exception when you try to use - with a string, and if they offer multiple operators that take a string and a number, they always only perform string operations with that and never cast to a number type to do math operations with it.

(e.g. some languages have + for string concatenation and * to add the same string X time together, so e.g. "ab" * 2 => "abab". It's a terrible idea to have + perform a string operation and - performs a math operation.)

The NaN isn't an thrown. It's just silently put into the result. And in this case it's completely unintelligible. Why would an operation between two strings result in a number?

"Hello" - "world" is an obvious programmer mistake. The interpreter knows that this is not something anyone will ever do on purpose, so it should not silently handle it.

The main problem here is downward coercion. Coercion should only go towards the more permissive type, never towards the more restrictive type.

Coercing a number to a string makes sense, because each number has a representation as a string, so "hello" + 1 makes intuitive sense.

Coercing a string to a number makes no sense, because not every string has a representation as a number (in fact, most strings don't). "hello" - 1 makes no sense at all. So converting a string to a number should be done by an explicit cast or a conversion function. Using - with a string should always result in a thrown error/exception.

You aren't wrong, it wouldn't be bad for it to just print the help in that case, at least when running interactive.

For automation, printing the full help of a more complex command would completely trash logs.

You can not change history for any published changes - like I said, doing so makes your repository incompatible with any other clone.

That's the same on Git.

You mean with an actual plan?

"Agile development" (aka business substituted a plan with utter chaos and daily changing super-urgend demands) has ruined our industry.

Agile done right can be helpful, but in 95% of times, agile isn't done right.

Electrical engineering can't quite work like that because if you want to try out a change you have to order new, expensive prototype boards that take time to be finished and delivered. Can't just run a new pipeline and have the new version in production within minutes.

Does gtfo() then work as expected?