WinDev VS biden-approval-ratings

Trying to research this a little more, I came across a post that certainly seems to mimic the issue.

> compressed memory

doesn't solve much and it's been available in all other OS for a long time.

many reported that compressed memory can negatively impact performances in certain scenarios

For example

https://github.com/microsoft/Windows-Dev-Performance/issues/...

You can see pretty easily if you ever try to delete a node_modules folder on Windows: https://github.com/microsoft/Windows-Dev-Performance/issues/17 There's some anectdotal evidence in there that FS performance is better in Linux even when Linux is emulated in WSL2 instead of native Windows.

issue on github

Addressed an issue where when explorer.exe is launched from an elevated process was using a lower memory priority, impacting the performance of all processes launched after it (Issue #55).

A bug has been filed about this on the WinDev repo, might help resolve it faster if it gets some upvotes: https://github.com/microsoft/Windows-Dev-Performance/issues/...

There are performance issues with POSIX-first software on Windows. There is an open issue for the Windows team about it on Github. You can read more about it here. That's why WSL is needed.

I now own https://www.bidenapproval.com, which just redirects to my blog now. On that blog I have posted that I've developed a basic Biden approval polling average in Python (very rudimentary and shitty because I have very little formal programming experience pls no bulli), anyway, Biden's average approval right now is 55.0%, something that I imagine will go up as more polls come in and the average has to rely less on Rasmussen, which is a quarter of the sample right now and an increasingly important part of it as they keep putting out more recent polls while there hasn't been one from anybody else in a few days (to be clear, older Rasmussen polls are thrown out of the average when a new one comes in, but it still allows them to stay ahead of the recency weighting).