hi, great question. we have to start with something and while the RP2350 is not going to beat a 600mhz m7 it is much less expensive, fast to get, has lots of nifty support libraries available, and will definitely do better than the teensy 3.2 which many folks loved so much (and was discontinued during the chip shortage). this is also a great time to add things that we always wanted in the teensy: SWD debug, built in 8 MB storage, lipoly battery charging, open source bootloader, open hardware design. stuff like CAN is supported via PIO (https://github.com/KevinOConnor/can2040), as is USB host on any two adjacent pins. M33 has FPU, and the dormant/RTC mode for the RP2350 is 10uA (see https://www.tomshardware.com/raspberry-pi/raspberry-pi-pico/...). other 'teensiriffic' things like NeoPixel DMA support is well supported by PIO on the RP2350. as well as I2S audio.
as for the bootloader chip: we don't want to trade one closed-single-source component for another. if we're going to make something it should be fully open source as much as we can!
finally, for teensyduino libraries that you love: there's no reason they cant be ported (we did an audio port for the samd51) - which specific library are you referring to?
I have projects that can equally use either a Teensy or a few different Feather boards, and frankly the Feather boards are always the prefferred option beacause:
* assymetrical footprint - the assymmetrical dip footprint means the board has polarity protection. I have hat/receiver boards with zig-zag stagger dip rows that work as free componentless sockets to receive a feather board with pins soldered. The Feather versions are far more convenient and safe since they can't be plugged in any way but the correct way.
* The Feather standard being a standard - ecosystem of compatible boards with compatible footprint & pinout at least for main functions.
* lipo charging circuit and jst plug, the automatic ups functionality, usb charging, removable/replaceable via standard plug
* off-board power on/off - I very much make use of the trick Feather has where a hat can turn the mcu board on/off without being the source of power to the mcu board.
* Perhaps a small detail but Feathers with sd card slots have the card sense pin wired up to a gpio pin while the teensy's do not. On Feather I can have a hardware interrupt fire when a card is inserted or ejected, and I can't do that on Teensy.
* keeping all parts on the top surface - there are other mcu dev boards with some similar functions but they are less convenient to use as a module in a project since they may have buttons, jst plug, sd card slot, or other stuff on both sides of the board, which makes them inaccessible when mounted onto some other pcb.
Teensy has a few points in their favor too but I really value these facets of most Feather boards.
I think this is a bit tone-deaf the reason why the teensy is so desirable is because of its raw power in such a neat package. The RP2350 is great but if I wanted that I would just purchase it rather than the Freensy
Right, but you're not really competing on processor speed. You're competing on maturity of peripherals where the RP doesn't really match up PIO or not.
Edit: I see you're comparing it to the 3.2 but I suspect most folks are going to be comparing your offering to the 4.x.
Thanks for the answer. I know many are scared off by the closed bootloader of the teensy (though I feel it's a fair thing to do). The lack of on-chip debugging is another shortcoming the Teensys have.
I've been working on an audio project recently, and the the ease of use and feature set that TeensyAudio has is incredible.
Teensy 4 does currently fill a pretty unique niche in terms of processing power though. There isn't much like it outside of professional eval boards.