It's basically just an inversion; instead of the cache being a read-through layer over the database, the database becomes a write-through layer over the cache.
625 karma · joined December 14, 2009
http://mattdw.github.com/ http://problemattic.net/
It's basically just an inversion; instead of the cache being a read-through layer over the database, the database becomes a write-through layer over the cache.
Any client program can wrap as appropriate (which is not always to 80 chars, but 80 chars would work as well as anything) with QP; the same is not true of hard-wrapped as gmail does it.
It doesn't quite have all the libs you might want for general development yet, but for the things it's currently equipped for it's a lot of fun, and surprisingly easy. (Up until I find myself in a quagmire of lifetime problems of my own making. Looking forward to the coming lifetimes inference enhancement.) It's a surprisingly reasonable functional programming environment too.
The attacker got access via a reboot, so something as simple as passphrase-protected private keys would probably be sufficient here - "manual actions" could well refer to "enter the passphrase after startup". Or using something like kerberos, where credentials have to be fetched/validated via a separate server.
(Edit: Also being limited to alphanumeric for hashes and printable ascii for input gives you pretty good compression potential.)
> I still don't know a thing about what F or Coyoneda mean. But it isn't really slowing me down.
They're essentially cargo-culting signatures, and while sometimes that can be enough to stimulate proper understanding, I worry that the first time something goes wrong the author will be hard-pressed to solve it. It seems like a useful way to stumble around in unexplored areas; it doesn't seem like a good way to build software you're going to have to maintain and support.
That's not generally my observation of the world. No-skill-required jobs pay less, skill-required jobs pay more. There's a slight bonus for dangerous jobs, but not a heap, relatively speaking. Pleasure derived or not only appears to have an effect on income levels outside of traditional employment and into freelancing territory, for example with starving artists and writers.
That's untrue. Switzerland is having a national referendum on whether to offer one, and stipends from oil or casino money, while not enough to live on at this point, already exist in a few places. You may be correct that there's not enough money to give everyone enough to live on, but it's far from sci-fi.
(There is plenty of money in the world, it's just tied up in things like insane finance industry salaries, or $500k/yr/person for imprisonment, etc.)
And historically? People looked after their own menial tasks, where they were small enough, and where the tasks were too big for individuals (like roads, or building a town hall) the community got together and did it.
Interesting times ahead. It's going to be painful getting there, if we get there at all, but the idea of a Universal Basic Income seems to be getting more popular. (It wasn't so long ago it was pretty much pure sci-fi.) Particularly I guess as it begins to look like modern capitalism may not actually be good at providing jobs for everyone who needs one.
Potentially UBIs could be very good for the world, freeing people to work on things they personally desire and value, and in some ways redistributing the 'means of production' back to the little guy.
window["alert"]("hello")First, we set var '$' to bitwise NOT of [], which is -1 ([] casts to 0 or false depending on the operator):
$ = ~[];
Then we re-set $ to an object: $ = {___: ++$,
$$$$: (![]+"")[$],
...
Which gives us: $.___ == 0 // ($ was still -1, now it's 0)
$.$$$$ == "f" // I think
The "f" is a bit clever: ![] == false
(![]+"") == "false"
(![]+"")[$] is an index on the string, and $ is now 0
That's as far as I've bothered. (edited for formatting) preferred-width: 300px, 1.0; 200px..299px, 0.7; 100px..199px, 0.5;
That's slightly less flexible than a utility curve function, but (especially if ordered) is far easier to optimize for, as choices are ordered and restricted.And it's worth considering that every tweet, every photo on Flickr, every video on YouTube, every status update on FB, and so on, constitutes a new copyrightable work. Not everyone will care about the copyrights of their tweets, but some will. How do you copyright something for which you have no control of the identifiers? I assume you don't intend for people to hit up the service for a new UUID before tweeting and embed the token in their tweet?
(Obviously this problem would go away if e.g. Twitter itself signed onto this scheme, automatically registering and UUIDing your tweets on your behalf.)
Assume all the usual tensions between designers and developers :).
(Grunt, incidentally, strikes me as a system that has learned nothing at all from decades of other build tools. It's about one step better than piping globs to unix commands.)
Which is fine for you. But I tried it for a project then ditched it, because it didn't justify the extra tooling required in my development pipeline, and because there are ambiguities and inconsistencies in the syntax and the language, and yes, occasionally it's actually worse than Javascript.
Which is only to say that not everyone fits into a "doesn't know CoffeeScript"/"loves CoffeeScript" dichotomy.
So it would have been entirely possible to go to war in its wake without expecting to participate in its like. After all, officially (from the outside), it was condemned.