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.
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...
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 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.
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.
Man pages are displayed in less (which acts as the so-called "pager" here), so you can search man pages interactively like you search in less. And you do that by pressing /, then typing your search term and pressing Enter. Then you can jump between results with n and Shift+n. This is also how search works in vim, by the way.
Perhaps another tip in this regard, to search in your command history with Bash (for re-running a command you've previously used), you can press Ctrl+R, then start typing your search term. Pressing Enter will run the displayed command. To skip to older search results, press Ctrl+R again. If you want to edit a command before running it, press → or Ctrl+F instead of Enter.
This UI is a bit fiddly in Bash, but worth figuring out.
As for Fish, it's great for new users, because:
it has a much more intuitive Ctrl+R UI, displaying all the search results interactively and not behaving weirdly in certain situations.
it automatically sifts through your command history as you type and suggests the most recent command which starts with the prefix you typed. You can fill in its suggestion with → or Ctrl+F, or only use the next word from it via Alt+F. You can skip to older matches with ↑, which is then a proper search like Ctrl+R in Bash, so not just prefix-matching. And yeah, overall just really useful, because it'll both make it quicker to run frequently-used commands, and sometimes suggest a complex command which I didn't even remember that I once ran.
its tab-completion shows short descriptions of what most (sub-)commands or arguments do.
But:
don't set it as your system-wide default shell or there's some chance of shell scripts not executing correctly. What you should do instead, is to set it as the startup command to run in your terminal emulator.
the syntax of Fish is somewhat different to that of Bash, which can be confusing when you're still learning the Bash syntax. It's not the worst thing in the world, as it basically only affects scripting and more complex command chains.
Scripting is not a problem, because you can throw a shebang into the first line to use Bash syntax (#!/bin/sh or #!/bin/bash). You should add a shebang to your scripts anyways.
And running more complex commands isn't too big of a deal either, because you can run bash in your terminal to launch Bash, then paste the command into there to run it, and then quit back to Fish with exit or Ctrl+D. Typically you'll know to run bash, because Fish's syntax highlighting turns red after you've pasted a complex command.
Oh yeah, I'm in favor of using type hints. People here are also saying that Pyright is more useful, which I haven't used yet.
I was involved as the unlucky bastard supposed to sprinkle software engineering on top of a Python project 2+ years ago, and I just remember how much I understood right then and there why Python devs thought static typing was cumbersome. Felt like I had to write Java again, except it also didn't work half the time.
Interesting. If it's only in the type checker, can IDEs/editors correctly show the type information of inferred types then? Do they call the type checker themselves to retrieve that info?
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.