Sadly, that’s not code Linus wrote. Nor one he merged. (It’s from git, copied from rsync, committed by Junio)

There’s plenty, but I do not wish to hijack this thread, so… have a look at the Forgejo 7.0 release notes, the PRs it links to along notable features (and a boatload of bugfixes, many of which aren’t in Gitea). Then compare when (and if) similar features or fixes were implemented in Gitea.

The major difference (apart from governance, and on a technical level) between Gitea and Forgejo is that Forgejo cherry picks from Gitea weekly (being a hard fork doesn’t mean all ties are severed, it means that development happens independently). Gitea does not cherry pick from Forgejo. They could, the license permits it, and it even permits sublicensing, so it’s not an obstacle for Gitea Cloud or Gitea EE, either. They just don’t.

There are no bugs. Just happy little accidental features.

It’s about 5 times longer than previous releases were maintained for, and is an experiment. If there’s a need for a longer term support branch, there will be one. It’s pointless to start maintaining an 5+ year branch with 0 users and a handful of volunteers, none of whom are paid for doing the maintenance.

So yes, in that context, 15 months is long.

A lot of people do. Especially on GitHub, where you can just browse a random repository, find a file you want to change, hit the edit button, and edit it right there in the browser (it does the forking for you behind the scenes). For people unfamiliar with git, that’s huge.

It’s also a great boon when you don’t want to clone the repo locally! For example, when I’m on a slow, metered connection, I have no desire to spend 10+ minutes (and half of my data cap) for a repo to clone, just so I can fix a typo. With the web editor, I can accomplish the same thing with very little network traffic, in about 1 minute.

While normally I prefer the comfort of my Emacs, there are situations where a workflow that happens entirely in the browser is simply more practical.

Or one could buy any of the existing pre-built splits. Which might be more expensive, but it does not involve something one very explicitly said they don’t want to do.

I’d rather spend twice as much on a well built keyboard with warranty than trying to solder one together myself and botch it up, and then it suddenly costs more than if I just bought a pre-built one.

And that’s relevant, how? (start of the thread)

And where do you think GitHub is?

Yep. So I don’t see why they wouldn’t enforce that extra win.

…and then risk the same litigation from Nintendo, or at least a DMCA takedown, something which the settlement explicitly mentions.

Well, citing IGN:

Citra, a Nintendo 3DS emulator, will also be discontinued.

The Citra homepage seems to confirm that.

On GitHub? No. It will get DMCA’d in very short order.

The single best thing I like about Zed is how they unironically put up a video on their homepage where they take a perfectly fine function, and butcher it with irrelevant features using CoPilot, and in the process:

• Make the function’s name not match what it is actually doing.
• Hardcode three special cases for no good reason.
• Write no tests at all.
• Update the documentation, but make the short version of it misleading, suggesting it accepts all named colors, rather than just three. (The long description clarifies that, so it’s not completely bad.)
• Show how engineering the prompt to do what they want takes more time than just writing the code in the first place.

And that’s supposed to be a feature. I wonder how they’d feel if someone sent them a pull request done in a similar manner, resulting in similarly bad code.

I think I’ll remain firmly in the “if FPS is an important metric in your editor, you’re doing something wrong” camp, and will also steer clear of anything that hypes up the plagiarism parrots as something that’d be a net win.

I think I can pinpoint the exact date things went sideways. It was a dark day on Monday, October 1, 2012.

https://deskthority.net/wiki/IBM_Adjustable_Keyboard maybe, or https://deskthority.net/wiki/Cherry_G80-5000? Something along those lines?

I use a keyboard with 64 keys (Keyboardio Model 100), with a layout that would likely drive any normal person mad: there are no numbers on the base layer, and all modifiers are on the thumb cluster. My top row is shifted symbols like @*$^%!&. I love it. I can reach every key without moving my hand, which helped tremendously with my RSI. With clever use of layers, one-shot modifiers & layers (where one-shot means that you press and release a modifier, and it remains active for the next keypress only), I have access to every symbol available on a traditional layout and more, without having to move my hand or do weird finger gymnastics.

