420 karma · joined October 25, 2008
Some (more or less) fair ways to do that would be to give the goods to those that pay more, or work harder, or wait longer. There are other ways - stealing, cheating, haveing influential friends.
In any case, the scarcity simply won't go away by declaring economics unscientific.
I still remember when I was a kid growing up in communism, there would be days with no potatoes in any store in the city, but there were heaps of rotting oranges that nobody wanted, while the store was not allowed to lower their price. Butchers and gas station operators were among the richest citizens, since those jobs allowed for the easiest cheating on both customers and the state.
While economics is nowhere near an exact science, some people would do better to learn about its very foundations, rather than write lengthy, post-modern-sounding, uninformed criticisms of it.
WRT Larrabee, I agree with you, and I wonder if the scientific market can recover their development costs.
http://www.haskell.org/tutorial/
For those already proficient with programming that just wnat to pick up Haskell, it's ideal.
Then I would suggest an exercise that involves manipulating abstract syntax, for example parsing and interpreting a little language. ("Build yourself a Scheme..." might be good though I didn't read it myself.) This is where the language really shines, and you don't need any of the recently popular trickery like arrows or GADTs.
CH is a statement about the existence of an abstract infinite set, so it is not that surprising that its truth depends on your very definition of a set, an elusive object with multiple possible meanings.
On the other hand, P=NP is a statement about boolean formulas, Turing machines and polynomials. None of these are elusive, they are very cleanly defined, trivial concepts. So it's a very well-posed question.
Of course, we could still not be able to prove the (non)existence of a polynomial algorithm for SAT in ZF set theory. In that case, too bad for ZF, but whether P=NP is still a meaningful question.
But I agree, the blog isn't about this issue at all.
However, if Bing gets to a point where their search results are clearly better, then Google will be in trouble, and no amount of screaming "we have a better infrastructure!" will help. Users want the best results, and that's why Google originally won against other search engines.
I don't know if that's ever going to happen. Probably not, but I would not bet on it.
The only thing I can think of is some light-weight collaboration, but more involved collaboration is better done using version control anyway. This is outweighed by the disadvantages of having to deal with clunky Javascript/Flash apps and slow internet connsections.
There are many cool things to be done on the cloud, but Office-style apps just don't seem to be a good example.
My point, instead, was that FP does not break down when things get ugly; on the contrary, it gives much stronger guarantees on correctness. Of course, it takes effort to express the problem in the more restrictive functional paradigm.
If you have a function that moves a player in a game such as movePlayer :: PlayerState -> PlayerState, you know that it only changes the state of this player, and nothing else. In an OO language you would do something like player.doUpdate(), which has absolutely no guarantees.
Plus there are many facilities available to deal with threading and hiding state.
But I somehow cannot see any functional programming hype. Where are the people heralding it as solving all problems? Even in a place like HN with a highly non-average community of programmers, the FP links are quite rare and very intro-level. I would say FP is a high-hanging fruit that's only starting to find a few niches in real-world programming.
So I son't see anything close to an FP hype, nowhere near to the Java hype or Ruby hype.
Quite the opposite - functional programming is becoming very appealing as a practical alternative for building large, multi-threaded, correct systems.
True, it might be a bit more tedious to write a program that type-checks, but as many (including me) have been repeatedly amazed, it often works correctly right away, with minimal debugging.
But it also may be that almost no one has been thinking about problems like this
Mutable state is a fundamental issue that every functional programmer deals with every day. Indeed, it might be sometimes frustrating to pass around state that in C would be directly modifiable, but the benefits are huge.
Pure code has been called a "scarce resource", and that's exactly right - once it works, it will always work, no matter how huge is the system you build on top of it.
Most CG movies and effects (from Pixar, Dreamworks, ILM, ...) also do not have anything close to photorealistic lighting (i.e. correct global illumination), but they do not look grey.
One common mistake that leads to washed-out images is to apply gamma correction (which is the right thing to do) but not apply inverse gamma correction to your textures. That way your surfaces are essentially gamma-corrected twice, which is clearly wrong. I don't know if they're really making such a simple mistake, but who knows...
2. CO2 concentrations are clearly rising.
3. Well-understood physics suggests that rising CO2 should lead to rising temperatures.
Does this make it 100% certain that we're causing global warming? Maybe not, but if you want to disprove the link, you're going to need better arguments than "41% of laypeople think global warming is exaggerated".
I was just a bit upset at the dichotomy of "industry = responsibility, having to deliver" and "academia = lack of such responsibility". I think we know better now what each of us meant.
"Do x, y, and z by the first of next quarter or you're out of business." Sure, but new developer hires in large companies are absolutely not in a position to decide where the business is going, and won't be for quite some time. The article and my comment were about the entry-level developer positions.
"And for everyone of those, there is someone else changing the world." Absolutely, and I greatly admire such people. But you won't change the world in an entry-level developer job. I tried such jobs, they were very easy and I suffered a lot the lack of opportunity to change the world.
"Deliver something every day to someone who is depending on you" - this is exactly what you have to do in a Ph.D. program all the time - you have coauthors on papers that have to be shipped, and yours and their future depends on it.
In the corporate world, you also have to deliver, but at least what you're doing is well known to be possible. In academia you have a constant feeling that you might be against an impossible problem, and the results will never come together.
Plus in the corporate world, you can work 9am-7pm at most, rather than 11am-2pm as in grad school. And the pay is 4x higher. Now what sounds more like a vacation?
(Of course, here I was referring to a PhD in Computer Science. I don't know what's Strategic Planning, so I can't judge there.)