The case argument really solves everything whenever someone brings up poor choices
- Annoying glass back that scratches immediately and slides out of your hand- "just put a case on it"
- Undersized battery that won't last a day - "you can buy a case with a battery"
- The phone wobbles when you lay it on a desk or nightstand - "most people use a case anyway"
If we're meant to make our phones twice as thick, why not sell it in that form factor? Stuff that extra battery in there, make the backside grippy, and have it be able to lay down without being like a 4-legged chair where 1 leg is longer
I've never used a case on any phone. They're big enough as it is (in the xy dimensions). I did try it out of necessity when needing 2 phones in 1 pocket (work and private phone) for a week during a work trip. It's doable but just why
Arc Raiders is a great example of a modern and popular multiplayer game that works with proton. I haven't heard about it having a problem with cheating.
Marvel Rivals, Age of Empires 2 DE, Path of Exile 1/2, Last Epoch, Fall Guys are other such examples. In fact, Marvel Rivals even explicitly mentioned Bazzite in one of their changelogs! I can't recall an instance when a major game name-dropped a (relatively) minor Linux distro like that.
I think a big portion of that is the rather poorly made anti-tamper solution they are using called 'Theia' most cheat developers are too unintelligent to correctly reverse engineer this kind of binary obfuscation
Tiger Style is a coding philosophy focused on safety, performance, and developer experience. Inspired by the practices of TigerBeetle, it focuses on building robust, efficient, and maintainable software through disciplined engineering.
GitHub PRs don't solve anything about that, but I wouldn't have to spend (waste) time figuring out the contribution process. At least I learned a few things writing the patches. I learned nothing of value dealing with git email or Phabricator. It's just work of the boring and tedious kind.
Dealing with github is the boring and tedious thing, you have to run huge amount of proprietary javascript, keep up with their weird UX changes, start X11 to open a browser to render their html, overclock your CPU for a large PR review conversation to scroll without locking up your computer for minutes, constantly click "load more" since their webpage keeps hiding comments (while still lagging massively)...
Email is simple. It's just text, there's no weird javascript or html or lag. I don't have to open X11. I can just open mutt and read or write. I can type "git send-email". It's all open source, so I can read the code to understand it, and write scripting around it. It runs on any computer with ease. Even on a slow connection, it's quite speedy.
I totally agree with you about Phabricator though.
I have some unconventional workflows. And I try not to bother anyone else with it, especially in a volunteer driven open source context. It would be selfish to do otherwise.
To be honest based on what you've written here, keeping you out of my projects sounds like a good thing. What a bunch of piss and vinegar over how other people are choosing to work in a way that works for them.
Many projects have rules about what kinds of pull requests they accept. You would still have had to familiarise yourself with those rules, as well as the usual things like coding style, testing policies, etc.
Surely the claim being made is that the overall effort was increased in this case. That makes sense to me. I guess you can debate "but by how much?" but it seems fairly clear that there is more friction than there would have been via Github PRs
I have been using Syncthing fork since before the official app was discontinued, and can vouch for its quality. My favorite feature is that it allows conditional pausing of folders based on phone state, such as if the phone is charging or connected to WiFi. Just be warned that the version on Google Play was no longer updated last time I checked (Googles fault), so you're better downloading releases from the Github repo.
Completely anecdotally, but my personal experience over the past ~2.5 years of using Emacs has been the opposite of a dwindling community. Releases are frequent, often containing exciting new features; the community maintains many great packages, with new ones get released frequently; and I see more Emacs discussions online than I did when I started using Emacs, many of which involve new users. Emacs has a brutal learning curve, awful defaults and ancient bones, so will always appeal to a smaller number of people than VSCode or (Neo)Vim. However, for those willing to learn the arcane art, it can wield immense power.
Excited to try this. I was aiming to be done by Christmas, but this is my first AoC and reading other replies makes this seem a bit unrealistic. Decided to do it in elisp to try and improve my emacs-fu and lisp knowledge.
I use this; it does require changing the Firefox accelKey to something other than control, but works well. I also tried using nyxt but found it to be far too slow.
