954 karma · joined April 26, 2010
Whether it's Haskell or some other purely functional language, I'm of the opinion that every programmer should have one in their toolset.
That said, a side interest of mine is investigating applications of fountain codes to video streaming. There are a few papers out there and I'm slowly building up the knowledge (and courage) to implement something in that area..
Summary of results:
• Neither cameras in Jordan Downs nor Hollywood Boulevard had any significant effect in reducing violent or property crime rates within the target areas;
• The monthly rate of violent crimes fell in both the Jordan Downs and Hollywood target areas; however, the Nickerson Gardens control site and the Hollywood Box matched pair experienced similar reductions and the results were not statistically significant;
• The monthly rate of property crimes decreased in Hollywood, and increased in Jordan Downs, but the results were not statistically significant in either case;
• The evidence on the displacement of crime is mixed; in both locations, some crimes increased at a faster rate in the adjacent areas, indicating that CCTV may displace crime, while other types of crimes decreased relatively more in the buffer areas, though results were not statistically significant;
• CCTV had no statistically significant effect on arrest rates for misdemeanor quality-of-life infractions in Jordan Downs or on Hollywood Boulevard
All in all, I doubt the NSA (or any TLA) would hire them.
However, the example code uses `c' for connection and `q' for query. Surely, knowing what those are from the variable name would be a good thing?
It's not that I want to impose Obj-C's verbosity but the other extreme (1-letter names) is just as bad.
Aside: As a Haskell beginner, I find it astonishing that 1-letter names are the norm in Haskell-land. To me, names are not just placeholders imposed on you by the language, they should convey meaning, too!
I have a few reports that I keep open (last month's expenses, this month's expenses, etc), so my usage is generally 1) download transaction history in OFX from Natwest, 2) import into gnucash, 3) put the unrecognized transactions in the correct accounts (rarely if ever have to do that these days - the bayesian matching works rather well) 4) inspect the reports.
I couldn't be happier!
The order that visibly went through was redirected to the full Wallet site. I say "visibly" cause apparently one of the popup ones went through as well. Oh, well, I'm sure one of my friends would appreciate it.
I guess that's a good reason to implement credentials storage, don't you?
P.S. AccountManager stores your passwords and tokens unencrypted in a database as well.
Without device encryption, encryption of the passwords is useless, given root access, since the key is somewhere on the device as well. If anything, the only crime here is not using access tokens but storing the whole password.
With device encryption, the situation changes slightly. Unlike iDevices, most (all?) Android phones don't come with a hardware encryption chip, so, given a vulnerable bootloader, full-device encryption doesn't do much in the way of security. Under a secure bootloader, device encryption should be secure as well.