Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Farolero – Common Lisp style-conditions and restarts for Clojure

github.com

Post reply on HN
Print view View original

11–20 of 37 posts

Re: Show HN: Farolero – Common Lisp style-conditions and restarts for Clojure

#11

Post by phoe-krk »

sglisp wrote: post #9
phoe-krk wrote: post #8

Earlier quoted context omitted.

I don't understand the first sentence; do you mean writing it several times in succession and completely discarding all results but the last one, or more like an iterative process that actually looks back at what was written previously and improves upon that content? Also, I don't think I can really make use of the latter part; it implies that only people who have taught the subject for years are qualified for writin…

Take a few weeks break between each write, you will start to see areas that are clear and those that you will not like. Connect the flow of paragraphs and chapters to each other - hard to see all this when you first write it down; but after taking a reasonable break - you will start to see which areas to change. I get your point on not being a teacher, but I would recommend doing it as blog posts then and not a book,…

OK - thanks, I'll keep that in mind for my future writing and for the second edition of TCLCS (if it happens). The first edition was written pretty fast (a total of six months?) and it did not have enough time to have enough of the "few weeks breaks" that you mentioned, so I can understand that it suffers from lack of text maturity.

I'm curious about "a book implies something much more" though. I have seen multiple series of blog posts that then grew to the point where they were actually published as books. What's the difference between the two when one wants to tell them apart via their content? What's this implication that you mention?

Re: Show HN: Farolero – Common Lisp style-conditions and restarts for Clojure

#12

Post by ghufran_syed »

blacktriangle wrote: post #10
phoe-krk wrote: post #4

I'm glad to know that my condition system book is of some really concrete use; an independent implementation of CL-style conditions and control flow in Clojure is probably the best example I can imagine for that. Congratulations, and thank you!

Bought your book. It was a huge help to me understanding the CL condition system. Thank you very much for taking the risk to write a much-needed treatment on a niche topic of a niche language.

Which book are we talking about? could you post a link or a title please?

Re: Show HN: Farolero – Common Lisp style-conditions and restarts for Clojure

#13

Post by the-smug-one »

ghufran_syed wrote: post #12
blacktriangle wrote: post #10

Earlier quoted context omitted.

Bought your book. It was a huge help to me understanding the CL condition system. Thank you very much for taking the risk to write a much-needed treatment on a niche topic of a niche language.

Which book are we talking about? could you post a link or a title please?

The Common Lisp Condition System: Beyond Exception Handling with Control Flow Mechanisms phoe is the author.

Re: Show HN: Farolero – Common Lisp style-conditions and restarts for Clojure

#14

Post by harperlee »

fiddlerwoaroof wrote: post #3
suskeyhose wrote: post #2

farolero is a full, thread-safe implementation of Common Lisp conditions and restarts for Clojure. Most of the other implementations are incomplete or fail in cases related to threading, or don't include a debugger. This implementation is full. I have plans to make an nrepl-integrated system debugger for integration with cider, although the existing debugger is quite good already. This library has just hit RC3, which…

This is pretty cool, conditions/restarts were one thing I always missed in my repl-driven workflow when writing Clojure. Now someone just needs to implement a reliable way to add/reload dependencies without restarting the REPL.

> Now someone just needs to implement a reliable way to add/reload dependencies without restarting the REPL.

Alex Miller is working on this as an official clojure functionality, see the add-lib, add-lib2 and add-lib3 branches of deps.alpha. It's just brewing very slowly... hopefully with Tonsky now on board they are able to speed up this and other topics!

Re: Show HN: Farolero – Common Lisp style-conditions and restarts for Clojure

#15

Post by phoe-krk »

ghufran_syed wrote: post #12
blacktriangle wrote: post #10

Earlier quoted context omitted.

Bought your book. It was a huge help to me understanding the CL condition system. Thank you very much for taking the risk to write a much-needed treatment on a niche topic of a niche language.

Which book are we talking about? could you post a link or a title please?

the-smug-one already posted the title. It was discussed on HN twice:

https://news.ycombinator.com/item?id=23843525

https://news.ycombinator.com/item?id=24867548

Re: Show HN: Farolero – Common Lisp style-conditions and restarts for Clojure

#16

Post by nightwolf »

