True that. But I feel like you can at least glean something from what pictograms they choose to express themselves with. Like how you can with the posters they choose to hang in their room.
That falls under being ignored. Most people will only realise it's a big deal if enough noise is made about it. Sony would maybe lose 10% sales from people quietly quitting, but still profit from the decision long-term. Right now the news article was only written, and we're only talking talking about it, because enough people made a fuss. That's how protests work; they're not convenient or polite.
I always thought this stance to be interesting, because it reminds me of soldiers in a conflict. The arguments are that the enemy rank and file are just doing their jobs, they have a family, the actual evil bigwig is out of reach, etc.
But also, are you just going to do nothing and let them steamroll you? They're choosing to continue to work at that business, and are the only "frontline" that you can interact with. The fact that the business made a policy specifically addressing this common complaint, means it actually reached the ears of someone in power.
I'm not encouraging violence or anything of course. But, by design, there's nobody else to voice your displeasure to. The only other option is to quietly accept their changes and be ignored.
If they didn't want angry people calling, maybe they shouldn't make terrible decisions?
I like how in their remediation suggestions they "gloss" over windows as an unavoidable bird genocide fact of life. Abolish windows! !fuckwindows@lemmy.world
Video hosting and distributing is very expensive. YouTube operated at a major loss for a while, and maybe still does, I'm not entirely sure. Lemmy is much cheaper as a text and occasional image platform.
I considered doing streaming for a while. I looked into Peertube and the Twitch fedi thing I forget the name of, wondered why there was only one Russian guy streaming, balked at the hosting fees, and gave up.
By that I mean you have to be careful which libraries you use. There's a good chance that a System.* or random NuGet package will either completely fail to run on Linux, or be horribly buggy if you force it to work via build flags. In fact, they've completely removed the build flag in .NET 7+, System.Drawing.EnableUnixSupport. It used to be supported via libgdiplus.
I would expect .Net to be fully compatible with Linux out of the box. Especially system libraries. You can't say that you support cross-compatibility, and then deprecate cross-compatibility of system libraries; that's just insane.
I don't remember the exact details because it's been several years, but it was far more than just System.Drawing.Common that broke on Linux after updating to .Net 6. Some breaking changes were undocumented, only appearing later in GitHub issues. Some were buried in sub pages or individual library documentation.
In the patch notes they even had the gall the claim that our business use case doesn't statistically exist, and we can just drop in replace SkiaSharp; which was absolutely not the case. It was an unmitigated fucking disaster, even accounting for rolling back to .Net 3.1 for a few months while we sort it out and wait for critical 3rd party libraries to accommodate the change. Before anyone says it, yes we actually paid handsomely for our critical third party libraries; we didn't mooch off open source and whinge about it. Even so, it never really worked right after that change. A hundred small things, like differences in how SkiaSharp draws differently and handles edge cases. In an enterprise application, it was a big problem.
Shamed*