The open source community works in mysterious ways. This bug reminds me about the audio via HDMI bug for old radeon video cards. A simple flag in kernel configuration could have fixed it, yet the bug has been present in kernels from something like 4.1 to 6.0. It only recently has been fixed, after years of having to patch your kernel for a very simple bug.
When it comes to open-source software, usually it’s absolutely critical bugs that get patched or necessary features that get worked on, since it’s really just volunteer work.
Pay every contributor a salary to make the program “feel” nice instead of actually bloody work (hi every ms app), then we’ll talk.
I’m not a fan of the inability to drag a tab into a snapping position, I have to drag it out, then drag the new window to the snap location.
And apparently this has been a documented issue for 15 years, and there’s been little to no progress in all that time.
The open source community works in mysterious ways. This bug reminds me about the audio via HDMI bug for old radeon video cards. A simple flag in kernel configuration could have fixed it, yet the bug has been present in kernels from something like 4.1 to 6.0. It only recently has been fixed, after years of having to patch your kernel for a very simple bug.
The secret is fixing it yourself and submitting a pull request for approval/further additions.
Unless its GNOME in which case the maintainers will tell you to screw off and you will promptly switch to a better alternative.
I’m trying, I don’t know much about JS or the Firefox codebase, but I’ve been reading for hours and I’m getting a grasp of how it currently works.
Now I’m tryna see how chromium does it to either replicate, or inspire.
When it comes to open-source software, usually it’s absolutely critical bugs that get patched or necessary features that get worked on, since it’s really just volunteer work.
Pay every contributor a salary to make the program “feel” nice instead of actually bloody work (hi every ms app), then we’ll talk.