Show HN: Farolero – Common Lisp style-conditions and restarts for Clojure
1–10 of 37 posts
Re: Show HN: Farolero – Common Lisp style-conditions and restarts for Clojure
#2farolero 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 includes a test suite adapted from ANSI-TEST, and is ready for release after a tiny bit more testing.
Re: Show HN: Farolero – Common Lisp style-conditions and restarts for Clojure
#3farolero 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.
Re: Show HN: Farolero – Common Lisp style-conditions and restarts for Clojure
#4I'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!
Re: Show HN: Farolero – Common Lisp style-conditions and restarts for Clojure
#5I'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!
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!
Re: Show HN: Farolero – Common Lisp style-conditions and restarts for Clojure
#6I'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!
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.
Re: Show HN: Farolero – Common Lisp style-conditions and restarts for Clojure
#7Earlier 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 need to write it a few more times so it is clearer. Also I’m sorry if this is harsh, but technical books should be written by experts who have taught the subject for many years and understand the best way to communicate the subject matter. Otherwise better leave it as a series of blog posts.
Re: Show HN: Farolero – Common Lisp style-conditions and restarts for Clojure
#8Earlier quoted context omitted.
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 need to write it a few more times so it is clearer. Also I’m sorry if this is harsh, but technical books should be written by experts who have taught the subject for many years and understand the best way to communicate the subject matter. Otherwise better leave it as a series of blog posts.
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 writing technical books, which - given that I am not a teacher and likely won't be one - gives the resulting vibe of "just give up" without any possible improvements. I can't make any use of that in order to improve my current or future writing.
Re: Show HN: Farolero – Common Lisp style-conditions and restarts for Clojure
#9Earlier quoted context omitted.
You need to write it a few more times so it is clearer. Also I’m sorry if this is harsh, but technical books should be written by experts who have taught the subject for many years and understand the best way to communicate the subject matter. Otherwise better leave it as a series of blog posts.
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, a book implies something much more. Or maybe I’m just old school and not for the current times. After all, there are countless of ebooks of questionable quality on various programming topics.
Re: Show HN: Farolero – Common Lisp style-conditions and restarts for Clojure
#10I'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.