Just because a human-device interface (e.g., touchscreen) is well-suited or optimal for all functionalities of one device doesn't mean that same interface should, or eventually will, propagate to every functionality of other devices. A smartphone is a completely different use case from a vehicle — especially a 6,000 lb. truck hurtling down the road at 70 mph where driver error can cause the deaths of its occupants as well as those in other vehicles, cyclists, or pedestrians.
I don't foresee a touchscreen ever being used for steering, accelerating, or braking, for example. If Ford had done proper (or any?) UX (User Experience) studies and testing, they would have observed the dangers of a driver's attention diverted trying to hit the tiny 'Off' button on the screen for the fan (the only way to actually turn the fan off), or getting the amount of seat heating or cooling they want. The upcoming Sync4a update allowing the dial to control those functions (and possibly adding them to the voice command menu) should solve that problem.
But for touchscreen + knobs vs. only touchscreen, people have, and are certainly entitled to, different preferences. Especially if you're paying $90K for a car (which is a fair amount more than the cost of the priciest smartphone, last time I checked....).