harperlee wrote: post #14
fiddlerwoaroof wrote: post #3

Earlier quoted context omitted.

This is pretty cool, conditions/restarts were one thing I always missed in my repl-driven workflow when writing Clojure. Now someone just needs to implement a reliable way to add/reload dependencies without restarting the REPL.

> Now someone just needs to implement a reliable way to add/reload dependencies without restarting the REPL. Alex Miller is working on this as an official clojure functionality, see the add-lib, add-lib2 and add-lib3 branches of deps.alpha. It's just brewing very slowly... hopefully with Tonsky now on board they are able to speed up this and other topics!

Do you mean Fogus, or have I missed something?

Re: Show HN: Farolero – Common Lisp style-conditions and restarts for Clojure

#17

Post by harperlee »

nightwolf wrote: post #16
harperlee wrote: post #14

Earlier quoted context omitted.

> Now someone just needs to implement a reliable way to add/reload dependencies without restarting the REPL. Alex Miller is working on this as an official clojure functionality, see the add-lib, add-lib2 and add-lib3 branches of deps.alpha. It's just brewing very slowly... hopefully with Tonsky now on board they are able to speed up this and other topics!

Do you mean Fogus, or have I missed something?

Yeah sorry; that would have been interesting, but fogus.

Re: Show HN: Farolero – Common Lisp style-conditions and restarts for Clojure

#18

Post by sglisp »

phoe-krk wrote: post #11
sglisp wrote: post #9

Earlier quoted context omitted.

Take a few weeks break between each write, you will start to see areas that are clear and those that you will not like. Connect the flow of paragraphs and chapters to each other - hard to see all this when you first write it down; but after taking a reasonable break - you will start to see which areas to change. I get your point on not being a teacher, but I would recommend doing it as blog posts then and not a book,…

OK - thanks, I'll keep that in mind for my future writing and for the second edition of TCLCS (if it happens). The first edition was written pretty fast (a total of six months?) and it did not have enough time to have enough of the "few weeks breaks" that you mentioned, so I can understand that it suffers from lack of text maturity. I'm curious about "a book implies something much more" though. I have seen multiple s…

At least for me, those blog posts that become a book are not of very high quality. Very bad actually.

For example, books (at least used to) have editors, and reviews by multiple specialists in the field. I can’t think of distinct step between personal writing and something publishing, so I cannot add meaningful comments to your question.

Re: Show HN: Farolero – Common Lisp style-conditions and restarts for Clojure

#19

Post by phoe-krk »

sglisp wrote: post #18
phoe-krk wrote: post #11

Earlier quoted context omitted.

OK - thanks, I'll keep that in mind for my future writing and for the second edition of TCLCS (if it happens). The first edition was written pretty fast (a total of six months?) and it did not have enough time to have enough of the "few weeks breaks" that you mentioned, so I can understand that it suffers from lack of text maturity. I'm curious about "a book implies something much more" though. I have seen multiple s…

At least for me , those blog posts that become a book are not of very high quality. Very bad actually. For example, books (at least used to) have editors, and reviews by multiple specialists in the field. I can’t think of distinct step between personal writing and something publishing, so I cannot add meaningful comments to your question.

I've had the book reviewed and edited by several people (mentioned in the front matter), and you're not the first person to complain about the long-winded style. This likely means that we collectively screwed up with regard to the English layer of the book.

Thanks for the feedback; I'll let my reviewers/editors know, get this fixed in the second edition, avoid doing that in my future writing.

Re: Show HN: Farolero – Common Lisp style-conditions and restarts for Clojure

#20

Post by sumnole »

phoe-krk wrote: post #6
sglisp wrote: post #5

Earlier quoted context omitted.

I bought and read your book. Unfortunately it is long winded and poorly written, so I advise others not to spend time and money on it. Bit disappointed that it gets misleading treatment online, I was expecting a book by an expert, but I guess lesson learnt when making judgement based on what is written online - those who post more aren’t necessarily any expert in the field!

Sure, please tell me more about it; I'd like to know what in particular can be fixed in it to make it better. I already know that you're dissatisfied with it and you're up for getting personal at me, but I think that I'll need more details to ensure that whatever is wrong with this edition of the book doesn't get replicated in the future.

You're giving this troll way too much food.
Post reply on HN