321 karma · joined October 17, 2007
In my opinion, if a business model requires there to be no public libraries or a substantially reduced public library, then so much the worse for the business model. There needs to be an analogue between the world where books are things made of paper and the world where books are made of bits.
I think if you learn the fundamentals (and that often means having a good grasp on C) it shouldn't be too terrifying to pick up at decent grasp on lots of languages.
%%(diary-anniversary 14 2 1940) Dad turns %d
Check out the EmacsWiki for more examples: http://www.emacswiki.org/cgi-bin/wiki/DiaryMode#toc11 (defstruct mountain :name :latitude :longitude :country)
(struct mountain "Zugspitze" 47.416667 10.983333 "Germany")http://www.wired.com/underwire/2009/07/sci-fi-channel-reboot...
In the more technical areas there are the predictable "Here's a homework question that I'm sort of trying to disguise" and, what the article said, "How do I build a forum." What Yahoo Answers REALLY needs is an FAQ in each category. But, I suppose, then it would be IRC.
(let [#^int a 2
#^int b 3]
(cons a b))
a and b are not hinted to be primitive types. Type hinting is purely for objects. Use hinting to make it clear to the compiler what sort of objects you are passing into something (e.g. a constructor that takes a String). If there is confusion, clojure will do reflection.The right thing to do in this case, is the second thing that the author mentions:
(let [a (int 2)
b (int 3)]
(cons a b))
a way to see that a and b are really primitive is: (let [x (int 5)]
(.shortValue #^Integer x)) ; exception: "can't type hint primitive..."
There's a post on the mailing list that goes over this much better than I did (and where I drew the examples): http://groups.google.com/group/clojure/browse_thread/thread/...I understand that this is really beside the point, that the author finds type hinting syntax unattractive, but I just wanted to clear up confusion (if there was any).
EDIT: clarity
Feynman has great examples of this type of work: "The Character of Physical Law" or "The Feynman Lectures on Computation" are both excellent. I've found that these books walk somewhere between textbook and popular science book. Easy to read but all the while teaching you the material.
I've found this type of work to be the crucial link between pop. science and a textbook. You learn enough that you can find your footing when you're in a textbook and and also the inspiration to actually read it.
But I think something else is going on here, the Inscrutable Macro idea serves as a kind of "intuition pump" (of the negative kind) http://en.wikipedia.org/wiki/Intuition_pump to try and demonstrate macros' badness. If someone isn't very familiar with lisp they'll offer code that's merely not idiomatic, when someone is familiar with lisp then they'll offer up something that's just downright pathological, and I'll be the first to admit, that a pathological macro can be really pathological. At this point, equipped with their executable straw man, they claim "this macro is insane, and so macros are unmanageable."
If the measure for unmanageability is just that impossible-to-understand code can be written in some language then the IOCCC means C shouldn't be used.
In practice the Inscrutable Macro just isn't written.
.java -> [javac] -,-> .class -> [dx] -> .dex
/
??? ------------'
Has anyone done this, with Clojure, for example? "Whether stability is such a good thing in a downturn,
though, is a different matter. A decade ago Andrew Oswald
of Warwick University argued that owning your own home
makes you more reluctant to move, so labour markets tend
to become more rigid as home ownership increases. He
claimed that increases in the level of home ownership
(though not necessarily the level itself) are associated
with rises in unemployment. Ireland, Greece and Spain all
saw large increases in home ownership in the 1980s and
1990s, and had relatively high unemployment. America and
Switzerland had stable ownership rates, and escaped the
long-term rise in joblessness."My feeling is that a lot of science jobs will rely on the Linux/Unix platform. Backend or system control type things are on Linux and a lot of personal computers are OS X.