This sentence does not lend the rest of the article much credibility.
664 karma · joined February 8, 2008
This sentence does not lend the rest of the article much credibility.
As for the wisdom of the NIF as public policy, that's something on which reasonable people can (and do) disagree. I'd only point out that the first government to master the goal of break-even fusion (getting more energy out of the reaction than is put in to trigger the reaction) will gain a _ridiculous_ economic advantage over the rest of the world, to say nothing of the non-economic benefits of energy independence. It's the kind of big bet that rich nations can (and in my opinion should) take.
Furthermore, if you actually switch back even for a few minutes once a week or so, your Qwerty typing won't atrophy much at all.
However, I wouldn't bother switching unless you're pretty sure that you're going to be spending several hours a day typing, and mostly on the same small number of computers. Reconfiguring any modern computer back and forth between Qwerty and Dvorak is easy, but it's completely maddening for anyone with whom you share a computer.
http://ftp.squeak.org/docs/OOPSLA.Squeak.html
Also consider that a bunch of languages (most?) consist of a kernel (or other VM) written in something native (like C) surrounded by a bunch of libraries written in the language itself. Off the top of my head: python, java, clojure, most schemes, etc. are like this.
For ridiculous exercises in bootstrapping minimalism, check out Ian Piumarta's work on Cola:
http://piumarta.com/software/cola/
Won't she be pleased!
Markdown similarly hides (automates) all the details of how it generates HTML from source, and in exchange you give up control over (many) aspects of what the target HTML looks like.
My car abstracts away from me the details of fuel-air mixtures, gear shifting, battery recharging, and so forth.
In all of these cases if I want more control I can go get it. The point is that I don't _have_ to: I can drive the kids to school, document something in reasonably nice HTML, and get a damn window on the screen without having to think (as much) about it.
Edit: Geez, people. Lighten up!
100 kWh / year == 100,000 W / (years/hour) == 17.1 W.
so we save 17 W per computer. This is good, though less impressive-sounding.
Another way of looking at it is that a kWh of electricity costs something like $0.10. Saving 100 of those a year is ten bucks per computer. $10 per PC per year is nothing to sneeze at if you have a lot of computers.
I know at least one would-be programmer who is not scared away by complier errors, but he is almost comically infuriated by them: not their presence, but their customary vagueness and unhelpfulness. Such a tool as this might provide an intellectually curious sort like him to learn proper syntax for common programming concepts without having to dig through man pages or web pages, and without lots of trial and error.
The pipe character is used to indicate that the output of process A is piped to process B. I guess it's a pun. My apologies for horribly overexplaining.
The key feature of the reading group, I thought, was that we were able to identify, right in our production code, right there in the conference room, instances where we used particular idioms from the SICP section under discussion. It was that identification of actual fancy SICP concepts (in scheme-world) in the familiar production code (java-world) that made this particularly worthwhile; folks (including me) saw a whole bunch of places where our java codebase would be (or had already been) improved by applying what we were reading about in the book. It was among the more useful exercises of my professional career so far.
So perhaps this django-based discussion group could include illustrations from a reasonable open source codebase (django itself?).
Sounds like great fun.
“Will a company be able to operate completely on these games? No,” Mr. Yoshida said. “After all, we’re talking about the kind of games people make sitting in a cafe with a laptop.”
A person sitting in a cafe with a laptop might be able to operate completely, though.
We recently gave up on GWT at work for precisely the reason that IE6 and friends are waaaay too slow to do anything meaningful in GWT. Had we had this option we might have stuck with GWT instead of rewriting in Flex.
http://www.thecorporation.com/
(spoiler: a sociopath)