5 ms·
The "windows style" of monolithic development where the more checklists on the feature list, the better the product must be, only works in a monopoly, which is
by VLM 14y ago
The "windows style" of monolithic development where the more checklists on the feature list, the better the product must be, only works in a monopoly, which is the situation on the desktop, more or less in consumer goods, but not even close in embedded. The problem is now you've got a CPU with 7 UARTS and the 5th one has a hardware bug that only affects one user in the world. Debugging doesn't scale very well.
The same cost argument applies to unused blocks. If you can save 5 cents per device by not using FPGAs then you'll save 10 cents by selecting a minimal old fashioned controller, but that blocks you into a corner.
Another issue is the infinite variety of peripherals. An infinite number of an infinite variety of peripherals rapidly becomes very expensive compared to "here's 1M identical gates to implement whatever you want"
Its like the extremely early history of computing, will reconfigurable and infinitely reprogramable von-neumann processors ever beat hard wired logic "computers" based on physical plugboards and unit record equipment in the marketplace? Well, yeah that's exactly how it turned out.
"unless the designer gets something very compelling from that flexibility" Yes almost infinitely fast hardware accelerated peripherals and the devs choice of cpu core. If your app has no inner loop that requires optimization (perhaps an automobile transmission, or a tamagotchi) or WRT core selection then in the style of "only got a hammer then the whole world looks like a nail" in those situations there would be little advantage.