961 karma · joined March 12, 2009
http://en.wikipedia.org/wiki/Pascal_(programming_language)#P...
Just kidding. The heart of rock and roll (and r&b and techno and hip hop, etc) is in ... yadda yadda ... DETROIT!
What's particularly galling (to a matlab hater like me, anyway) is how some of the most highly-cited and useful work that's made available by researchers is done so only through matlab. The de facto standard benchmark for keypoints (http://www.robots.ox.ac.uk/~vgg/research/affine/) is a matlab function, but it's not like that code uses matlab in any interesting way, it just reads text files. And even though it's not computationally intesive (the benchmark is only on small set of images) there is a mex function involved to do the actual computation, which makes it a pain in the ass to use with octave. Basically they're using matlab as a $2000 bash shell. Same situation for the standard segmentation benchmark (http://www.eecs.berkeley.edu/Research/Projects/CS/vision/bsd...) And then there's LabelMe (http://labelme.csail.mit.edu/) the "open" annotation tool. They've got a really slick javascript UI for crowdsourcing ground truth collection for image segmentation / object classification tasks. They make the data freely available (which is awesome) but to access it you have to go through a matlab toolbox...? WTF?! I mean really, you've obviously got someone on your team who knows a thing or two about the web: take a page out of Flickr's playbook (after all they've done for the CV community) and make your data available via open standards. There's not even a goddamned download link on the page. It's like they're on the Mathworks payroll.
Grrr...
Tech journalism bingo in one sentence!
A const reference in C++ is like an interface that doesn't have any mutating methods, except that all the methods of the interface have the same names and signatures as the original, and I don't have to actually type out a separate interface definition, I just choose which methods I want to appear in both the immutable and mutable interfaces by appending a "const" to their signatures (bonus: if the implementation for the const version is different, I can overload it.)
Sure, C++'s const has tons of problems, but it seems like the Java and C# designers looked at it and said "const is probably more trouble than it's worth so let's not bother." Which is a fair assessment, I guess.
get's to bottom of article, reads that author represented NM in the house...back up to the byline...
Fucking Heather Wilson. Should have known...
Take that sentiment and mix it with some freedom: Instead of making them play the violin/piano and study pre-med, let them choose their goals. "Want to be an actor? Great! But you're going to be the best actor in that play and I won't tolerate anything less." "Guitar? Sure! ... You're not coming out of your room until you nail Stairway."
Not all Chinese folks are as psycho as this gal. A Chinese guy I worked with told me that he put it to his son this way: "You can do what ever you want, I just want you to excel at whatever you do."
(on the balance, though, this essay is garbage.)
But you're right that this parenting style has benefits. It strikes a chord with me, as a parent of small children, when she says that you're not doing them any favors by letting them give up. But parents have to find the right balance. Maybe the author's children benefited from having both kinds of parents, one strict and Chinese, one doting and Western---Cue shock and horror from Chinese grandparents. I know many successful children of mixed East/West families. Sure, that's anecdotal evidence, but so is this article.
More like (I'm guessing) it uses the change in reflected intensity with respect to the change in light position to estimate a surface normal (e.g., forehead is the same for all light positions, left side of your nose is bright when the left light is on, dark when the right light is on, right side of nose vice versa, etc). It then finds a surface that agrees with these normals by solving a partial differential equation. Clever, not simple. (Although I guess it's a compliment to say they make it look easy.)
Nevermind the "real" definition of this or that esoteric concept. If you ask N category theorists you'll get N answers. Just import one that works for you and you're off.
What seems to have gotten this fellow is that either the definitions in the Prelude/libraries didn't match his expectation, or (more likely) he was surprised by the inconsistencies between GHC and GHCi (which I also find annoying.)
And whether that massive data gathering violates privacy? The organization says it never looks at personally identifying information
If it's not personally identifying then how is it useful for attribution?
Anyway, IMO this is not an iOS-vs-Android issue. New markets are going to open up, Android will be there. iOS will still be a cash-cow. Win-win, everybody celebrate (except Microsoft)
Look on the bright side: your PhD is an insurance policy against ageism. When you are 50 you will still be able to find (or make for yourself) low-risk, high-paying work doing neat technical stuff. The VP and C-level peers that you envy so much now will essentially be managers for the rest of their lives.
I went to go check out the code to see if this issue had been fixed, but the download link has gone bad.
I mentioned this library on HN some years back, when I was still excited about it, and the reply I got was something like "No! Not that macro boneyard!" He was right.
The purpose of the technical problem was to assess more directly candidates ability to write Haskell programs that can be used to solve real world problems, where memory usage and performance are important. The problem was all about evaluation order and memory behaviour. We started by asking candidates to look at a short program and say what shape they would expect the heap profile to be. That would then lead on to a discussion of what things are evaluated at what stage and how much memory they are taking in the meantime. For the final step we asked candidates to rewrite the program to run in constant space. We felt overall that the technical problem was quite useful and we allowed it to become a significant factor in our final decision making process.
The choice of problem is based on our belief that a good understanding of evaluation order is very important for writing practical Haskell programs. People learning Haskell often have the idea that evaluation order is not important because it does not affect the calculated result. It is no coincidence that beginners end up floundering around with space leaks that they do not understand.
I've written a lot of C++ and a fair amount of Haskell, and this kind reasoning about the evaluation order and space usage of Haskell a program is no less of a black art than pointer arithmetic or manual memory management in C++. In both cases, it's too steep of a learning curve to just be able to write practical programs, which is why garbage collected languages have displaced C++ in many domains.
It's particularly damning to say that "good understanding of evaluation order is very important for writing practical Haskell programs" because the easiest evaluation order to understand is strict evaluation order. In that sense, lazy evaluation is to strict evaluation as manual memory management is to garbage collection, except that the latter is supposed to be an improvement on the former.
But the caveman explanation for health and nutrition always leaves me cold. Yeah ok we can pretty much gauge what proto-humans ate and why it was good for them, but what if it made them miserable? It's romantic to think that early humans lived in the garden of lo-carb eden, but what if it really fucking sucked? What if they were just plain hugnry all the time, it was miserable and only the strong survived?
Don't get me wrong I think most of the conclusions are right, but I prefer evidence collected from modern people to justify those conclusions. Appealing to evolutionary biology is only valid for survival and reproduction. It doesn't say anything about happiness, fulfillment, etc.
I seem to recall some crackpot theory that low-calorie diets (ie., borderline starvation) increase your lifespan. That would certainly jive with the caveman hypothesis, but does it sound like fun? How miserable are we willing to make ourselves for a few extra years in a nursing home? That's probably a false dichotomy, but you get the point.
Pretty embarrassing for HN to be so reliably trolled.
The whole "these bits are worth $X each" scenario becomes meta-absurd when you consider commercial infringement. At $60K/song, The Pirate Bay would be on the hook for more money than the Earth could produce before it was consumed by the sun.
Also, the happy haacking keyboard already puts control in its proper place and puts esc where ~ normally is, which is close enough that you don't really need to remap it. Best vim keyboard ever.