It’s not a keyboard I’d normally carry (it’s heavy, split, and takes up more space than a traditional full-size one), that’s not why I like it small. I like it small because I don’t need to move my hand to reach all the keys, and that increases my typing comfort a lot. I have no use for a dedicated numpad: I can just press my right palm key and turn that half of my keyboard into a numpad. If I’m typing a single digit, I don’t even need to hold the palm key. If I’m typing a longer number, I can double tap the palm key to toggle the numpad layer on, and tap it a third time once I’m done. I don’t need cursor keys, because I can tap the left palm key to turn the keyboard into navigation mode: the right side controls the text cursor (ie, arrow keys, page up/down, home/end), and the left side controls the mouse. Most of the time, I don’t even need a mouse, because I can control the pointer from the comfort of my keyboard. I do have a trackball placed inbetween the two halves for the rare cases where I require more mousing than what is comfortable with keys, but… that’s not used all that often.

So, in short, the reason I prefer small and split is because they let me type without moving my hand, or stretching my fingers uncomfortably, and I still have convenient access to every symbol I need. I might need to do a bit more “work” to type certain things, but that’s a small price to pay for the comfort I gain by not having to move my hands.

I can write at ~120WPM with this setup (but I normally don’t need to, my normal typing speed is closer to ~60WPM, because my speed is limited by thinking speed, not my typing speed), I write code with this, I write prose in both English and Hungarian, and I even play some games with it! (Most games I play with a controller though, because I can do that from the couch.)

Just because it is small doesn’t mean it can’t do everything a full-sized keyboard can. I just do the same things in a different way, with different compromises. With a full-sized one, if you want to type numbers, you either have to move your hand to the numpad, or use two hands to type something like 1994. I can type that number with one hand, without moving my hand: instead of moving hands, I switch layers. With a full-sized keyboard, if you need Home, End, PageUp, PageDown or the like, you either need to move your hand, or you need whatever program you’re using to have different bindings for the same functionality. I can just press a key to go into navigation mode, and move the cursor whatever way I like, without moving my hands, or finding an alternative binding - works in every program, anywhere - instead of moving hands, I press an extra key. I found that pressing an extra key (especially if I don’t need to hold it) is more comfortable than moving hands. I also found that not moving my hands increased my accuracy, because I don’t need to find the home position when moving my hand back: it never moved in the first place.

In most games, I move with a mousetrackball, controlling everything with one hand didn’t quite work out for me. I do use the thumbstick to navigate menus or the like, and it works well for that. As for the thumb button: I usually bind that to Jump, or to Esc (or whatever other key gets me to the game menu). It really depends on the game how much I use the thumb button.

If I were building a gamepad, I’d build something very close to the Azeron, but probably replace the thumb stick with a D-Pad, or 4 buttons or something along those lines. I’d put those to better use than the thumbstick. And I’d make the thumb button trigger by pressing downwards, rather than out.

Although not a QMK-powered keyboard, perhaps an Azeron device could do the trick? I have an Azeron Classic, and it’s fantastic, friend of mine is very happy with her Azeron Cyborg too. They are built for gaming, they’re comfy, and reasonably customisable too. Comes fully assembled, so you don’t have to build it either.

A story like that, eh? Well, as it turns out, the entire configuration of my operating system is a story. Or rather, many stories.

Very bad, because the usability of such a scheme would be a nightmare. If you have to unzip the files every time you need a password, that’d be a huge burden. Not to mention that unzipping it all would leave the files there, unprotected, until you delete them again (if you remember deleting them in the first place). If you do leave the plaintext files around, and only encrypt & zip for backing up, that’s worse than just using the plaintext files in the backup too, because it gives you a false sense of security. You want to minimize the amount of time passwords are in the clear.

Just use a password manager like Bitwarden. Simpler, more practical, more secure.