What about Skype?
HamsterRage
joined 2 years ago
I'm currently working on a tube of Black Forest flavour.
That's the point of the post. It's so bad you can't even believe it.
93= Four score and a baker's dozen.
Came here to say this!
It's a close call, but I think the IOC just edges out FIFA in overall corruptness.
I got confused about which side not to believe when one of the most corrupt governments on the planet starts mucking with one of the most corrupt organizations on the planet.
In truth, the 70% was just one, low end product which could have been due to any number of factors. The other price hikes quoted were much more in line with the tarrifs.
I once spent 10 hours travelling from Toronto to Iowa (and back to Toronto) to flip a switch on a printer that multiple people had failed to figure out how to flip.
I spent 30 years working with derivatives of the Pick Operating System and its integrated DBMS. Notably Universe and Ultimate. Back in the day, it was very, very difficult to even explain how they worked to others because the idea of key/value wasn't commonly understood, at least as it is today.
I was surprised at how similar MongoDB is to Pick in many many respects. Basically, key/value with variant record structures. MongoDB uses something very close to JSON, while Pick uses variable length delimited records. In either case, access to a particular record in near instantaneous give the record key, regardless of how large the file is. Back in the 1980's and earlier, this was a huge advantage over most of the RDBMS systems available, as storage was much slower than today. We could implement a system that would otherwise take a huge IBM mainframe, on hardware that cost 1/10 the price.
From a programming perspective, everything revolves around acquiring and managing keys. Even index files, if you had them (and in the early days we didn't so we maintained our own cross-reference files) were just files keyed on some value from inside records from the main data file. Each record in an index file was just a list of record keys to the main data file.
Yes, you can (and we did) nest data that would be multiple tables in an SQL database into a single record. This was something called "Associated Multivalues". Alternatively, you could store a list of keys to a second file in a single field in the first file. We did both.
One thing that became very time/disk/cpu expensive was traversing an entire file. 99% of the time we were able to architect our systems so that this never happened in day to day processing.
A lot of stuff we did would horrify programmers used to SQL, but it was just a very different paradigm. Back in a time when storage and computing power were limited and expensive, the systems we built stored otherwise unthinkable amounts of data and accessed it with lightening speed on cheap hardware.
To this day, the SQL concepts of joins and normalization just seems like a huge waste of space and power to me.
I fixed it by installing Shazam. Since then I haven't paid any attention to it.
Groove Salad plays constantly on all the Nest devices through my from morning to night.