3 ms·

I heard one time someone make the the distinction between 'big E' Embedded and 'little e' embedded. Little e is classic embedded where you need some computatio

I heard one time someone make the the distinction between 'big E' Embedded and 'little e' embedded. Little e is classic embedded where you need some computation next to inputs. That's generally where you see talk of real time. Then there's big E where you have devices that you aren't really supposed to interact with via a keyboard, screen, or shell prompt for the most part, but have closer to server compute, like storage appliances or high end car head units.

touisteur 3y ago
Pretty much. If you can put x86 on your (big E) embedded thing, you can shortcut so many classic embedded time- and money-pits. Look up VPX for example for rugged PC platforms. But same here, if you can do without (industrialized PC, 'edge' stuff or even COTS server...) you can shave so much cost, in sometimes very competitive markets. Edit: of course this works for low-volume. If you're getting millions of objects out the door, it's another story...
InitialLastName 3y ago
That's a helpful distinction. Another to add to that is that both classes of E(e)mbedded system are designed to be used with a single application (i.e. the user isn't running arbitrary software).