I've done both over my career (as well as some other stuff.)
While they are very different, if you know C, it's not hard to transition.
Getting a job in the embedded space though is obviously a lot harder than web. There are simply fewer jobs to be had. Doing some personal projects in the space may reawaken your C skills, and help demonstrate competence.
There are two issues: 1) transitioning your skills, and 2) persuading someone to hire/pay you for your new skills.
Transitioning your skills is possible. But embedded is a different world and a different mindset. You a lot less RAM and a smaller CPU. You may have hard deadlines - the right answer can be wrong if it's too late. You may have multiple threads that have to share data and not corrupt it, no matter what order events occur in.
In the worst case, you may not have logging available at all, and you may not have a debugger. (I think the worst I ever had to do was attach a logic analyzer to the address bus, triggered by a specific address, and then use it to look at past memory addresses in order to figure out what path of execution had got me to the point of the crash.)
So, yeah. It's a different world. Learnable, but different.
Getting someone to believe you can do it enough that they're willing to pay you: I don't have great advice there. I spent almost my whole career in embedded. It seems to me that it's easier to get from there into, say, desktop programming, than it is to go the other way. Your best bet might be to emphasize your native development background, and count on there being a shortage of embedded people.
I've done both over my career (as well as some other stuff.)
While they are very different, if you know C, it's not hard to transition.
Getting a job in the embedded space though is obviously a lot harder than web. There are simply fewer jobs to be had. Doing some personal projects in the space may reawaken your C skills, and help demonstrate competence.
Good luck!
You can embed quickjs then write js.
There are two issues: 1) transitioning your skills, and 2) persuading someone to hire/pay you for your new skills.
Transitioning your skills is possible. But embedded is a different world and a different mindset. You a lot less RAM and a smaller CPU. You may have hard deadlines - the right answer can be wrong if it's too late. You may have multiple threads that have to share data and not corrupt it, no matter what order events occur in.
In the worst case, you may not have logging available at all, and you may not have a debugger. (I think the worst I ever had to do was attach a logic analyzer to the address bus, triggered by a specific address, and then use it to look at past memory addresses in order to figure out what path of execution had got me to the point of the crash.)
So, yeah. It's a different world. Learnable, but different.
Getting someone to believe you can do it enough that they're willing to pay you: I don't have great advice there. I spent almost my whole career in embedded. It seems to me that it's easier to get from there into, say, desktop programming, than it is to go the other way. Your best bet might be to emphasize your native development background, and count on there being a shortage of embedded people.