Like everything else, it depends. What does it depend on? Lots of things - the two that come most immediately to mind are 1) Money, and 2) Function.

If all you're doing is daisy-chaining them for the purpose of splitting a network cable, then it's likely not the best option, although see below. But there are legitimate network-engineering reasons to do it. Switches, unlike hubs, are great traffic-reducers, at least against the core. If you have a small workgroup that, for the most part, accesses a local server in their own dept., then segmenting them off with their own switch might make a whole lot of sense! The bulk of their traffic doesn't have to touch the network core, so why shouldn't they have their own switch?

On the aesthetics and management side, yes, it would be great if everything could home back to the wiring closet, but it could still make sense to put in separate switches, depending on the environment.

The other reason, as I said, was money. What is being suggested here is that new computer locations should be home-run back to the closet. That may work for a company with an IT budget, but smaller companies, for whom this is largely an annoyance, may not be able and/or willing to PAY for the cable work to get done. So what does an IT Consultant do at that point? Throw up his hands and say, "Well, then it can't be done!" Very quickly, you'll discover that they might find another consultant who can do it. Now you've lost a client.

Someone once told me that Money and Politics are two additional layers to the OSI Model. In looking back over my 20+ years in the industry, I find that to be largely true.