Besides all the other posts, this might just be a small improvement in rare cases:

The V8 javascript engine does some clever work when performing regular expression matching. Normal engines would compare one character at a time, but whenever the possibility occurs V8 matches several characters at once (eg. for /foobar/ it will try fo match "foob" instead of just first "f", then "o", then "o"), doing comparison on longer segments than just (usually) 8 bits at a time. This usually means that comparisons are grouped together as 32 bit values matching several characters at once.

I reckon the 64-bit edition would simply match up to 64 bits as well.

There are a lot of exceptions where the engine can't just simply match long segments (unicode, case-insensitive searches and so on) and there surely are operations that are a lot more cpu intensive than just comparing strings. I'm just excited about that simple optimization :)

.. but I didn't speak up because I wasn't Soylent Green. .. but I didn't speak up because I wasn't Charlie Brown. .. but I didn't speak up because I wasn't Technician Ted. .. but I didn't speak up because I wasn't Striker, Ted.

The end of level monster is pretty hard.

Well, if there isn't a law against this, there should be!

Caveat: These reports origin from foreign dubious sources and haven't been processed by the US News un-bias-o-matic.

I look forward to reading /. in fifteen years.

"Windows FOX is bloated. Why does it require 2 TB of ram just to boot when I can browse the intercloud without problems on Gnubun*x running with only 512 GB ram?"

It's people like you (and your fish) who created the economic crisis in the first place!