Comparing an RP2350 to the ESP32 family (which is broad) is very much apples to oranges; they each have feature sets which make them ideal for completely different use cases.
I just got ESP32 C6 on a custom board, with micro python it pretty much made all RPi's obsolete for a quarter of price for I2C, GPIO, UART, SPI communication while having WiFi 6 and BLE.
There is no more use case for RPi if I can have ESP32 C6 for $10 - maybe I have to do some soldering on my own.
Then if I need a minicomputer I'd rather go with MinisForum PC that is in price range of RPi and if I need I2C or GPIO I can pair it with ESP32 like as many as I want ESP32 instead of single one like RPi. Then communicate over wireless as much as I want with BLE or WiFi.
Also, could you confirm that the RP2350 consumes 2-3x less power when idling?
If you have the contact details for any certification labs that don't charge extra for radio modules even if you're not using them in your product, that'd be super helpful as well.
It's not a question of "unnecessary". You just don't like it when someone points out that you're making shallow statements and you don't even realize it.
When you frame two MCUs intended for different purposes as competition, you're completely missing why there are so many different useful MCU families in the first place.
If you need a programmable IO state machine (or twelve) then you need the RP2350, period. It's a feature that enables entire domains of functionality that wouldn't otherwise be possible. For example, I'm using it to perform a real-time 12 output MIDI THRU that doesn't tax the CPU cores. Nothing like that exists on the ESP32 family.
