That lazy culture is exactly why discord is bad for the job. I search for solutions first, instead of barging in with a question that may have been asked and resolved a thousand times before.

Recommending the use of a software for a purpose it wasn't meant or designed for, is the real bad argument. There are a lot of projects that use forums for support questions just fine. Instead when you offer a chat room, people will try to get away with quick answers. But it rarely ends up like that and all the conversation that ensues also becomes buried.

Short lesson - use software for what it's meant for. Don't shoehorn a support forum's job to a chat application simply because people already use it.

But calling that doff is misleading.

Git actually uses diffs behind the scenes a lot - 3-way diffs/merges to be more accurate. Merging, rebasing, cherry picking and even reverting are all 3-way diff-merges.

Can I interest you in a Torvalds rant?

Dape looks dope! As an eglot user, I was holding back on dap-mode due to all the dependencies it pulls in. I guess others had the same issue. Meanwhile, GDB recently added a native DAP interface. So, good timing overall!

Not really. Rewriting something in Rust has some obvious advantages. But those advantages diminish with the age of the old code base. For example, the biggest advantage is memory safety. But old C or C++ code bases would have undergone so much real world use and testing that most of the memory safety bugs would have been corrected anyway. Similarly, the new code (in Rust in this case) may fail to capture lessons from the old code that may not be well documented.

For these reasons, the common approach followed is to wrap old code in safe Rust and use it, instead of completely rewriting it in Rust. This was a stated objective (C & C++ FFI) of Rust project since its early days. This is also the reason why core Rust team often doesn't support the RiiR zealotry.

In this case though, the developers of fish themselves decided that the hassles of C++ is worse than completely rewriting such a big and old code base in another language. I'm interested in C++ as well, though Rust is my primary language these days. I thought that it would be interesting to hear the experience of someone who made this unusual decision after dealing with both languages.

I think that you can add a WIP prefix to the MR title to prevent the maintainers from accidentally merging the branch prematurely.

What is to prevent the chrome developers from selectivity bypassing the content of the block list in the future?

Protobuf is also not a proper binary alternative for Yaml. Protobuf needs a schema in the form of its IDL. Cbor and messagepack might be more analogous.

Gamers and typists/coders are completely different species. Besides, WASD keys don't use lateral extension (assuming gamers use touch typing at all). Have you checked out any KB layout communities?

That would be a bad design, IMO. The index finger has 2 keys to manage, of which one needs its lateral extension. Though the pinky is weaker, the semicolon is in its resting position.

The actual answer though, is Bill Joy's keyboard. Another commenter has explained it.

Hopefully that principle will hold true with websites as well.

The main issue that I have had is that the web experience for many banking apps is really really bad. Many of them are non-responsive designs aimed only for desktops. Even worse, some features are available only on their mobile apps - like chat support. Honestly, I don't understand why banks do Google and Apple favors like this.