Greg Smith's book "High-Performance SQL" is a good start.
80x24 even on a C64 was painful; the best one I saw was VIPTerm from SoftLaw, but there's only so much you can do with a 4x8 pixel grid.
As I recall, the move that secured the C64's place in market history was the price drop. It originally sold for $595, but in 1984 a combination price drop (to $299) and a $100 trade-in rebate for your videogame console meant you could buy it for $200 at Toys-R-Us. That was the magic number.
You really wanted to LOAD "0:*",8,1, though, because if you left off the "0:" you'd trigger a bug in the 1541 ROMs that would eventually cause you to corrupt a program if you used save-and-replace. (The 0: indicated drive 0 of a dual drive; IIRC those were only produced for earlier PET/CBM computers with an IEEE-488 bus, and not for Commodores - though we did eventually see Lt. Kernal hard drives with partitions 0-9.)
On a similar note.. growing up I had a scooter that would do 22mph with one rider, and 5mph with two.
I figure if I'd been able to fit seven people on it, I could go 80mph backwards.
No, you misunderstood the reasoning. The United States takes up more space than England.
Remember, the people funding this research have a vested interest and a strong desire to have the numbers come out the way they want them to and, no surprise, they generally do.
Yep. I worked on a cybercrime startup idea for a while, and every single "cost of cybercrime" calculation I found - even from government agencies - was based on the same estimate from MarkMonitor. After a few years, MM was able to cite the more "official" sources with a circular reference.
If nothing else, because the sounds you (the musician) hear on overdubs will affect the sounds you sing and play. Late binding and lazy evaluation is not always a feature in music production.
GIF patent was on the compression used by GIF, not GIF itself. The patent was held by UNISYS, not AOL/CompuServe.
Oh, we were... I remember trying (and failing) to convince Cisco that they should make some type of load balancer. They didn't see the need.
Others have commented on the security benefits of prepared statements, but one problem with them, at least on Postgres: Since you're planning the query before executing it, the planner doesn't have as much information as it will at execution time, and it might not pick the optimal plan - especially if the database changes significantly between PREPARE and EXECUTE.
OTOH, I suppose you could take every statement and turn it into a group of PREPARE/EXECUTE/DEALLOCATE. Not sure if there are performance implications with that, though.
As George Carlin pointed out, you probably could beat a guy to death with the Sunday New York Times.
What's a New York Times?
I was just thinking "Hasn't Karl Auerback been trying to get the world to realize this for a decade?" Thanks.
latency will finally be a worry of the past
To be replaced by fear of decapitation, no doubt.
They work with the SAS - that's Super Army Soldiers!