3 ms·
Or you could simply learn the command set for a new micro. Once you are fluent in one, moving to another is no big deal.
by Johnythree 4y ago
Or you could simply learn the command set for a new micro. Once you are fluent in one, moving to another is no big deal.
- adhesive_wombat 4y agoMoving your skills might not be a big deal. Moving an entire mature application might be. Or it might not be. If it's just a simple loop, probably fine. If you have to move a custom assembly RTOS and an entire stack of business logic, maybe it's going to be very painful, project-risky and error-prone. Whereas if it was C, you just need to port drivers (which may already be provided by the manufacturer) and maybe do the RTOS port (if not already done). That could be days to weeks of work. A rewrite in a new assembly language could be months, at the end of which, to a customer, you have the exact same product you had before, except without a proven track record for any single byte of code. Like everything, it depends on the project. This year especially, it's going to be hard enough to stay alive by just shipping anything at all while competitors go to the wall under the double whammy of customer hesitancy and component shortages that can cut an established product of at the knees. And the last thing a company needs then is a long and expensive rewrite blocking shipping. Not only that, if the chips you rewrote for end up on 100 week lead times (and thats not even the longest I've seen this month), you're completely dead in the water.