2,544 karma · joined June 15, 2010
(require 'package)
(add-to-list 'package-archives
'("marmalade" . "http://marmalade-repo.org/packages/") t)
(package-initialize)
(when (not package-archive-contents)
(package-refresh-contents))
(defvar my-packages '(clojure-mode ...)) ; list of packages
(dolist (p my-packages)
(when (not (package-installed-p p))
(package-install p)))At least IntelliJ has Emacs-style DWIM tab, but still has a whole host of problems with its better than Eclipse but still subpar editor.
Even as a beginner text, I think it's a bit lacking due to hurried presentation. This Coursera class is a far, far better presentation of intro FP, and a much better intro to Scala IMHO.
This is one of the bigger reasons I'd be pretty wary of managed blogs again, although I guess I'm probably not the target audience for them since among the alternatives I'm thinking about is a few Emacs Lisp functions calling Org mode, which I admit is a little fringe.
It's never really caught on though, I would guess due to inertia. Most Lisp programmers just get used the parens, and maybe those that can't end up not using Lisp.
Ah ok, that makes much more sense.
I can't really speak to what is clear or not for a first-year Clojure dev. When I first learned Clojure, I had already dabbled in Lisps and Schemes for a while. The very first time I ran across `read`, probably in Scheme, it was obvious to me that it was special. Did I understand and appreciate the security implications? Probably not.
Hopefully the security issues will be clear to a new Clojure dev since at least the ClojureDocs site steers you away from read and towards EDN. Maybe the official docs should be more stern and clear about it, but they do make a note of the security issue: http://clojure.github.com/clojure/clojure.core-api.html#cloj...
Assuming that by `gets` you mean Ruby's `gets`, this is not quite right. `read` (and `read-string`) are not just generic IO functions. They are parsers for Clojure code. There are plenty of other varied forms of reading input to a string, but `read` does more.
This almost implies that there is no opportunity for anything new in programming language research, which I find laughably depressing, especially if you take "some popular language somewhere" to mean the popular industrial languages. It would be rather sad to think that Java (or C++, or C#, or Ruby, or Python, ...) represents the pinacle of programming language design, and we're stuck with it and its ilk from now on, forever, since there are no good language features left that are worth implementing.
Languages which support this (including Agda, I believe) usually support some fallback to ASCII, allowing you to type "->" instead of a Unicode arrow, because it's easier to type on the vast majority of keyboards.
Of course, APL also famously uses all kinds of symbolic nonsense.
> There are instructions within the game, and without in the form
> of wikis and forums, but I wanted to begin at the most basic
> level, if only to come at the game from a recently trendy (if
> controversial) design paradigm on discoverability that's flowed
> from mobile apps to many new indie games: "if you see a UI
> walkthrough, they blew it".
Some of the author's other points are valid, and DF definitely has some (just some!?) problems with the UI (my personal nitpick is that there are multiple ways to draw rectangles) but I get the impression that she set things up planning to fail. Not R-ingTFM isn't really a reasonable way to review this game. DF doesn't have a team of people behind it, and there's no UX designer to figure out how to make things beautiful and intuitive. On the other hand, the game is free, and the developers have supposedly turned down at least one relatively large buyout offer in order to keep working on their dream on their own terms.It's cliche, but you get out of DF what you put into it. If poring over fan-made wikis, taking notes of all your findings, winning tiny victories like successfully getting your first workshop running, and losing in spectacular fashion only to retell your loss to friends doesn't sound fun, maybe stick to Skyrim.
The power of "code is/as data" means that Lisp macros can manipulate code as easily as other Lisp code manipulates data. It's not really about eval.
> I wrote some code with lots of nameless functions as input parameters (think JavaScript style or Ruby blocks), which of course was an ugly pain to port to Python with no multi-line lambdas.
As nnq points out elsewhere in this thread, this doesn't have anything to do with significant whitespace. Python only allows you to have a single expression in the body of a lambda, and from what I've read the reason it stays this way is to discourage using a lambda as an argument to map, fold, filter & friends. The usual suggestion from Python programmers is to just use a locally defined, named function, which to be honest is often what I do anyway in languages like ML, because it's clearer.
And anyway, just because it was hard to port some code from language A to language B due to something different about B doesn't really seem like a valid knock against B.
I'm just speculating here. I don't really have an opinion one way or the other, although I don't think anyone's an idiot for having an opinion about it, as the OP does.
var foo *[]*FooType
http://news.ycombinator.com/formatdochttp://en.wikipedia.org/wiki/Considered_harmful
Plus it's a quick way to write a pithy link-bait title (not commenting on the OP, but in general)
edit Actually according to Wikipedia Dijkstra's original title was different, and Niklaus Wirth changed it. I didn't know that, funny little bit of history.
Whether you think that's a good thing or not is another story. Or maybe you think farmers should be able to save GMO seeds. I won't argue with you there, but the process of farming most definitely has changed, and it's not the same as it was thousands of years go.