Ephera

Maybe they didn't slaughter her with how many fans she has? Cows can live to be twenty years old. But yeah, probably wishful thinking...

Yeah, after writing that comment, I was thinking, if I do promote it, that means there's a certain expectation that I'll integrate or implement functionality that others want. At that point, it becomes less of an egoistic thing. And I'll be doing more communication and whatnot, therefore less programming.

Maybe that's the puzzle piece that OP is missing? If you don't promote it, you have practically no extra work compared to developing it under a proprietary license. In fact, it often reduces the workload, if you can just post it publicly without having to secure the repo.
And you don't incur costs from giving it away either. So, if you make sure to only put in the work that you want to put in in the first place, you have no disadvantage from publishing it with an open-source license.

Incidentally, you can also play !dcss@lemmy.ml to train Vim navigation with HJKL keys.

I mean, DCSS does also have diagonal movement keys, which are most definitely not a thing in real Vim, but uh, you can probably just ignore those. So long as you're not trying to win the game, anyways...

Are you referring to the workspace feature of uv? Is that working well?

Management might want us to revive a project from a few years ago, which is like 5% Python, but for which we had to build a ~~homegrown~~ horrid implementation of workspace builds, using shell scripts and symlinks. We'd definitely want to get rid of that, if uv's workspace builds work at all, really. 🫠

I mean, it sounds like it's gonna be a fairly large codebase. Rust is definitely better equipped for large codebases than Python...

I do agree that Python could give them more outside contributors, but from my experience, I don't think it's worth swaying from your preferred tooling for that. Outside contributions will make up barely a fraction of code changes either way, so you should rather ensure that your core team is productive.

Many people enjoy programming, you know. I've got like ten reasonably-sized projects and I haven't posted about them anywhere. Because I built them to scratch my own itch, both in terms of functionality I could use and the itch to build something, no matter what it is. I'm not wasting my time, because I'm doing something I enjoy.

The system for domain names is called Punycode: https://en.wikipedia.org/wiki/Punycode

But it's still combined with domain registrars rejecting names like "αpple.com", which ultimately needs a human to approve names.

There could also be a system like here on Lemmy, where there's a separate display name, but it still doesn't really solve the impersonation problem...

The problem is, even if it were solved for 99% of systems, 1% of systems crashing is still a massive problem.

But yeah, I also don't believe that it is solved for 99% of systems. There's a ton of embedded systems all over the place, which are easy to forget about.

French kiss?

Yeah, it's great. Farmers need to use pesticides and monocultures to stay competitive, since other farmers are using them. Also, pesticides and monocultures kill the ecosystems that provide things like natural pest control, pollination and humus. So, you probably don't get an increased yield from pesticides and monocultures when they're employed in wide areas, while you do still get the destruction of ecosystems.

It is similar to Bluesky, yes. They both got a lot of inspiration from Twitter (before Musk turned it to shit/X).

And I would say that the discussions are more shallow than on Lemmy. Even though Mastodon has a higher character limit than Twitter and many Mastodon instances effectively remove the character limit, it's still fundamentally a platform for shortform interactions. Infodumping is rarely seen, because you need to create a silly number of chained messages.

On the flipside, though, you get to know people. I do appreciate the time I spent on Mastodon, because of that. It's a very different perspective as not everything is about discussing cold hard facts, but rather also people's hobbies and struggles and whatnot.

Not sure what your problem with Discover is. It uses PackageKit under the hood, which hooks into APT (as well as other distros' package management).

If you want to, you can disable Flatpak and Snap support in Discover's settings and then it is effectively just an APT frontend.