I'm glad to hear there have been big changes. However, there is a more recent accident associated with a Korean operator: Asiana flight 214 crash at SFO in 2013.
The NTSB identified poor crew communication and crew resource management as important factors. Reuters and AFP reported negative repetitional impact to Korean air carriers.
It sounds like Stockholm to me ;) I don't think you _need_ the index to make partial commit work. I've used Mercurial first so I know "hg commit -i" exists.
Even if the staging concept is clear to someone, git cli terminology _is_ objectively very confusing and there are many articles written about it already (e.g., do I "add" to index? Is the index also referred as cached/Staged? Mixing different verbs and nouns everywhere). Are they all the same?)
I just wrote this to say it is not a necessary part of making a tool as powerful as git - Mercurial shows an example of a similar tool with a less confusing CLI.
Of course, git won so I just live with it. I enjoy teaching git new devs because once you explain the confusing terminology up front, they understand it faster.
Disabling swap on windows means all of your applications virtual memory has to fit in your physical memory. In Windows any unused virtual memory still needs space in RAM or, it has to have space in the page files.
Right now if I look at my Firefox processes, they take more (10-20%, sometimes a lot more) more commit size (virtual memory) than their private working set. With page files the unused virtual memory portion is simply reserved on the page file with minimal overhead. Without any page files, you will be just wasting memory.
RE: unnecessary writes, it might be windows proactively dumping the contents of the memory (I think this happens but I cannot confirm right now). But in general that's very low priority and it should affect your performance.
Firefox does not request private working sets beyond what is required. There are memory request mechanisms available to applications for MANY generations of windows that specify whether it is high-priority private working set (generally "uninterruptable") or opportunistic commit that is needed. The understanding is that commit can be removed by notification but private working cannot and instead you will be OOM killed if that happens. It is totally fine to have 80% of your system ram "used" but it should not be 80% private working set unless some processes are leaking or legitimately using it. There are also priority flags for memory use and the kernel memory manager will notify and kill in that order.
Check out RAMMap from the absolutely excellent system internals to see how your system memory is allocated currently, even per-process.
As an example, I have 64G of ram, showing ~40GB "used" as per task manager. Of that however only 22GB is private process active. The rest is memory-mapped files, standby, paged pool, nonpaged pool, shared etc.
The issue with pagefile - say there is also a 64GB pagefile - is that windows is notifying processes and the memory manager is considering that the system has "128GB" of ram, which many processes will take as a sign they can reserve more memory and causing an inflation of reserved actual ram.
It is less of an issue now that the memory manager is tier aware and applications have ABIs to check and request memory in a more informed way.
Writes on an SSD are always an issue unless you're running SLC or similar high endurance flash.
This is the correct answer that needs to be at the top. No swap doesn't mean OOM killer magically kicks in earlier. It just means the anonymous memory has no where to go and your executable pages get evicted and then you are really hosed.
Unfortunately no crash. This is the dog slow case. Too slow for an SSH session to be able to start. But the machine might catch itself and get back onto tracks without an OOM happening.
I have owned WF-1000XM3, 4, and (currently) 5. I got the 5 with discount as replacement for the 4 since the battery of one earbud was dead due to a firmware bug.
The noise cancelling gets slightly better each iteration. There's another thing the 3 and 4 are better at than the 5: easier to get out of the charging case.
Also, while you could replace the batteries in each of these versions, the IP rating would be in practice regressed.
I keep looking and asking this all over the place, haven't found one yet. I don't see why not, it's basically a 3d printer with two axes instead of 3 and toner ribbon cartridges are ubiquitous, much much cheaper than filament. I don't understand why nobody has done this, I might go ahead and do it one day down the road if it doesn't happen before I get around to it.
I don't have solid data but for "core" mature software written in c/c++ like browsers and Linux, I feel like I see far more high profile security bugs from the lack of memory safety rather than something like "Linux failed to enforce the existing permissions".
