It has a bad reputation but judging books by their cover is increasingly useful.
i judge almost everything i consume by their cover/packaging
The back cover of C++: The Language raises questions not answered by front cover
51–55 of 55 posts
Re: The back cover of C++: The Language raises questions not answered by front cover
#52Plot twist: the publisher just looked into the future. I’m currently building an EBNF parser for my project, C³ (C cubed), which allows you to define arbitrary grammar at the very beginning of a file to seamlessly mix strings and syntax from Python, JS, or any custom DSL. While C++ was just a simple iteration, C³ aims to be a paradigm shift. If you see JavaScript DOM manipulation code on a C++ book cover, it’s not a…
The repo readme doesn't mention anything like that. It looks an ambitious project. I think the AI-style tone in the readme, or things like 'paradigm shift' and that it would be an online service (for a language? huh?) may be contributing to the downvotes you're getting.
[flagged]
Re: The back cover of C++: The Language raises questions not answered by front cover
#53I wonder if the book itself is actually any good. My understanding is that authors often have little or not control over the covers chosen by their publishers. It's at least possible that the book itself is excellent, but I'm not going to spend $90+ on a hardcover copy to find out.
[deleted]
Re: The back cover of C++: The Language raises questions not answered by front cover
#54Its crazy to me how little effort publishers put into the basic parts of their job sometimes. Its even funnier that raymond chen of all people is the one calling this out
Also crazy to me: how some people can't bother to capitalize names or use punctuation.
Considering the book's title is almost identical to Bjarne Stroustrup's book, it smells like an attempt to profit by confusing buyers.
Re: The back cover of C++: The Language raises questions not answered by front cover
#55It reminds me of an incident involving an old colleague of mine at some kind of graduate recruitment fair thing. He walked past a stand which was trying to hire engineers which had some code on the wall when the following exchange happened: Recruiter: Hey there! Do you know what this is? Colleague: Err, … It *looks* like some sort of network protocol Recruiter: No, it’s *COMPUTER CODE*
Once a recruiter asked me if I knew react, after answering yes they asked me if I knew javascript.