Hacker News new | past | comments | ask | show | jobs | submit login

Odd choice. A little more research could've yielded a migration to something like Clojure with the benefits of Lisp and an industry-backed stack (JVM).

Of course using an offbeat stack is going to hurt - doesn't mean you have to give up Lisp too.

A decision made odder still since being an independent project, one would think maximizing individual productivity would be the only hope of yielding anything novel and useful in a field like search that isn't a fitting of an off-the-shelf to a business problem. (Something I've done before, it was quite neat.)

Go is not a language focused around individual productivity in any capacity or scope. It's the language of pyramid-building Egyptian Pharaohs. (Throw 1,000 lives at it, it'll get 'er done...)

I say this as someone rather envious of any language that has a native compiler that builds static binaries. (Oh, OCaml...)

As we ponder on what orangetide is up to, lets keep in mind he's not explained or revealed anything at all about Nuuton and for all we know - could be having us on for the sake of self-promotion/promoting Go.

The incorrect speculation about the origins and purpose of Go make this even stranger.

Go exists to make people like Rob Pike happy. The Plan9 and Suckless community of programmers. Those types. That it happened to solve the problems of some Google programmers who were making it was almost incidental.




As we ponder on what orangethirty is up to, lets keep in mind he's not explained or revealed anything at all about Nuuton and for all we know - could be having us on for the sake of self-promotion/promoting Go.

Well, you are right. I am promoting Nuuton. After a almost a year of working on it and not speaking much about it, I decided to start opening up. I don't want for it to fail due to being too secretive. Time will tell if this is the right decision. But I'm having a great time building in Go. If all fails, I will still have the knowledge of doing it.

Edit

I also considered Clojure. Even spoke about it to some people on this board. But it seemed to take me along the same path Lisp did. Still a fine language, though. I have nothing against it. It did not make much sense in my mind.


I'd dearly love to know what about Clojure made it inappropriate for you.

My own path was GW-Basic -> C -> Common Lisp -> C# -> Python -> Clojure, with other languages learned along the way.


> Go is not a language focused around individual productivity in any capacity or scope.

Seems to have been my impression as well. Lisp with its macros can make an individual programmer who doesn't need to worry about coding conventions incredibly productive. I see Rust has a semi-powerful macro system too although not to the extent of Lisp, as it doesn't look like you can evaluate arbitrary code at compile time.


I was attracted to Go at the beginning due to Limbo and Oberon influences that the language has.

Even did some coding in Go for a few minor projects.

But that experience showed me that it actually felt like a time travel back to 1992, when I was using Native Oberon.

Sure the language feels like a better C and I find it good that it has native code compilers as the default implementation.

But since 1992 we have gained lots of abstractions in mainstream languages that it is pity to throw them out of the window.


> Go is not a language focused around individual productivity in any capacity or scope.

I don't know the motivation behind the people developing Go, but I found it very easy and convenient to work with it, almost as easy as with Python sometimes, which is mind-blowing IMO given the static, compiled, strict, etc. nature of Go. So again, don't know whether the guys behind the language were motivated by personal productivity, but they have definitely achieved it.

Though I didn't really try Lisp other than quick tutorials, so I can't make a comparison with that.


Interactive programming is like escaping the Matrix when all you've done up to that point was standard compiled or interpreted languages.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: