Not quite. The estimated publication date has kept sliding--later, less specific--with no context or announcements.
The original HN post said, "The final publication date is set for mid-January 2024." Early-access was framed as "so that you can start learning today, but also, so I can get feedback and refine the content of the book with your feedback." Yet in two years there’s been no content updates, no requests for feedback--nothing.
delays happen, and writing a book is tough. But two years of radio silence while still posting plenty of unrelated writing, blog posts, and projects (like Pingoo itself) isn’t the situation that was advertised. An active project with normal delays and complexity is way different than vaporware. Buyers expected an active, rough-but-completion-in-sight project they’d help refine--not immediate and total abandonment and silence.
So after two years of this, seeing Sylvain's frustration about a lack of clarity/communication from someone he's given money to and has expectations of (GitHub), is pretty galling to be frank.
Having no communication from people you’ve given money to sucks, doesn’t it, Sylvain?
If there is a really simple, honest, clear narrative that proves me wrong on all of this, I'd be thrilled. Let's hear it!
Your knowledge of the author of Pingoo makes you more likely to believe that he may have erred? This explanation gains strength for you given your knowledge of his character and personality and professional practices?
He wrote different books about Rust, Cybersecurity, etc.
I just wonder if he may have used, I don't know, a VPN with blacklisted IPs and because he had many connections to his account from it, he was flagged.
Not sure if this was taken into account, but I think there's a huge issue with the study subject itself: violence has always been there, especially in the past, death was not hidden, people were beaten and executed in public, and that violence was not necessarily what would draw people to more violence.
The real question is ethics and morality in a violent context.
And I don't think that aspect was taken into consideration.
The problem is that when you try to not do so, there’s a bunch who comes at you with knifes at your throat: “it’s not our job to code and maintain this”.
Even something which would require 5 lines of code, they would install a package.
I think that may be a really good project. I’m pretty sure if you could make it work properly, a lot of organic farmers would invest into such a solution.
It’s funny how much we limit our understanding of the past by our own current limits.
Back in the days I had quite old teachers who knew few dozens long poems by heart and most of them learnt in their youth.
I think that the way we manage our memory and the context as well as the ratio short/long term memory demands scoped to that context is totally different and is diverging from old times.
As for the writing, there are many instances of long novels where the author radically changes the style even nowadays.
Last but not least, we have inherited a disfigured version of those epics. The originals sung by their authors are long gone. Thus the iterative divergence by the following generations of bards in terms of style and even in addition/deletion is inevitable.
1) either you have the habit, energy and time to systematically rewrite your code properly through iteration;
2) or you are so good that your average throwaway code is considered not that bad.
Because mostly either we are going through well known paths which leads to case 2) or we’re exploring new things and being “skilled & experienced developers” we manage to have the right habits, energy and time to build things iteratively ending up in case 1).
If in the end we still have trashy code, then we need to ask ourselves if we are lacking any of the following: skills, energy, time or good habits (or a proper context, but that’s a whole other universe of problems).
But the man is very clear: https://kerkour.com/cloudflare-for-speed-and-security
> Estimated date of final publication: 2025 (soon ™)
If I'm not wrong, we're still in 2025 :)