The semicolon wars

I found this article very, I wouldn't say informative but, entertaining. It felt like the type of thing that is said as a joke at tech, specially programming and hacking, conventions. Although I was a bit disappointed that "The semicolon wars" where just a tiny reference and not the real topic, even if it probably was better of that way. Apart from that, I also found that it said a lot of things that I've witnessed, at least in the programming communities I've been part of over the last years, although of course a bit blown up for the sake of publishing (I'd guess). It is my belief that any passionate programmer has thought at least once, and probably a lot more than that "Why hasn't a programming language that mixes the best of X, Y and Z languages been made" hoping to meld the best of the handful of programming languages he likes the most. Like that's going to solve all of the little, or big, annoyances he finds while working. And I really liked the part about evangelizing, because a couple classmates appeared in my mind immediately, with their good intentions trying to get everyone to use their language of choice because "it's so much better" or "so much more elegant" or concise or whatever they find to be the best about it. Anyhow I think that the part that makes much more sense is the last phrase: "When you get to the bottom of it, however, I write programs in Lisp for the same reason I write prose in English—not because it’s the best language, but because it’s the language I know best." which is to say; the language you write on is not as important as you may think, whatever you have to do you are probably better of doing it in the language you are more confortable in.

Comments

Post a Comment

Popular posts from this blog

The Roots of Lisp

The Roots of Lisp is, in my opinion, one of the weirder texts we've read, not because it's content is actually strange, but because it is very unexpected. We have been reading mostly blogs or conference transcripts about lisp where the focus in placed on the actual presentation of content and the isn't much code or anything like that. This article on the other hand reads almost like a manual with most of its content being code or brief explanations of it. That caught my by surprise, being used to other styles of text that we have read before. Anyhow, I found it difficult to read (as in heavy not actually complicated) but more interesting than I had expected, even so I don't really think it was very informative, most of what it said we already knew even if we knew it in a less detailed way and it didn't explain or even mentioned new concepts, It just went in to a lot of detail about how lisp was first created as a concept, using common lisp syntax instead of the actu...
Read more

Rich Hickey on Clojure

To be honest this is the first time I don't really find anything super interesting or at least good enough to make a comment about it. Nonetheless given that I do have to do it irregardless of my opinion here it is. I think this podcast wasn't quite as interesting as the rest of the things we've read or heard is because it is kinda getting old: the "LISP (and by extension Clojure) is so much better than any other language in the world" speech is just the same as in all other assignments we've had. The problem is, in my opinion, that we haven't reached yet the ability in Clojure to at least verify the things that we keep reading about. To this point Clojure just feels like a really uninteresting language that has a really ugly and unwieldy syntax, I would even say that there are a bunch of languages out there that would render the problems we've had to deal with trivial, and Clojure has just made it much more complicated. To me it still doesn't feel...
Read more