3 ms·
Just tried it, same 2 seconds. Perhaps it was changed sometime afterwards?
by ThrowawayR2 4y ago
Just tried it, same 2 seconds. Perhaps it was changed sometime afterwards?
- bediger4000 4y agoWith Windows, who can tell? And that's the real issue. Is it a bug? Is it Micrsoft telemetry? Is it Microsoft being underhanded (which happens!)? I've noticed that Windows programmers are very quick to work around what they perceive as bugs in underlying library code, and opaqueness in both code and motives is why.
- georgia_peach 4y agoFor that particular case, the source is available: https://github.com/microsoft/calculator/issues/148 https://github.com/microsoft/calculator/issues/148 Aside from that, amen. "Get a byte, get a byte, get a byte byte byte" is a breath of fresh air compared to MS documentation. The situation has improved--if only because we can go to StackOverflow and ask Jon Skeet for the answer--but in the bad old days (where you might as well be on a desert island with your MSDN DVDs) it was pure pain.