As a daily hg-git user, could you elaborate on (2)?
1,833 karma · joined June 30, 2012
And it's still creeping upward. The average voltage at my house over the last year was 121.9 volts. https://i.imgur.com/6RMZnXd.png
Not exactly English, but it's in the dictionary. I don't know if I should be impressed that the first result actually sounded pretty reasonable or disappointed at how bad some of these pronunciations are.
Of course, the whole thing is gonna be "results may vary", I suppose... https://youglish.com/getcid/25032799/electrophoresis
[1] https://www.washingtonpost.com/opinions/trump-made-the-right...
[1] https://www.nytimes.com/2018/11/04/us/politics/apps-public-v...
And the clearly malicious action of modifying Firefox to disable signature verification can and should be flagged by anti-malware software, which runs at a higher privilege level.
[1] Putting aside for the moment the fact that most users now have no extensions installed due to the certificate expiration issue. No Firefox user, myself included, is happy about that.
How? These extensions were not being installed through the normal mechanism. The malicious extension installer will just set the flag that says "this extension has been verified".
> And honestly, I think it is security theater to attempt to defend against attackers on the same or higher privilege level.
I understand that, and Mozilla does too: "By baking the signing requirement into the executable these programs will either have to submit to our review process or take the blatant malware step of replacing or altering Firefox." [1]
[1] https://blog.mozilla.org/addons/2015/04/15/the-case-for-exte...
That would defeat the purpose of verification: "Add-on signing in Firefox helps protect against browser hijackers and other malware by making it harder for them to be installed." [1]
And it's not just malware that was doing that. Microsoft force-installed the ".NET Framework Assistant" into Firefox on Windows, and you had to edit the registry to remove it. [2] If I recall correctly, AVG and Logitech were also among the list of offenders.
[1] https://support.mozilla.org/en-US/kb/add-on-signing-in-firef... [2] https://support.microsoft.com/en-us/help/963707/how-to-remov...
If Uncle Sam can save a lump-sum for you by deducting from your paycheck, you could have done the same (in fact, better) with a bit of resolve and a bank account.
The problem is that Google wants to break API compatibility without actually calling it what it is. Your app, which worked for years, is now broken and as far as the user is concerned it's your fault. I've been tempted to set the "max API level" property on my apps so that I don't have to deal with this anymore. (Oh, wait, Google changed Android to no longer enforce that property.)
If Google wants to make breaking changes to the API then give developers a reasonable deprecation timeline and don't let users install apps that target old API levels.
[1] https://github.com/dotnet/corefx/issues/33284#issuecomment-4...
I wish I could summarize the error model here, but I really couldn't do it justice. Read the blog post -- it's very good.
With Dropbox dropping support for ZFS on Linux, I had no reason not to switch. It's cheaper than Dropbox and you get Office.
So to "remove Quaternions from every 3D Engine" all we need to do is rename the "Quaternion" datatypes to "Rotor" and we're done?
.NET Framework only has the portable implementation though. The fast implementation requires support in the runtime, and Framework may never support fast Span<T> [2].
[1] https://www.nuget.org/packages/System.Memory/4.4.0-preview1-... [2] https://github.com/dotnet/coreclr/issues/18280#issuecomment-...