Sure bud, you have one central non-gui worker, which the GUI thread communicates with and dispatches shit to other workers that need to process stuff. You store a bit of "extra" text (probably 50 pages would easily fit) in the GUI and make requests when it gets closer to the end.

Just because you can't think of a way to solve a particular problem you've just thought of, doesn't mean that high-quality performant programs can't be written in the language. You haven't worked with any other message-passing model, have you?

"No brain patterns involved at all"

I am not sure you know what a brain is?

Oh no, you've invented a contrived scenario in which you assert there will "surely" be a performance penalty, therefore the model is entirely unacceptable.

Maybe you should just, you know, leave the text in the non-GUI worker to start with? Or you can incrementally update the background thread as the data changes. I'm not even positive that postMessage() doesn't execute concurrently with the calling thread, as I'm sure the JIT could do.

Most browsers actually support web-workers: http://caniuse.com/#feat=webwo...

And there are a bunch of wrappers to make them feel more like regular threads. Easy-peasy.

Just play Unreal Tournament.

Most TLAs are a "caesar cypher" away from most other TLAs. (The obvious exception being ones with repeated letters, like BBC -> SSL)

Then it shouldn't be hard to find somebody who's noted them.

Yeah, I probably simplified too much there. Honestly, I almost posted anon; I didn't think it was a particularly good comment of mine.

Seriously, googling "python lmdb" shows up only documentation and lmdb blog updates on the first few pages, and also a link to this slashdot article. I don't see anybody interested in it or singing its praises.

It's okay that your pet project isn't wikipedia-noteworthy yet. Concentrate on your evangelism (like, get at least one person who isn't you to write about it), and then try submitting again once you have some sources to cite.

Because it's not about reducing kids born to unmarried mothers, it's about not forcing kids to be born to mothers that don't feel they can adequately provide for their children (or just plain don't want them).

It's about being born into poverty, not about whether the mom wears a ring.

Fair Tax isn't fair, and it isn't right.

If you want fair, you go with Basic Income. http://en.wikipedia.org/wiki/B...

You literally just give a certain amount of money to everyone, every year. You combine this with wealth taxes, such that whoever owns the most, pays the most. Thus, every single human being can afford to live with dignity, there's no "poverty trap" where your means-tested assistance cuts out, and the system will constantly rebalance money from those with much to those with little.

If the rich are truly rich due to their own hard work and innate talents, then they will have no problem maintaining a higher standard of living than those that are poor. While those who are simply born into money but have no real "merit" will gradually sink to a more appropriate level.

It's a bit hard to "only tax the first 200 gallons of gas" - how do you propose we do that? 200 gallons per credit card? Per license plate? Per social security number?

That's... certainly a thing you can say.

Less charitably, I might say "Your preexisting faith in the supernatural hinders your ability to comprehend the natural."

"Doubled" doesn't mean much, when it's one afternoon every three years.

But y'all didn't hold GameSpot's feet to the fire over Kane&Lynch. You whinged a little bit, and threatened to boycott GameSpot, but really nothing happened.

Apparently a journalist mentioning a game written by somebody he knows is much worse than, you know, a triple-A studio buying positive reviews. And the appropriate response is to attack the developer, and not the journalist.