Apparently the screenshot is to be read as Catturd proudly proclaiming that democrats weren't even briefed, so they could not have leaked anything.
But when Trump said a few days later that democrats leaked information, Catturd still immediately accepted that as truth.
Ephera
joined 5 years ago
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.
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?
Honestly, at this point just plonk down a few traffic lights and pretend it's a normal intersection. At least assuming that center piece isn't elevated.