??? 12/23/11 15:08 Read: times |
#185194 - embedded categories vs "ease of programming" Responding to: ???'s previous message |
That obviously depends on the requirements and priorities.
with the "small PCs" such as the Android called 'embedded' there is one HUGE distinction: * a) fixed purpose embedded (what we have known and loved for decades) * b) multi-purpose embedded (anything that can load an 'app') for group a) there will, depending on production volume, be a weighing of develoment cost vs unit production cost, e.g. for a thing that is to be made in multi-millions you may still see some assembler. for group b) the only concern is the 'attitude' of the users. in this thread I must, once more, get on my soapbox, why is everybody haunting Dell and HP to be "energy efficient" when no one haunts Microsoft for forcing PCs to use more energy to have an, even acceptable, performance. Erik |
Topic | Author | Date |
Wirth's law Does it apply to embedded systems? | 01/01/70 00:00 | |
Same for embedded | 01/01/70 00:00 | |
It's possible, but ... | 01/01/70 00:00 | |
That obviously depends on priorities and focus | 01/01/70 00:00 | |
Still Java | 01/01/70 00:00 | |
embedded categories vs "ease of programming" | 01/01/70 00:00 | |
No question about it, but doesn't that also contain risks? | 01/01/70 00:00 | |
Speed, quality, cost | 01/01/70 00:00 | |
I think they have to choose which one of the three ... | 01/01/70 00:00 | |
Its time for me to get on my soapbox | 01/01/70 00:00 | |
passing knowledge | 01/01/70 00:00 | |
Software Bloat - or Feature Bloat? | 01/01/70 00:00 |