What's the WTF? The Prius uses gas.
I would be hard-pressed to ever find a WTF in the justaposition of billboards that are a mile apart.
What's the WTF? The Prius uses gas.
I would be hard-pressed to ever find a WTF in the justaposition of billboards that are a mile apart.
@joe.edwards@imaginuity.com said:
@snyd3282 said:
...The minimum was 3...I guess w3.org is out of luck.
I think he meant the entire domain name: "w3.org" => 6 characters. Which makes me wonder if there is a three character domain: "a.b"
@Weng said:
@esoterik said:I can't tell by the fragment what facilities they have, i.e. C or C++, etc.Being Apple, this is going to be Objective-C.
It's C. http://www.opensource.apple.com/source/Security/Security-55471/libsecurity_ssl/lib/sslKeyExchange.c
@joe.edwards said:
I tend to agree here. In a sense, all programming tasks are about managing complexity. The best model is the one that produces the least entropy, that is, one where every component is neatly organized and more can be added without disturbing what is already there. This also means minimizing side-effects and interactions between unrelated components.
(Emphasis mine.) I agree 100% and I've been saying exactly that for years. I believe that managing complexity is the fundamental activity of modern software engineering. Unless you are working on something like a AAA game title, or embedded code that runs on a pacemaker, the greatest obstacle to the program's success is managing the growing complexity that comes with any moderate-to-large software project.
@rbowes said:
Does anybody know what the logic behind this is?
There is no logic. Excel is the second worst piece of mainstream software of all time. Total, indefensible bullshit. After all these years, they still haven't fixed these basic fucking problems!!?!
You also didn't mention a good one: if you save in between cutting and pasting, you lose your clipboard. So if you are a compulsive saver (as buggy office software has trained so many to be) and you happen to control+S after you cut something, you have to cut it again. (Luckily Excel doesn't actually remove the cut cells until you paste. Even though it's non-standard behavior, it's better than deleting your cells, erasing your undo stack, and then saving the document.)
Edit: Haha... just realized this thread is 6 years old, AND I posted in it 6 years ago to bitch about Excel. Some things don't change.
@veggen said:
#1 Supportability - By far the most important. No exceptions.#2 and #3 depend on the context. If the app can potentially be under a heavy load, efficiency would be more important than compactness. Beautiful code won't make the app responsive. On the other hand, for apps that do not take much punishment, compactness gets #2.
Agree totally with #1, but I'm not even sure what #3 is supposed to mean.
First of all, compactness != elegance; elegance is about stating an idea clearly and without cruft. Sometimes the elegant solution is more compact than a ham-fisted solution, but code golf isn't elegant, either (in a production application).
Secondly, isn't elegance intertwined with supportability? If the intention and working of a program are clearly stated and easy to discern by other readers, then that enhances supportability.
I think a better question would be to rank maintainability, performance, and UX. Performance is still obviously the red herring, but prioritizing maintainability (for the developer's pleasure and productivity) and UX (for the user's pleasure and productivity) is probably a more thought-provoking question.
Edit: God the motherfucking text editor on this forum kills me.
@C-Octothorpe said:
That looks like minified JS. Someone actually did this by-hand and intentionally?!
To me, it has the aura of a long Excel formula. On the rare occasions that I find a spreadsheet with actual formulas in it, I usually find some horrendous, deeply nested formula written on one line just like this. Something as simple a switch statement becomes an abomination when expressed in Excel syntax, and if you mix in some string processing and error handling, its a migraine waiting to happen.
This should have made the front page. It's better than any of the front page stories in a while.
* Big commercial website
* Common problem (filtering user-generated content)
* Common tools misused (regex written by somebody who doesn't know that a dot is a character match operator = clownshoes)
* The juxtaposition of the two spam spam posts and then the mangled-but-legit post is amazing
My question is this: why block site names at all? You're never going to capture all of the various permutations, like 'visit mysite [dot] uk [slash] thehotness', but you could trivially block tags in user posts.
All I can think is that it was used as a really crazy 'goto' mechanism.
E.g. within each case, you could set i to some other value to repeat steps or skip steps.
That would be awesomely evil, in fact. I imagine there is something like that inside SSDS.
This guy on /. pretty much nailed it:
C++ is much too slow and carries too much of an overhead. And it usually requires an operating system on a general-purpose processor. You could go to hand-optimized binary code written directly for the processor but that still leaves us with inefficiencies.
Imagine if every website was implemented as an ASIC. Then we could talk about efficient datacenters. Maybe, if you're relly strapped for cash, you could implement each website in an FPGA. But that should only be a stopgap measure until you can afford a proper implementation.
@tgape said:
I think if someone had a compiler that actually converted the PHP code into the equivalent stand-alone code, you probably would get similar performance to the destination target language. But I wouldn't expect to see such a product any time soon.
This isn't just about "interpreted" versus "compiled". PHP, like a lot of modern development environments, takes care of a bunch of stuff for you at runtime, like memory allocation, garbage collection, boundary checking, type checkiing, linking, etc.
You could cut a lot of slack by optimizing out these costly operations in a compiled version.
I'm not suggesting that this is a sensible thing to do... just that I don't see a 10x improvement by compiling PHP code to native instructions. Especially if you're already caching your bytecode.
There are a lot of laws like that. They aren't enforceable per se, but they can be used to jack up the charges against anybody they arrest for something else.
So if you arrest a guy for something else (perhaps only on suspicion) and then find he has a concealed weapon, then you can charge him with that even if the original charge falls through or is too weak to hold him.
I'm not defending this particular law, but rules like this could have a purpose, generally speaking.