Regarding the chance of a cafe owner receiving a subpoena, it won't happen, because the cafe owners don't provide the service. Cafe owners pay a fee to an internet service provider. The ISP places a wireless router in the cafe. The cafe then either sells access, or allows free access. So, any subpoena will be served on the ISP.
Offering free wireless access can be either good or bad for a cafe, depending on the business climate. If the cafe enjoys good business, then it is probably better off charging for access. This is because wireless users tend to spend less over the time they sit in the cafe. If business in the cafe is slow, then offering free access is a way to bring in a little extra income, while also creating an appearance of popularity (an old trick in the restaurant business.)
Actually, what I've done is present the book the way it reads. Also, a complete explanation of those concepts doesn't necessarily make it a bad book. That's why a reviewer will comment that the explanation of those areas "falls short." Given the books wide intended audience, I wasn't sure whether it made sense to rip the book for those ommissions. People can still use the book to learn the basics of C++. I think the book is probably most useful to C programmers who want to learn C++, but again I don't want to make that an unequivical statement because people with other backgrounds may benefit from the book. Its a big world out there, with lots of different people. Who are we to be absolute arbiters of what people should read?
They didn't editing any of my writing, other than changing the periods to parenthesis, such as "1." to "1)", etc. When they did that, they inadvertently added the additional "4)". Thanks for your feedback.
Hey Timothy,
The review I submitted didn't have that extra "4)". My guess is the first paragraph got mangled when you converted it from text to html. The review I submitted used periods, not parentheses. I appreciate having the periods changed to parentheses (more readable,) but the repeating "4)" is a real drag. Hey, a misspelled word is embarassing enough. Thanks.
Have you ever thought about looking at the book the next time you visit your local bookstore? Then you can look at the diagram. Maybe I think the book is interesting enough to entice people to look at it, by making reference to a cute diagram on the software development life cycle. Gee, you guys want everything spoon fed to you!
There are two types of source code errors in the book: 1. Intentional errors that the author explains. 2. Unintentional errors that are not explained. The second type of error can be very frustrating for novice users; this is the type of error I find unacceptable.
Slashdot Mirror
Regarding the chance of a cafe owner receiving a subpoena, it won't happen, because the cafe owners don't provide the service. Cafe owners pay a fee to an internet service provider. The ISP places a wireless router in the cafe. The cafe then either sells access, or allows free access. So, any subpoena will be served on the ISP.
Offering free wireless access can be either good or bad for a cafe, depending on the business climate. If the cafe enjoys good business, then it is probably better off charging for access. This is because wireless users tend to spend less over the time they sit in the cafe. If business in the cafe is slow, then offering free access is a way to bring in a little extra income, while also creating an appearance of popularity (an old trick in the restaurant business.)
Actually, what I've done is present the book the way it reads. Also, a complete explanation of those concepts doesn't necessarily make it a bad book. That's why a reviewer will comment that the explanation of those areas "falls short." Given the books wide intended audience, I wasn't sure whether it made sense to rip the book for those ommissions. People can still use the book to learn the basics of C++. I think the book is probably most useful to C programmers who want to learn C++, but again I don't want to make that an unequivical statement because people with other backgrounds may benefit from the book. Its a big world out there, with lots of different people. Who are we to be absolute arbiters of what people should read?
An explanation can do a "good" job, but not a complete job (i.e. "It falls short.") Most people don't have a problem understanding this concept.
Yeah, I agree the first sentence is bad. Thanks for the feedback.
They didn't editing any of my writing, other than changing the periods to parenthesis, such as "1." to "1)", etc. When they did that, they inadvertently added the additional "4)". Thanks for your feedback.
O'Reilly gave me the book to review, because I thought it looked interesting. I haven't received any other compensation, other than the free book.
Hey Timothy, The review I submitted didn't have that extra "4)". My guess is the first paragraph got mangled when you converted it from text to html. The review I submitted used periods, not parentheses. I appreciate having the periods changed to parentheses (more readable,) but the repeating "4)" is a real drag. Hey, a misspelled word is embarassing enough. Thanks.
Have you ever thought about looking at the book the next time you visit your local bookstore? Then you can look at the diagram. Maybe I think the book is interesting enough to entice people to look at it, by making reference to a cute diagram on the software development life cycle. Gee, you guys want everything spoon fed to you!
There are two types of source code errors in the book: 1. Intentional errors that the author explains. 2. Unintentional errors that are not explained. The second type of error can be very frustrating for novice users; this is the type of error I find unacceptable.
Can you explain how to make money from an "affiliate link?" I haven't made any money from this review, but I'm certainly open to suggestions ;)
Hmmm... whoever edited my review mangled that part of it. The one I submitted didn't have a fourth "4)". That's annoying.