Makes sense to me, since the technology landscape has drastically changed since the project inception. You'd probably need to start developing from scratch anyways, if you wanted to bring that up to modern standards...
For what it's worth, being a professional software engineer, I expected that list to be at least a magnitude longer. I guess, it doesn't include all their internal projects. But yeah, you would not believe how much shit we throw at the wall and how little of it sticks, particularly not for more than a few years.
I once heard the figure that IT investors expect 1 out of 20 investments to pay out, which feels about right to me...
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...
Du meinst nachdem die Politik sich um ein Verbot einer Regenbogenflagge kümmert anstatt richtige Probleme anzugehen. Wenn Klöckner nichts getan hätte, wäre sie weniger menschenfeindlich aufgetreten.
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...
Not an expert, but I find a good bit of context here is also that in the elections in 1932 and 1933, the three strongest parties were:
- NSDAP: National Socialist German Workers' Party
- SPD: Social Democratic Party of Germany
- KPD: Communist Party of Germany
So, it really was just popular at the time to say you were doing socialism, but they also weren't actually fooling anyone who really wanted these politics, since two other viable and more obvious choices existed.
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...
On KDE, I'd recommend getting a KWin Script for tiling. Krohnkite is what people use currently.
It's not as buttery smooth as dedicated tiling window managers and it can be a bit glitchy at times, but it is better than one might expect and significantly easier (and likely less glitchy) than trying to get bspwm to work in Plasma.