I know that, e.g., Budweiser and Miller tend to ship cans of water for this purpose.
But those are branded "Bud Lite" and "Miller Lite" respectively.
I know that, e.g., Budweiser and Miller tend to ship cans of water for this purpose.
But those are branded "Bud Lite" and "Miller Lite" respectively.
Soooo.... the "ED ppiills" will give you such a vibrant, long lasting and powerful erection, that you'll be able to type out whole emails with your penis?
My favorite ice cream is _9dae361af79b04c9c8e7057f60cc6)
My favorite ice cream is {40d30102-6a36-4bca-83d9-5e3855641ecb}bold text
Basically Markdown is just terrible awful shit. So it was the obvious choice for Discourse.
: Let's take something that's just terrible and mix other parsers into it so that it's even worse and they're all terrible too!
When I try to call my own number, I always seem to get an engaged tone. I must be busy...
Every time I call malloc()
I get a different result. Suuuuuuuck...
My personal favourite is Password does not meet length and complexity requirements. Try again.
Thanks for not letting me know why the password I just entered didn't meet the requirements. :<qqq>/
This is just me thinking out loud here, but it looks like "letter people" do have avatar png files, but maybe not on the same path as "avatar people":
Even more interestingly, it looks like you can just 'make up' random user names and it will serve you a letter...
Excuse me one second...
So they're not defined to be undefined
, implying that they're undefined, but not undefined
, whereas in the other case, they were defined to be undefined
. So you need to be sure whether your undefined
is a defined undefined
or an undefined undefined
. Makes sense?
My books are literally paying the rent now.
Now there's nothing standing between you and the spoon.
which one does not belong?
The chicken is the shortest, so it is the least belong.
The only trouble we ever have with TFS is that our dumb, ancient, proprietary language no one else uses ends statements with a specific non-printing character, and if TFS sees that in the first n characters of a file, it marks it as binary, which makes the builtin compare not work right. And we deserve that.
You should start a thread about that. It sounds awful fascinating...
My SSN is 12345. It's easy to remember because it's the same as the combination on my luggage...
THERE'S A COMMENTER ON A BLOG I READ WHO TYPES LIKE THIS FOR SOME REASON.Filed under: we should onebox the hell out of bash.org
Come to LOCAL COMPUTER STORE
, where drunks will attack your computer with wirecutters!
The fact that we live in a world where computers are fast enough to run Ruby programs convinces me that the singularity is near.
I remember that a thing happened to me once, also. It was probably when I was younger than I am now, and it happened in the place where I was at the time when it happened.
>When I git pull, it takes forever, esp. given our Digital Fortress connection issues.
Three guesses what I read the bolded text as at least twice...
The funnest part is that if you unexpand them, it goes away again...
It has 5 attempts at resizing the image down to the allowed size too.
Am I reading that code correctly? They literally attempt the exact same resize on the exact same image five times because if it discofails the first four times it might discosucceed on the fifth. What is this? Faith-driven development?
Also magic numbers == urgh, but whatevs, this is Discourse.
>Warning: you don't know how to use, don't even try to use it.
Are you tough enough to use this function? Do you have the what it takes? Do you? You wouldn't dare!
The funny thing about XSS exploits on Discourse is...
...that literally every single codepath that can have an XSS does have an XSS, because the devs exist in state of perpetual surprise and also never use one function when 10 will do and wilfully reinvent wheels inside wheels and...
The spelling of aluminum is consistent with other metals like lithum, sodum and magnesum, at least.
Spider farms probably produce spiders, which are creepier than chickens.
bumps... humps...
I believe either term is acceptable.
Both derive from the name of the inventor, Sir Reginald Humpington Bumpington.
i=i+1
That's probably still a little bit obfuscated, don't you think? Better to abstract it away with a function so the intent is clear:
const int DEFAULT_INCREMENT = 1;
void increment_integer_value(int &i) {
i = i + DEFAULT_INCREMENT;
}
Now it's nice and straightforward, and this way, if we decide that we want to start incrementing by, say 2 instead of 1, we only need to change the code in one place.
A nearly $50,000 federal study is examining the sext messages of college girls to determine whether sending racy pictures makes them more likely to engage in risky sexual behavior.
I cannot imagine why middle-aged men might be so interested in this.
The real solution is to hard-code the enum values and never ever fucking change them. If Ruby can't do that, one more reason to use a less stupid language.
If only it were possible to generate an integer value from a string, some kind of function perhaps? Could end up making a hash of it if you weren't careful though, admittedly...
Where's the fun in just writing what you want if you can't tell the system exactly what pointers to follow and what memory to free and allocate?
Let me guess, we're speaking of Real Programmers...
[...]
Mel's job was to re-write
the blackjack program for the RPC-4000.
(Port? What does that mean?)
The new computer had a one-plus-one
addressing scheme,
in which each machine instruction,
in addition to the operation code
and the address of the needed operand,
had a second address that indicated where, on the revolving drum,
the next instruction was located.
In modern parlance,
every single instruction was followed by a GO TO!
Put that in Pascal's pipe and smoke it.
Mel loved the RPC-4000
because he could optimize his code:
that is, locate instructions on the drum
so that just as one finished its job,
the next would be just arriving at the "read head"
and available for immediate execution.
There was a program to do that job,
an "optimizing assembler",
but Mel refused to use it.
"You never know where it's going to put things",
he explained, "so you'd have to use separate constants".
It was a long time before I understood that remark.
[...]
I compared Mel's hand-optimized programs
with the same code massaged by the optimizing assembler program,
and Mel's always ran faster.
That was because the "top-down" method of program design
hadn't been invented yet,
and Mel wouldn't have used it anyway.
He wrote the innermost parts of his program loops first,
so they would get first choice
of the optimum address locations on the drum.
The optimizing assembler wasn't smart enough to do it that way.
[...]
I have often felt that programming is an art form,
whose real value can only be appreciated
by another versed in the same arcane art;
there are lovely gems and brilliant coups
hidden from human view and admiration, sometimes forever,
by the very nature of the process.
You can learn a lot about an individual
just by reading through his code,
even in hexadecimal.
Mel was, I think, an unsung genius.
[..]
—excepted from The Story of Mel, a Real Programmer
[b]Proposal:[/b] anyone who wants to stand for political office should be banned from standing for political office.
Discuss..
Most of that time was spent Discosearching for the correct topic.
The characters I can read on both cans are as follows (translation mine, but Google translate basically agrees with me, so make of that what you will):
#非常災害用
Extraordinary Disaster
#飲料水
Drinking Water
The plot thickens...
http://yotube.com. See if you can spot my obvious mistake.
I would actually advise not visiting this site, as it immediately starts playing audio at you (strike #1).
Well, at least I'm a "Valued Visitor", and not just some random shmuck who typo'd one of the most popular sites on the internet. I wonder if I can win Apple Product (100% anonymous)? (strike #2)
(Wait, if it's "100% anonymous", how will they know where to deliver my Apple Product...?)
I have decided that this shit is not worth my time, and a Ctrl+W GTFO may be in order, but wait! There's more:
Strike #3, and I think we're done here.
As a bonus featurette, this misadventure originally happened on my laptop, so I decided to recreate it on my tablet to capture some images. Although it turns out that McAfee is still somehow infesting my Chrome, it at least seems to have the right idea about this:
Whoa! indeed. Now excuse me while I go get my video fix from a genuine internet site...
Note to self: wait for at least 54 seconds before calling anyone on their ambiguous syntax...
Because Windows never crashes.
Unless it's running third-party software, or running on hardware?
why do you need to kill a process and its children?
Because it's a very naughty process?