spartanatreyu

The first problem is they're letting AI touch their code.

The second problem is they're relying on a human to pick up changes in moved code while using git's built-in diff tools. There's a whole bunch of studies that show how git's diff algorithms are terrible, and how swapping to newer diff algos improves things considerably.

TL;DR on the studies:

• Only supporting add/remove/move operations is really bad.
• Adding syntax awareness to understand if differences in indentation should be brought to a reviewer's attention, improves code and makes code reviews more accurate. (But this is hard because it's language dependent)
• Adding extra operations (indent/deindent/move/rename-symbol/comment/un-comment/etc...) makes code review easier, faster and more accurate. (But again, most of this requires syntax awareness.

There's also a bunch of alternative diff algos you can use, but the best ones are paid, and the free ones have fewer features. See:

• https://www.gitclear.com/rich_diff_checker
• https://semanticdiff.com/
• https://difftastic.wilfred.me.uk/

Looks like you can't distribute a modified version of the project (e.g. a fork), but it wouldn't stop anyone contributing to or distributing a separate project that users could run locally to patch duckstation's build process where they can now build it on and for their own machines.

A build patch wouldn't contain any copyrighted material, so anyone could contribute and distribute it.

Ironic considering that's how many emulator get around legal issues. Emulators distribute virtual machines, but they don't distribute the copyrighted material.

the dev deliberately changed the license to his source code to prevent forks

The licence is a creative commons licence and hasn't been changed in 11 months.

I'm not sure what you're talking about

1. ~~Any dev can fork it and do the work themselves~~ Edit: Project is licenced to disallow forks (but that wouldn't stop the community from supporting linux builds, see my comment further down the chain)
2. Community forks can exacerbate rather than fix the problem, see the Fedora OBS fiasco (link: https://www.youtube.com/watch?v=dJJvq3dpylM)

I have to disagree here thanks to one great and recent counterexample:

Remember OBS getting hammered by error reports that had already been fixed ages ago?

Fedora had a habit of building and distributing their own version of third party projects.

Fedora users were downloading OBS but they were getting the broken Fedora repackaged version instead.

• Users were pissed that OBS wasn't working.
• The OBS devs were telling users these issues are fixed and to update to the latest version.
• As far as the users could tell, they were already on the latest version which pissed off the users even more.
• OBS devs figured out what was going on (users had the borked unofficial distribution installed) and told users to switch to the official version
• Most users didn't know how to do that and kept bombarding OBS with issues.
• OBS devs asked Fedora to stop linking to the borked version over the official version in their OS
• Fedora devs said no.

No matter how many times OBS tried to get Fedora to change what they were doing, the Fedora devs wouldn't budge.

It led to OBS threatening legal action against Fedora:

See: https://gitlab.com/fedora/sigs/flatpak/fedora-flatpaks/-/issues/39#note_2344970813 Video version: https://www.youtube.com/watch?v=dJJvq3dpylM

Fedora finally started listening to application devs after that.

Podcast interview discussing resolution: https://www.youtube.com/watch?v=oKP1hgdFJKo

Now for Duckstation it's a similar thing.

Arch (AUR) has a borked distribution that they're linked to instead of the official version.

The one difference is that OBS has financial support from paid streaming software that uses OBS as a base, whereas Duckstation doesn't.

Which means that Duckstation doesn't have the financial backing to legally compel Arch to drop their borked distribution.

So their only recourse is to make a public appeal saying if this isn't fixed, I'm dropping support entirely.

Entirely understandable.

Or, maybe they don't have enough contributors to manage all the issues coming in

Most new users won't even know that there is a choice until they're presented with it, and most will just stick with the default option anyway. (which most distros have/are switching to wayland)

The top comment in the linked article pointed out how that chunk of text was less than truthful:

There’s definitely regressions that need to be fixed, but the way it is presented here is just misinformation, mixing things like project-specific bugs and misunderstandings in as Wayland problems.

*BSD is officially supported by Wayland and by several display servers (a better state than for X11 where the *BSD’s had to patch things quite extensively downstream), the graphics tablet thing is a KDE-specific bug, and global hotkeys is available in some display servers through XDG portals (albeit a bit slowly), and using multiple independent mouse cursors is very specifically a Wayland feature (wayland multi-seat). Restoring window state is also supported, it just works differently than X11, and sway at least supports global fullscreen the same way as i3. [...]

The other comments pick out the other issues the top comment didn't go through.

If you want to shift your hands around on the voyager, you can only really shift up/down and not left/right because of how steep the middle finger is shifted up (aka how staggered the columns are).

Compare that to the moonlander where the columnar stagger is smaller so it's easier to shift left/right as well.

If you want a left/right shift and you're okay with two close thumb buttons, it might be worth going with the moonlander and add these key caps to "bring" the thumb cluster closer: https://www.thingiverse.com/thing:4948862

I recommend getting a switch tester with a bunch of "silent" tactile switches.

They have a muted thock that is much less annoying to be around.

For me I settled on Gazzew Boba U4 Silent Tactile Switches (the 62g clear version) in my moonlander (also using colemak-dh). I've also been looking at the voyager since the thumb clusters look like they're in a much better spot than the moonlander's which can feel like you have to pull your thumb back further than it goes to reach the keys if you don't mod your board (I have no idea what they were thinking with that positioning, it's so unnecessarily far away from the base keyboard compared to their other keyboards).

But definitely get the switch tester, because everyone's preferences are so different and finicky.

Oh behalf of everyone else around you.

Please don't put loud switches on a portable keyboard you're going to take around with you.

If you're taking them in public, you're probably going to be wearing noise cancelling earphones and you won't hear the noise anyway, but everyone else will.

Wait until you learn about firefox's container tabs (confusingly renamed to multi-account containers)

Instead of needing to sign in/out to switch accounts, you can set up this thing called container tabs.

Each container tab is given it's own color and is basically it's own copy (aka container) of firefox.

So I can click the new tab button then click blue and I have a tab that is already signed into my work microsoft, google, etc accounts.

And I can click on purple and I have a tab that is signed into my personal microsoft, google, spotify, etc accounts.

And both tabs live in the same tab bar, but the websites/accounts inside each tab can't see each other.