Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I distinctly remember in one of his talks he said words to the effect of “I wrote corporate C++ and Java for years and eventually realised I had to do something else, or else quit the industry”. So he took a year long sabbatical and created Clojure.


I guess that confirms my theory.


Rick wrote jfli, a Java foreign language interface for Common Lisp, before working on Clojure. He was a seasoned lisper, and he wanted to do something both modern and practical.

It's very interesting to go through the bookshelf he read during his sabatical. He was inspired by many languages aside from CL, including Mozart/Oz, AspectJ, and Prolog.

The bookshelf list was originally on Amazon, committed by Rich, but now behind a login wall. However, a Goodreads clone is easy to access: https://www.goodreads.com/list/show/137472.Rich_Hickey_s_Clo...


He didn't mean he'd quit out of boredom, he meant he'd quit out of frustration with proglangs that bite you in the ass when writing e.g. concurrent programs


Why not quite the niche though? Clojure doesn't make writing corporate CRUD apps enjoyable.


I don't think the particular niche matters, eventually everything becomes being a mundane job.

I know few people that made it in shiny businesses (Serie A and Champions League players like Fabio Liverani and Simone Pepe, or Massimiliano Rosolino swimming gold metal at Olympics) and they all absolutely either hated or found 99.9% of their career an endless marathon of mundane boring activities.

I'm not saying there aren't plenty of exceptions of people that like their job, and jobs that may make it easier, but it looks to me that most of people find their job mundane and boring most of the time.


Agree. Although, as opposed to physical performance activities, be it sports or music, where one of the key activities is to repeat the same thing thousand times, in software, we strive towards not repeating the same thing.


He wasn't writing corporate CRUD apps, he was working on systems like radio broadcasting, voting machines, and Datomic, which involve significant concurrency challenges.


Incorrect.




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

Search: