152 karma · joined October 5, 2018
If you want DRM, go to Microsoft or Apple.
I guess writing a numeric library, like Python's NumPy, is a lot more convenient using generics. But I've never tried...
Maybe it is just revealing where those programmers are coming from. Java and C++? Angle brackets! Eiffel, Scala? Square brackets!
Are there any parser considerations (like <Foo <Bar>> being an issue in C++, afair), or is it just taste (or Scala vs. C++ background)?
"But Hitler also started his movement in the Bierkeller!!!1" ;-)
I'll update accordingly!
`sort -h` is only needed because `du -h` is used in the first place. I admit that `du -h` comes in handy often, it is better not used for further processing.
Your proposed approach is not only more Unix-like, but also does not require bloated implementations of `du` and `sort` capable of parsing human-readable size indications.
I probably won't be able to read it before July, anyway, because I have to finish my bachelor's degree first. But I think it's not a bad time for a financial contribution to my favorite tech book publisher, so I already bought the book "blindly".
Please tell this Felix von Leitner (fefe.de, blog.fefe.de), and post his reply in this forum.
His blog software is written in C. It's one of the most frequented blog in German speaking countries and running on a single machine (AFAIK).
Of course, not everybody has the expertise to build something like a blog in C.
Many books nowadays, also from NoStarch, are released as early access books. Your book does not run under the early access program, or at least not yet.
Is this a decision made by you as an author? Or is the kind of book not really suited for early access? I could imagine that introductory books work well as early access books; readers could work through the first couple of chapters, while later chapters are still being written or refined.
Just curious...
The book is supposed to be around 270 pages, so verbosity probably won't be an issue.
I am right now working through "Python Crash Course" as an intermediate Python programmer. I very quickly read through chapters 1-8 so far and did all the exercises (rather simple ones), just to make sure that I'm not missing out anything on the basics. In the last couple of chapters, I actually picked up two or three pieces of knowledge I wasn't aware of. I spent around five to ten hours on this so far. This approach sounds terribly inefficient.
However, working through a beginner's book as an intermediate Python programmer, and only getting half a dozen of really new information out of it, gives me the confidence I need at this stage. So I don't consider it as a waste, but rather as an exercise in patience and repetition.
Why am I telling you all this? Because I think people overrate the monetary costs of books.
NoStarch never let me down so far, and paying USD 60 (or 40, or whatever) is such a marginal difference for a book you're going to spends dozens of hours on.
When I see that Brian W. Kernighan releases a book, it's an instant buy for me.