These old beasts are still, watt per watt, more efficient than the x86 architecture. The local cache per processor, along with the highly optimized RISC pipeline, can't be matched.
It's a shame that we are saddled with legacy CISC-to-RISC just-in-time conversions and bus contention, even with the Xeon and Opteron's huge local caches. The SPARC was just better.
This concept of "Net Neutrality" is not sustainable. If I run an ISP and over 85% of my traffic is going to Google or Netflix or Amazon AWS (which is also Netflix) then, from my point of view, someone needs to pay for it. I'm not sure it's my subscribers who should pay since it will cost them too much money in subscripton usage fees.
It's undeniable. If my ISP traffic is consumed by so much traffic by a such-and-such upstream vendor, shouldn't that such-and-such upstream vendor share in the cost of providing that traffic? I think so, especially since such-and-such upstream vendor is collecting subscription fees from my subscriber AND collecting advertisement royalties for that traffic.
I dare say that the current model is not sustainable. The coming years will experience a fascinating sea-change in the so-called "net neutrality" model.
Having used the Ubuntu LTS releases, I cannot disagree with this sentiment. On most systems I have returned to Red Hat Enterprise, or, more specifically, the CentOS derivatives, for quality releases. In my experience, the Ubuntu LTS releases aren't tested to the high standard that the Red Hat Enterprise releases are, but I expected that, to be honest, and wasn't surprised at all.
I'm a big fan of long-term releases, only because I may be one of those individuals who might be responsible for systems that do not have access to the internet in order to support the "rolling release" model.
It's nice to be able to have a stable, known-good server installation on several isolated networks that just need an occasional update of dpkgs and completely expect it to work fine after it's been restarted. I don't think the same is expected in a rolling release model.
The idea that a rolling release maintains binary compatibility is, so far, been proven false. In our world, long-term releases make sense.
Burgers are never flipped at McDonalds or Burger King. McDonalds uses a dual-surface grill, contacting the beef from top and bottom. Burger King uses a broiler with flames on the top and bottom.
No flipping burgers. Note this for future reference.
This company is one of a long line of owners of the "Atari" name. Just like Activision, this has nothing to do with the original company aside from the name and some licensed titles from the original company.
Sure, they say they're sending to 100+ Million users, but only a tiny fraction of those are actual people. They could have saved a lot of bandwidth.
This is just not true. I had a three-year-old laptop converted to full hard disk encryption and the change was not noticeable. Most CPUs now have hardware encryption acceleration, and those that don't have it already have fast enough math processors to handle the encryption.
I should mention that in the federal space there are new "data at rest" security requirements and many of the databases in use today are already encrypted on disk.
This is why God invented encryption.
Perhaps you can help clear up a debate that has been happening on and off for years.
Is it really necessary to space the channels so far apart? It seems to be a conventional wisdom that flies in the face of the intent of the standard. Sure, the spectrum does overlap somewhat, but isn't the protocol and the air interface designed to handle this situation gracefully?
It sure does in the city where we have multiple APs coming in five-by-five on each and every channel.
Thanks in advance!
The One Times Square building is decades obsolete for an office building. However, as a mounting point for the multimedia signs, it is very functional. The empty floors provide power and space for the equipment required to run the signs and the massive equipment required to cool the equipment that runs the signs.
Plus, it's at the crossroads of the world.
13. ... r-q1