Earlier quoted context omitted.
We have an alternative to the RPi that has an eMMC. It's called a Beaglebone. And everybody bitches that the board is too expensive.
It doesn't have the same ecosystem. Which is half the point of the rpi to start with. But if you vouch for it I'll take a closer look.
Now that's a valid argument. And I would argue it's way more than half.
If you want a one-off mumblesomething and can stay at the Linux OS level (ie. Web application, USB peripherals or maybe the most basic of GPIOs), the RPi ecosystem is going to let you get there much faster even though it will crash and burn occasionally. If that's "good enough" ... Douzou! ... Ganbatte! ... get moving and get going.
I have the same comment about Arduino. It ain't real reliable (but, to be fair, it's quite a bit more reliable than the RPis), but the ecosystem is awesome.
However, when you start asking something like "Gee, how do I send a single address byte over the I2C subsystem?" or "That signal needs a response in 50 nanoseconds, can I make that work?" you will thank the TI folks for producing that 5000 page (not joking or exaggerating) Technical Reference Manual.
One other thing that people who live in the RPi system always overlook in the Beagle ecosystem are the PRU cores. You can do HARD real-time work on those and still live in the Linux world. That's something that the RPi series just simply cannot do no matter how much you hack at them. And it often means the difference between a design which needs an FPGA and one that doesn't.
However, yes, you are going to live in that Technical Reference Manual for the Beagle series. If you're not comfortable doing that, then the Beagle stuff probably isn't for you.
There are really good reasons to use and love RPi's--ease of use is huge. But the whole "It's cheaper" thing just chaps my hide.