381–390 of 441 posts
Earlier quoted context omitted.
By DeMorgan's laws, typing this in a Google Doc causes OneNote to crash.
By DeMorgan's Law and Bill and Ted's Excellent Low Precedence Right Associative Postfix Sarcastic Not, "Or. Or. Or. Or. Or. Not!" crashes.
Earlier quoted context omitted.
Widely known because the token names were surfaced to users in error messages, so some common syntax mistakes would produce deeply unhelpful "Unexpected T_PAAMAYIM_NEKUDOTAYIM" errors. Hopefully they eventually did something about it, but it was like that for years and was one of the many things that put me off PHP for life.
> Widely known because the token names were surfaced to users in error messages, so some common syntax mistakes would produce deeply unhelpful "Unexpected T_PAAMAYIM_NEKUDOTAYIM" errors. Hopefully they eventually did something about it, but it was like that for years and was one of the many things that put me off PHP for life. One can like or dislike PHP for a variety of reasons, but surely being put off it for life…
Earlier quoted context omitted.
Ironic, from the authors of RE2. They know the correct way to implement regexes. Though, when I worked on Google's indexing system, some researchers were having machine learning generate regexes to run on every page in the visible web... and mis-implemented the feature to re-compile the regex to DFA (which re2 effectively lazily converts to NFA via memoization) for every single page load. The speed of the indexing sy…
> "DO" for "{" and "OD" for "}" so that they could write C++ a bit more like Bash. Bash (like Bourne shell before it) uses do/done. I think DO/OD was in an Algol (68?). I'm not sure where else? Bash does do the reversing for if/fi and case/esac, though.
The original bournegol macros for DO and OD were a bit different:
#define DO ){
#define OD ;}
Earlier quoted context omitted.
Widely known because the token names were surfaced to users in error messages, so some common syntax mistakes would produce deeply unhelpful "Unexpected T_PAAMAYIM_NEKUDOTAYIM" errors. Hopefully they eventually did something about it, but it was like that for years and was one of the many things that put me off PHP for life.
> Widely known because the token names were surfaced to users in error messages, so some common syntax mistakes would produce deeply unhelpful "Unexpected T_PAAMAYIM_NEKUDOTAYIM" errors. Hopefully they eventually did something about it, but it was like that for years and was one of the many things that put me off PHP for life. One can like or dislike PHP for a variety of reasons, but surely being put off it for life…
People are often defensive about PHP, but at the end of the day we choose our tools. I wrote a significant amount of PHP for a brief period and out of maybe 20 or so languages I've used professionally I found it by a wide margin the least pleasant to work with. Supposedly it has improved a lot, and I'm glad if so. But I have no desire to use it again, and am unlikely to ever have a reason to.
Earlier quoted context omitted.
But why it even happened? Typically you run Flume over docjoins in your project’s quota. If you screw up, all that should happen is that your Flume job is out of quota.
This was in the Borg days, pre-Flume. As I remember, we had at least one Borg cluster to ourselves for indexing. Our quota was a cluster. We cared because indexing latency is important. Engineers get paged and woken up in the middle of the night when indexing latency gets high. Doubling CPU usage meant doubling indexing latency. The pre-Percolator indexing system ran roughly 1,000 threads per box on roughly 1,000 War…
It sounds like it would be even cooler to coordinate with the local electricity suppliers to spin up and shed extra load a few minutes in advance, but I'm not sure if this would actually have a practical benefit.
Earlier quoted context omitted.
Quoted post unavailable.
Not many people know this, but similar to image alt text, the tag was originally introduced for accessibility reasons, so that people with autism and similar conditions can experience the web in the same way as more neuro-typical folks do. The tags should be invisible in the average browser, unless you've got sarcasm highlighting turned on. Unfortunately, the feature hasn't really caught on, and it remains unsupporte…
Earlier quoted context omitted.
Re2 is also slower, so they might not be using it for high volume stuff. Also I’ve heard that Google automatically fails people who use regex in interviews, so their average engineers probably aren’t the best at it.
> Also I’ve heard that Google automatically fails people who use regex in interviews, Hmm... I don't remember that, and I conducted over 100 interviews back when I was at Google. A blanket failure for using a regex sounds like it's missing some nuance. But, maybe that was before or after my time. I wouldn't be surprised if they start out with some interview questions that are easy to implement as regexes, but then gr…
In general regexes finish instantly for normal sized inputs, but the actual O(n) might be quadratic or whatever.
Discovered by Eliza Callahan triggered by a poem in the middle of her novel. (Friend of a coworker) That poem can be found here: https://durationandthebodyelizacallahan.cargo.site/ - if viewing on mobile you have to Request Desktop Site for some reason, at least on Android it initially shows up as a Lorem Ipsum page
Earlier quoted context omitted.
That's probably a cyber crime in most US states. Edit: You guys have no sense of humor.
try /s at the end of "offending" sentence, most people will look at it more kindly.