Varriount

I found this paragraph particularly interesting:

> Trimming the working set of a process doesn’t actually save memory. It just moves the memory from the working set of the process to the standby list. Then, if the system is under memory pressure the pages in the standby list are eligible to be compressed, or discarded (if unmodified and backed by a file), or written to the page file. But “eligible” is doing a lot of heavy lifting in that sentence. The OS doesn’t immediately do anything with the page, generally speaking. And, if the system has gobs of free and available memory then it may never do anything with the page, making the trimming pointless. The memory isn’t “saved”, it’s just moved from one list to another. It’s the digital equivalent of paper shuffling.

I'd always been under the impression that as soon as memory was trimmed from the working set. Perhaps this was the case at some point, and was a reason for the PROCESS_MODE_BACKGROUND_BEGIN priority? As the blog mentions, the SetPriorityClass call has had this behavior since at least 2015, though I wouldn't be surprised if this behavior has existed for much longer.

As for why this "bug" hasn't been fixed, my guess is that it's due to a couple of factors:

- Windows has become fairly good over the years at keeping the core UI responsive even when the system is under heavy load.

- There are plenty of ways to reduce memory/CPU usage that don't involve a call to SetPriorityClass. I'd wager that setting a process's priority class is not the first thing that would come to mind.

- As a result of the previous two points, the actual number of programs using that call is quite small. I'd actually be interested in knowing what, if any, parts of Windows use it.

(As a side note, if there was a bug in a Windows API function, how would you even report it?

Would those benchmarks capture the performance improvements listed in the change log? From what I read, there were two big ones:

- Inlined list and set comprehensions.

- Reduced data copying in asyncio.

> It's the awful queries that do in memory sorting or make temporary tables for no reason or read-after-write, etc.

Are there any viable alternatives though? I often wonder what an SQL-like language built from the ground up would look like.

Why? What's the (supposed) fear?

Insufficient test coverage doesn't necessarily mean lack of self-discipline. It can also stem from project management issues (too much focus on features/too little time given for test writing).

This is what puzzles me - while time drift does occur, it tends to be in the form of minor errors which build up over time; large jumps are relatively rare. You'd think the mechanism described in the article would have a failsafe ensuring that only minor time recalibrations are performed.

How does an FPU get out of sync with a CPU? Wouldn't the CPU automatically wait for the FPU logic to complete (just like with every other instruction)?

That quiz was surprisingly accurate - the three cities it listed for me are less than an hour away from where I live.

Anyone know what kind of process was used to create the original animation? Was each frame hand-drawn, or some other technique used?

Any idea what/which websites are written using GWT?

What do mass-sent resumes look like?

Have you tried Indeed, Monster, etc.? Or failing that, contact the companies you're interested in directly?

I'm curious though - how many of those applications were for recently posted positions? I ask because I assume that the older a job posting, the more likely its position has been filled but the posting hasn't been taken down.

If you apply to 1000 positions, but 700 are from those "zombie" job postings, then you've really only applied to 300 positions.

I've had the best luck with recruiters that have contacted me directly on LinkedIn. Conversely, I've had zero luck with the recruiters that contact me via phone call.

My assumption is that this is because many of the latter are operating under the "if we get you hired we get XX% percent of your salary" model, and are thus inclined to submit as many applications as they can.

Out of curiosity, is your work publicly available? It sounds interesting.

I'm getting ready to do this with my group as well. So far I'm really enjoying Pathfinder 2e's mechanics. I feel that the three-action system is much more straightforward than 5e's action/bonus action system, and the "Sustain a Spell" action much better than concentration.

The big thing I don't like is the organization of the core rulebook. Considering how heavily conditions are used, would be nice if features and spells that apply conditions mentioned what those conditions did directly in their description, rather than requiring the reader to repeatedly flip to the conditions section. And there's also the unfortunate tendency for some important details to only be explained in the glossary or other unexpected sections[1].

[1] https://www.reddit.com/r/Pathfinder2e/comments/cx6p63/harmon...

There's comments elsewhere in this submission proposing using ChatGPT for designing programming languages, but what about for designing APIs?

Anyone know what medium was used to create these?

Just an FYI, while Nim has arrays (which are fixed-size) it's far more common to use sequences (dynamically-sized arrays).

Goodness, what kind of process/tools did you use to track that problem down?

Can you elucidate? What did you find appealing/unappealing?

Regarding the country you formerly lived in, what efforts would you say were most effective?

I think the poster might be referring to "Sensodyne Repair & Protect with NovaMin"

As a layman (albeit one with an interest in Biology), one thing that makes me skeptical of this article is the way it's written. Very specific assertions are often paired with very vague references to other papers. For example, an oft-repeated study was cited which involved exposing rats to EMF radiation. The rats then developed cognitive impairments similar to Alzheimer. However no mention is made regarding the strength of the electromagnetic exposure, nor it's range.

Overall, it seems like the paper attempts to tie a number of different studies together, without showing that those studies have been reproduced. I try not to dismiss scientific papers like this out-of-hand, but there have been hundreds of (quite dubious) claims over the years that electromagnetic radiation causes everything from cancer to autism. At this point, any claim that "electromagnetic radiation causes <Insert Condition Here>" is going to need to be backed up by strong, reproducible (and reproduced) evidence.

Does anyone know some good reading material regarding the evolution of microchip design and fabrication? I found the article quite interesting, however many of the more technical terms flew over my head.

The "updated microcode" package is installed on your system manually (like any other package). The "automatic" part comes in when your system boots up, after this package is installed. On boot, when the package is installed, your system will automatically use the installed package to update the processor's microcode.

While I do agree with the latter 2 points, (can't multi-jump, hard to memorize), the assertion

  It follows the order of the DOM elements and not the visual position of these elements on the page, which means that it uses the HTML structure (not user-friendly), but it should go after the layout position (spatial position);

Isn't quite true - all HTML elements support the "tabindex" attribute[0], which can be used to set the tab order of a page's HTML elements.

That being said, using "tabindex" (or having an out-of-order page structure) can cause accessibility problems for those using screen-readers and related programs.

From [0]:

  Warning: Avoid using tabindex values greater than 0. Doing so makes it difficult for people who rely on assistive technology to navigate and operate page content. Instead, write the document with the elements in a logical sequence.

[0] https://developer.mozilla.org/en-US/docs/Web/HTML/Global_att...

I think the point being made though is that CWD and other prion diseases are quite rare. Is there any danger from compost sourced from human bodies that died from non-prion-related diseases?

> and spread trivial things across many cores in large, complex codebases

How are tasks spread across cores? My main experience with the "await" paradigm is from Python, which is primarily single threaded.

Neat, though I'm curious - when do instructions like this typically get used?