The Year of the Vulkan Book | Hacker News Reader

The Year of the Vulkan Book

jorenjoestar.github.io

67 pointsibobev21 comments

I have this terrible bias about pack-pub publishing that I associate with low quality books because of the unity books I bought 4-5 years ago. Which is unfair cause I’m sure I’m missing high quality books.

I have the opposite bias towards orielly and nostarch books. which I regard as high quality. And I’m sure theres also terrible books there.

I have the same bias. It’s a bias based on all packt pub books I’ve read so far.

Reading this blog, it’s another author who isn’t a native English speaker; and it shows. I’m betting there will be plenty of bugs and typos in this book as well unfortunately.

Native English speakers write less buggy code? That's a pretty good competitive advantage.

Technical books aren't just about the code itself. Programmers don't necessarily make for good technical writers, and non-native speakers of any language are worse writers on average in that language. Put those two things together, and a non-native programmer writing their first book needs all the help they can get with editing and reviewing the text.

Even a native author will need all the help they can get with editing and reviewing the text. But yes, even more so for non-native speakers.

Oh no, I did not mean to imply that. Just that quality control at packt doesn’t seem to great, so the books contain bugs and typos. The latter probably more if the author is not a native speaker.

I don’t think your bias is unfair, I once bought a Packt-published book and it was _bad_ (to put it nicely).

These are heuristics. They work most times (so I don’t buy Packt anymore).

Unfortunately it's true. They mass-recruit authors who want to be "published" via solicitation emails and then provide them limited support (as well as a limited or non-existent advance).

That doesn't mean there are no good Packt books. There are. It just means the average of quality will be lower than some other more picky publishers.

I feel bad for the good authors who get lumped together with the bad authors by virtue of their publisher. And I feel bad for the potentially good authors who just didn't get enough support in the writing process.

Don't judge a book by its cover or its publisher, but you may want to be a little more skeptical when Packt is the publisher on average.

The saddest part is how a lot of technical work goes to waste, because Packt won't give authors even the bare minimum technical review and copy-editing support.

I started reading "Mastering Linux Device Driver Development" a while ago but I found it to be almost unreadable, and I gave up after a couple of chapters. On top of the at times incomprehensible grammar, I found a few too many errata in the form of "can" vs "cannot", "only by" instead of "by only", etc... that change the meaning of the text significantly. It was too much work to pause every time I found the text confusing, to figure out what the author really meant.

I buy mostly ebooks for technical stuff, no need to kill trees in fashion driven industry, so I take advantage of Pack deals when they come around.

Yes there are plenty of books that aren't that good, but there are also quite nice gems there.

Oreilley was good in the golden days of UNIX, nowadays it is just like any editor.

The few NoStarch books that I have, with exception of the Rust book, all seem quite superficial to me, more towards begginers.

There's literally nothing unfair about this. Publishers have reputations, and they matter.

I just bought this book thinking it would be good. It's not. It jumps all over the place you have to sort of piece together what's going on.

That's a shame, this book seemed like exactly what I was looking for.

Yeah, if anyone knows of a good, coherent, well written Vulkan book that properly explains things instead of just enumerating API specifics (or if this is that book), I'm keen to hear of it.

Have you seen "https://vkguide.dev/"? I like it a lot more than "https://vulkan-tutorial.com/".

I completed the 5 chapters and recently started the "GPU Driven Rendering" section after chapter 5. I've found vkguide.dev far more interesting than the book mentioned in the article, at least for my graphics experience level.

Vkguide deals with the basics, starting from scratch. The book above can be a great read after one completes vkguide, as it shows how to implement some advanced features. I helped review the book and think they should have been more clear that its a book for the people who already know graphics to a high level and want a refresher/info on some new state of the art techniques.

   After some talking with Packt, we agreed on a 9 months writing time: a tight schedule, but we felt we could make it working together with Marco.
   We succedeed, albeit not to the level we wanted, but it was a huge learning experience for both of us (I am pretty sure is the same for Marco).

Sounds about right

Classic packt... How did this blatant spam post even get to the front page?

Vulkan, I suppose.

Haven't read this book but my experience with Packt is generally awful. Material that feels regurgitated from forums wrapped up in a book.

Personally I'd never buy a book from them unless I'd have a personal recommendation from someone I trust.

Reply on news.ycombinator.com