_nist

One of the major problems is copyright. The copyright laws have gotten so out of hand in this country that things still retain copyright long after the creator is dead. Back when it was first issued, it use to be only 28 years in 1710, but it has just increased and increased... I mean, what good is money if your dead? Does the media industry really need to make more than billions and billions of each year? And its not like they're that original, they release old films and books countless times and you're telling me its impossible to turn a profit in 28 years? It's ridiculous www.youtube.com/watch?v=tk862BbjWx4

Great, now I need to do a bunch of screen touching along with my typing. What a waste of time.

How the hell did some business fluff get on a site called "Hacker News"? 95% of business think can be reduced to fluff, dribel, and nonsense buzz words like "Do things different", "Think innovatively", etc. Why don't they teach them something like "Todays Lesson: The public is stupid, so make a fart noise phone app and you'll get rich."

I'm very skeptical about this. It seems like every time a "supposed" scientific discovery gets published in the media before a peer-reviewed journal, it's almost always wrong. The same thing happened with cold fusion, Ida (aka. Darwinius) the supposed "missing link" between human and ape, and NASA's "supposed" discovery of bacterium growth through arsenic instead of phosphorus.

It's always disheartening when science gets reported to the media at such an early age of discovery (i.e. the point where it hasn't been criticised and the lead investigator himself says he isn't so sure). It just opens the flood gates for the retarded news to make of moronic headlines like: "Roll over Einstein: Law of physics challenged"

Uh... almost any reputable company out there requests a resume when applying to a job. So I fail to see how this article is relevant.

Less lines of code does not equal more efficient code. A single C statement has almost a 1:1 correlation between underlying assembly when compiled, where as a single statement in a high level language usually consists of several assembly instructions.

I think the overarching point is experience with the language. I for one have seen and written incredibly long and convoluted programs in a high level language which was largely due to a weak understanding of the massive API's that come with it. And it would have taken roughly the same amount of time to read and understand what the API functions do and how to use them as it would in C.

In the end, it's all relative and it's totally dependent on experience with the language and what you need for your application.