zrm

51 ms·

481.
by zrm 7y ago
The operating system itself isn't the problem, it's all the applications. And the PowerPC transition was both easier and more worth it because the x86 processors were so much faster than the PowerPC processors of the time that the
482.
by zrm 7y ago
There are a lot of reasons to expect that to work better for servers than laptops. Most server workloads scale with core count, so winning in performance per watt is winning in general because you can scale performance by adding cores. A se
483.
by zrm 7y ago
The scaling is really the question. ARM processors generally have better performance per watt because they're designed to prioritize power efficiency over absolute performance. The Intel parts Apple's ARM processors compare to on
484.
by zrm 7y ago
The problem is they're using bad heuristics. Just because a service runs 24 hours a day doesn't mean it's using a significant amount of battery. The harder problem is, just because a service uses a significant amount of batte
485.
by zrm 7y ago
You use cron because it does one thing and that's the thing you want to do, so it's easier to use what exists than to reinvent the wheel. The flaw in systemd is that it doesn't do one thing, it tries to do everything. Instead
486.
by zrm 7y ago
> And then your cron job fails, but you don't know when, nor how. So you need to log it. Which it already does. Success on Unix/Linux is silent and any output from a cron job gets emailed by default. > And then your cron job
487.
by zrm 7y ago
We did try that and it supposedly claimed to the other party that I didn't have the app installed. Not that that would have been a scalable solution anyway, since then no pair of people could use it unless one of them gave it all their
488.
by zrm 7y ago
> I use WhatsApp without allowing them access to my contacts. That appears to be impossible for WhatsApp on Android. Someone wanted me to install it a bit ago, I refused to give it access to my contacts and it refused to do anything else
489.
by zrm 7y ago
The main enterprise thing you get from Xeon and not Core is ECC memory, but Ryzen does support ECC memory, and anybody can put it in a rackmount chassis. Whether or not it's common, it's available if you want it.
490.
by zrm 7y ago
The trouble is you can't actually scale that way. You might be able to make a 5GHz dual core that can match a 2.5GHz quad core, but nobody can make the 80GHz dual core that would be needed to match a 2.5GHz 64-core. Good luck even maki
491.
by zrm 7y ago
The people using laptops wouldn't leave them on longer than they would be otherwise, you'd just get the data from the one that happens to be on at the time, so they'd be "powered on regardless" for the same period o
492.
by zrm 7y ago
It's possible to use erasure coding to avoid needing that many more copies. With 75% erasure blocks you can lose any 75% of the nodes hosting the data without compromising availability, and that only requires the equivalent of four cop
493.
by zrm 7y ago
> Supporting the presence of multiple library combinations doesn't mean that you "support" all version combinations in the sense of supporting all combinations of their versions being used in the wild. It's not about
494.
by zrm 7y ago
> Well, no. Else software on macOS and Windows obviously wouldn't work, since those ship all their libraries along. Not exactly. For the system libraries (e.g. the Windows crypto API) you effectively get one version for the whole sy
495.
by zrm 7y ago
It's really trading one problem for a different one. The reason traditional distributions only package one version of a given library and make everything use that same version is so they only have to maintain one version of the library
496.
by zrm 7y ago
Spectre is basically a new variant in the longstanding category of timing attacks on hardware. There are things hardware vendors may be able to do to limit the impact, but it's just something software developers are going to have to le
497.
by zrm 7y ago
> I don't agree that phone numbers are good for onboarding: sending the first message to somebody on whatsapp requires asking for the phone number. Sending the first email requires asking for the email. Sending the first Skype messa
498.
by zrm 7y ago
Charities also have an ugly trade off when it comes to fundraising. You can often raise $2 by spending $1 on fundraising at the cost of lower efficiency -- you're spending half the money you raise on fundraising. But which gets more mo
499.
by zrm 7y ago
That doesn't really change the comparison. It would be better if we made more efficient use of the wireless spectrum, but if we did then people would just replace more copper and fiber with wireless. The wireless spectrum would still b
500.
by zrm 7y ago
Wireless spectrum isn't a great analogy for domain names. Spectrum is extremely scarce in practice, names aren't. There are hundreds of bits of entropy available so we're never going to run out of domain names even in an indi
501.
by zrm 7y ago
And the exception use case could be handled the same way that Flash was during its decline -- a box showing that there is some special content on the page, but it doesn't run until you explicitly click on it. Then it's there when
502.
by zrm 7y ago
See also: https://en.wikipedia.org/wiki/Wirth's_law
503.
by zrm 7y ago
We started with "does running your own recursive resolver break caching" to which the answer is yes, because it removes intermediary caches that can really improve query latency. It doesn't have to remove 100% of all caches t
504.
by zrm 7y ago
Sure, they had notoriously bad performance for a plurality of reasons. Which also explains the lack of specific complaints. People can tell you that it's slow, that doesn't mean they can tell you every reason why. Firefox historic
505.
by zrm 7y ago
You're naming some things that have notoriously bad performance. Being slow doesn't guarantee failure but it sure isn't a feature. And the problem isn't the protocol here, it's the choice of resolver. If the resolve
506.
by zrm 7y ago
That is effectively what causes the issue. The local resolver in the OS or on the LAN may have the name cached (because some other application or device requested it previously) and is thereby able to respond in <1ms, but if the applicat
507.
by zrm 7y ago
In that sense neither would putting a recursive resolver in your OS. DNS can have arbitrarily many levels of caching, because stub resolvers can be caches and can point to other stub resolvers. For example, you might have a DNS cache in you
508.
by zrm 7y ago
> The fact that no mainstream consumer OS runs a local recursive resolver should be a clear signal to you that people disagree with you about this; in particular, because doing so eliminates DNS caching, which is something most people
509.
by zrm 7y ago
> I don't think the hardware is that trivial. I used to think that, but I've learned a lot more respect for the people who understand how to troubleshoot it, how to purchase compatible components, and spot troublesome products
510.
by zrm 7y ago
> Certainly if you have someone already on the payroll who can take responsibility for the hardware part time, that makes it a lot cheaper. That's a different skill set though, so it's not true for every company. True, though a

More ›