I’d say it depends on WHY you like the art. Does it tie into the toxic or reprehensible traits of the artist? Was the artist trying to send a toxic or reprehensible message with this art?

If not, then it’s just a matter of ensuring that your enjoyment of the art doesn’t translate into support for the artist. Or, at least, that it doesn’t cross your personal line of support for the artist.

So, for example, does the Kanye music you like have nazi themes or messaging? Far as I’m aware, no, the nazi-ism is just his newest shit, so you’re probably fine as long as you’re not streaming from Spotify or YouTube, or otherwise giving him revenue.

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.

And here I thought the fact that it’s spelled “Cucumber” and not “qcmbr” was the giveaway that it’s a joke.

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.

For Canada, unfortunately no. Unless Microcenter is available up there, that’s my go-to these days. You could maybe try them out online, I dunno if they’d ship to you.

Newegg lost all credibility with me years ago.

The presentation is different, but the core problem that the FTC is targeting is the same: spending real money to gamble on artificial digital goods.

A very large portion (maybe not quite a majority) of software developers are not very good at their jobs. Just good enough to get by.

And that is entirely okay! Applies to most jobs, honestly. But there is really NO appropriate way to express that to a coworker.

I’ve seen way too much “just keep trying random things without really knowing what you’re doing, and hope you eventually stumble into something that works” attitude from coworkers.

As someone with 0 investment in this whole ecosystem, I saw and perused this article like a week ago, and my immediate impression was “Why is this guy constantly saying ‘Wayland breaks XXXXX’? Wayland isn’t breaking anything, it’s new tech. Wayland has certain features, or it doesn’t or doesn’t yet. The only folks breaking anything are those swapping use of X with Wayland, within various apps or tech stacks, potentially prematurely, where Wayland doesn’t yet have the full set of features needed.”

Whoever this is seems to have a really poor understanding of long-term software development, despite being way more invested in it than I am.