My big reason would be “it hurts readability”. That is, when writing code, readibility for others who aren’t familiar with it (including future me) is my top-priority, and that means indentation and alignment are HIGHLY important, and if I spend the time to write code with specific indentation and alignment, to make it readable at a glance, I want to be certain that it’s always going to display exactly that way. Tabs specifically break that guarantee, because they’re subject to editor settings, which means shit like the below example can occur:

I write the following code with an editor that uses a tab size of 4.

myObject.DoSomething(
    someParameter:      "A",
    someOtherParameter: "B",
    value:              "C");

If someone pulls this up in an editor that uses a tab size of 8, they get…

myObject.DoSomething(
    someParameter:          "A",
    someOtherParameter:     "B",
    value:                          "C");

Not really a big deal, in this simple case, but it illustrates the point.

My second reason would be that it makes code more difficult to WRITE, I.E. it’s not that hard to insert spaces when you mean to insert tabs, considering that you’re not LITERALLY using only tabs just only tabs for indentation and alignment. And if you do accidentally have spaces mixed in, you’re not going to be able to tell. The guy on another machine with different editor settings will, though.

I’m aware there are fonts that can make spaces and tabs visible and distinct, but that sounds like a NIGHTMARE to write and read code with. I mentioned above, my top priority is easy readability, and introducing more visual noise to make tabs and spaces distinct can only hurt readability.

Denying that the logo used to have a cornucopia is a thing? Sheesh, TIL.

Arcane.

Not banned… at least not that I know of. Just saw the writing on the wall after the API horseshit.

Part of the reason that “JavaScript sucks” is BECAUSE it doesn’t have alternatives. If you want to build a WebApp that manipulates the DOM, JS has the ONLY API to do it.

For me, “JavaScript sucks” not really because of the language itself, but because there’s such a massive disconnect between what it was designed for (small amount of bells and whistles within a web page), and what the ecosystem uses it for (foundation for entire GUI applications).

If you want to build WebApps, learn JavaScript, then do all your development with TypeScript, and be VERY mindful of the third-party dependencies you pull into your project.