One quite convenient thing is that Windows Installer packages can be installed via Group Policy, making deployment for new nodes work like a charm. How is a sysadmin supposed do this with scripts?
Maybe an unpopular opinion, but I am missing the old Microsoft these days. How did we end up in the world where technologies like Windows Installer are replaced with PowerShell scripts that downloads software from the Internet?
As far I remember NAND/NOR memory (used for SSD) is very slow to *erase*. The erase operation can be performed only by big chunks, requires higher voltage etc.
SSD vendors circumvent this by adding several layers of write buffers to achieve good test results.
I think there is relatively cheap way to reduce such scams: make it mandatory for banks etc to perform “training” of the clients. Regularly make a call to clients asking for sensitive data. Then block account if client provides this data.
We're using ESE NT in our product and I'd like to say it's a great DB. Yes, it's have some limitation and quirks, but overall it's great DB. For us killing feature is efficient handling of binary BLOB columns.
AFAIK original was "cvs annotate" [1]. Subversion introduced "svn blame" and "svn praise" aliases for "svn annotate" as some kind of joke. It's funny that git only has "git blame".
You should just ask for refund. I've the similar story, Uber suggested credit. But immediately issued refund once I declined credit and asked to refund money back to my credit card.
My favorite quote:
[[[
Greg Sullivan, lead product manager for Microsoft's Windows client division, says that the computing community as a whole has benefited from the Web's standardization around Internet Explorer. Competing platforms would have meant that developers would have had to duplicate their efforts more often, he said.
"There is benefit to everybody who's involved," Sullivan said. "In general, a standard is very useful, whether it's de facto or du jour. It enables a level of consistency and a level of investment and minimizes some of the redundancy that can occur."
]]]
In fact .zip file contains file header information twice: before every compressed file (local file header) and at the end of the .zip file (central directory). It's possible to omit file size in local file header, but most most compressing utilities doesn't use this option. So most .zip files could be extracted without seeking to the end.
Sure, package maintainers may backport fixes to their old versions. But they need to fully understand all upstream source code and follow all commits. Otherwise they can miss important fixes: following only security fixes for supported branches is not enough. Sometimes project developers fixes bug/security problem in the code, but doesn't flag it as CVE because current code usage doesn't trigger it. But code in old branch could.
In general this approach should work fine, but devil is in detail:
1. You have to flush change to temporary file before move because otherwise you may get empty file: OS may reorder move and write operations
2. After move you have to flush parent directory of destination file on Posix. Windows have special flag for MoveFileEx() to ensure that operation is done or you have to call FlushFileBuffers() for destination file.
Linked paper mention the many popular programs forgets about (1).