HNHacker News
TopNewBestAskShowJobs

unlogic

137 karma · joined August 2, 2011

submissionscomments
unlogic··on Another year of Clojure
You are right that The Joy of Clojure is for developers with some prior experience in Clojure and it explains the "why" of the language even further.
unlogic··on 50 Years Ago: The World in 1962
You can search for automatically created analog curcuits here: http://www.genetic-programming.com/humancompetitive.html

There are also examples and explanations in John Koza's "Genetic Programming" series of books.

unlogic··on [dead]
I don't have the "Feynman Lectures on Physics" where the driver and police officer situation originally took place. The book "What Do You Care What Other People Think" I own (audio version, read from 1989 edition) contains the story "Feynman Sexist Pig!" that is reprinted in the blogpost (and it seems to me, completely unaltered) has no clues or hints on the police officer gender in the initial story.
unlogic··on [dead]
I'm sorry to provide Feynman's story in this kind of wrapper. I've just read this in Feynman's book and this link was the first in Google where I found it. Please consider the identity of the blog author irrelevant to the story.
unlogic··on Girls and Computers
> I'd rather focus on explanations that offer disprovable models we can use to fix the issues at hand if they turn out to be correct.

So you are saying that you would fight one issue rather than another based not on arguments and evidence, but on the fact that the first can be fought and the other cannot (which is itself speculative)?

In my opinion this kind of reasoning has serious flaws. You could see already commenters on HN who say something like "Reading all these posts about sexism and women discrimination I don't want my daughter to work in IT". Doesn't that contradict to what we are fighting for - for bringing more women into IT industry? Doesn't it have to start with equal opportunity for children rather than fear (which in some - many - cases is wrongly induced?

unlogic··on Go is amazing, period.
> This discussion is increasingly weird and non-technical, mostly because there is no such thing as "Lisp". There are implementations of Common Lisp, implementations of Scheme, there is Clojure on the JVM, all of those are in the "Lisp" family. So comparing a particular language to "Lisp" makes no sense.

Since I've posted a link to Shootout comparison of Go and Common Lisp I thought I made it clear which Lisp I was talking about.

> And I don't understand the comment about things being "precompiled". So what?

It means that a descent part of the computation was done in the compile (macroexpansion) time and this time was not measured and included into the total result. This may be great for cheating Shootout benchmarks but does not fairly demonstrate the performance of the language.

unlogic··on Go is amazing, period.
Well, the link to the shootout statistics is probably not the best demonstration for Lisp speed/memory consumption/SLOC count relation. If you look into the Lisp sources there you will see that there are lot of things precompiled for the sake of reducing the execution time. Here's where the extensive memory usage and source size come from.

I intended to say that Lisp's and Go's both performance and succinctness in the wild are probably on par. But Lisp is already there for a long time.

unlogic··on Go is amazing, period.
Lisp has been having all these for five decades now and those features are done fast. http://shootout.alioth.debian.org/u32q/benchmark.php?test=al...
unlogic··on Ingo Molnar on what ails the Linux desktop
> tldr; apt needs to absorb homebrew.

An excellent package manager that exists for 14 years already is being told to mimicry a primarily inferior set of cruthes? The world has definitely gone mad.

unlogic··on Daring Fireball: The iPhone 4S
And that just means keeping your GPS turned on the whole day. Sure, I always dreamed about losing all my battery charge to such an insanely great feature.
unlogic··on Writing Tetris in Clojure
I am absolutely sure you can write Tetris in 100 lines of C. Would you be able to maintain it in half a year? Would anyone except you at the moment of writing be able to understand it? I wrote this implementation in January, found it and understood again in one go. There is even no comments in the source file. The Clojure code is mostly self-documenting (sure thing, you still have to write comments for bigger projects). And yes, I also liked the OpenGL version more. It is very nice except some logic being based on try..catch blocks.
← PreviousPage 3 of 3