3 ms·

More of a general observation than something directed at you in particular: back in the 2004-2005 timeframe, I saw a cohort of developers thinned out by the jum

by ern 8y ago

More of a general observation than something directed at you in particular: back in the 2004-2005 timeframe, I saw a cohort of developers thinned out by the jump from ASP/VB6 to ASP.NET/C#. They made similar arguments (mature framework, lots of documentation, de facto standards, also lots of FUD). Microsoft appeased them with VB.NET,and made soothing noises about them not being replaced. I suspect that the move to the current JavaScript-heavy ecosystem killed more careers. WASM represents another potential shift. If one wants to survive, one has to prepare for these shifts, and not emotionally invest in a particular tech stack.

Wintamute 8y ago
> If one wants to survive, one has to prepare for these shifts, and not emotionally invest in a particular tech stack. Couldn't agree more. I'm already a refugee twice over from previous tech stacks, and keep on enjoying where I end up! That said, I've always stayed within the realm of creative, visual and UI development. I'm just floating the idea that transitioning into a web/UI development stack from a backend or systems programming background might not be all that easy, whether ones favourite programming language now compiles to WASM or not.