Right, you do have to understand that either way, if you put something on the public internet, it is gone.

I don’t want a company to sell my data, making money off of me, then having the audacity to ask me for MORE money on top (nitro). It feels gross.

I don’t mind sharing bits of myself online otherwise.

The owners of federated instances can also just start selling your data too at any point. And as you said, advertisers will also just scrape public data trivially. Basically, the internet and world is a terrible place.

But Discord has cultivated a queer membership by serving a different need than those platforms: privacy.

Yeah, gonna stop reading right there. Discord is absolutely selling your data. Nothing against inclusivity features though.

Discord became ubiquitous because it works well, and is free. Take VC money, run at loss, get tons of users, enshittify, die because something better becomes good enough. It’s just another one of those speed runs, which will happen over and over again until the end of humanity.

Also, how do I verify that this fork isn’t malware wrapped in emulator code?

The code is open source, you read it all, ensure that you download exactly the code you read, and you compile it yourself. That’s the only way, in general, to accomplish this.

The JetBrains AI plugin wants to be activated so badly, but legal says we can only use GitHub copilot. The copilot plugin is really good so I don’t mind, but we all know the data is going to OpenAI regardless of the plugin. Data sovereignty will only be achieved by running these services locally.

This right here. Get good at navigating code of questionable quality that you didn’t write. If you can’t do it, start questioning your tools, and mastery of those tools. For the big boy jobs, you should be working with existing code much more than writing new code. Learn to get excited by tweaking existing systems with a few well placed, well researched changes, instead of being The Asshole that adds a new abstraction wart.

To me, a corporation cannot maintain quality code because requirements are ill defined, and there is no “done” state. With those two conditions present, unable to be changed, it’s not possible to form a coherent codebase. Those who try will make things worse, because their abstractions won’t fit in a year or two.

This is exactly the “messy code” people then leave behind. Bad code can come about for other reasons too, of course, but this is one of the more annoying reasons, because someone wrote it with self-righteousness, as if they were the only people to truly SEE the problem. Sigh.

It’s fine, this is how enterprise works. You can learn to navigate and make a living from it. You MUST internalize and accept that it is NOT the same as maintaining code for an open source library or whatever people think it’s going to be.

You have to listen to your heart, at least once in your career, to learn that grass on the other side is covered in just as much dog shit as it is over here.

deleted by creator

deleted by creator

Same, shit just works. I don’t even want anything I print to be color, by design, because it always is terrible anyway.

I go to Costco, I get hot dog. This is the way.

deleted by creator

YAML comes with its own unique pains in the ass https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-from-hell

These things actually matter, come up often enough to actually be annoying, and are a bit difficult to explain and learn into people. You’re basically fine if you just string quote everything that you can, but nobody does that.

MULTI-TRACK DRIFTING!! Which also kills the other lever guy, bonus!

To be that dick, a headless component library is still meant to do something, show an example of it being used!

The encryption: base64 encoding

Nah lol I’m good

Christ, do this many people really find iso8601 hard to read? It’s the date and the time with a T in the middle.

Using a TUI however makes you an absolute beast mode rockstar engineer

Packages often have recursive dependencies. There are some conscious packages that go the extra mile to not have any dependencies, but it’s very rare in the JavaScript ecosystem. Welcome to hell. You can at least use dev dependencies to avoid downloading them in CI etc., but that’s about it.