Web Assembly and Go: A look to the future

It’s no secret that I’m resistant to learning Javascript and frontend development. I learned HTML back before CSS was even a thing, and even Javascript came long after I started doing web development. When I look at modern web development I shudder; the ecosystem is so confusing for someone who has been out of touch as long as I have. Node, webpack, yarn, npm, frameworks, UMD, AMD, arghhh! I’ve been watching Web Assembly with anticipation for quite some time, with the hope that it would allow me to write web applications without the typical Javascript build process.

Old Dogs, New Tricks, and Cognitive Bias

For 15 or more years I have told myself that I can’t do frontend web work. I remember seeing a presentation from a co-worker on CSS in 2003 or so, and thinking it was just too complicated. I’ve always been the guy behind the scenes building the services that power the web, but never the one spending any time making them less ugly.

New Tricks - notes as I learn modern front-end development

I promised here that I would document my progress learning frontend development. This isn’t a book-length treatise on the subject, but I do have a few notes about my progress. It’s been a little overwhelming going from zero to having an idea about what I’m doing. Many other people have mentioned it, so I won’t belabor the point – the Javascript ecosystem is huge and confusing. Seriously. I played with several different frameworks with varying results.