Earlier quoted context omitted.
I challenge you to find a C “boot camp.” In fact doesn’t this point to a gap in the marketplace? Where are my “IOT ALL THE THINGS / 5G / Edge” bootcamps? Where are the “leetcode” challenges that talk about proper sampling rates for an 8-bit A/D converter, or implementing a closed loop PID in a 16-bit architecture? I suspect that that’s what the Grandparent comment is commenting on — there’s so much talking about the…
> I challenge you to find a C “boot camp.” C isn't a language that lends itself to bootcamp-stye learning. With Javascript, you can get something on-screen in a few minutes, and even if you make mistakes, you will normally see something . It's a more forgiving environment. With C, a small error prevents compilation at all, and it's going to be a relatively long time before you're ready to progress past the "printing…
This varies with goals, attitudes, background, bias, etc. Besides, if you know a little C, you can livecode over at glslsandbox or shadertoy and be immediately rewarded.
> It isn't the kind of thing you tackle because you need hirable job skills by the end of the month.
No, not really. This also roughly says "JS doesn't necessarily require lots of experience" which is not much of a plus, as someone already pointed out.