That article alone is a large part of the reason that I began my own JavaScript Odyssey 5 years ago. While some of the content in the above article seems redundant since the advent of ES6, it goes a long way to explaining the things about JavaScript that require a mindset shift from “normal” programming languages (if there is such a thing). That lightning talk has been part of the recommended reading list (viewing list? consuming list?) that I give to would-be front end developers, alongside Jonathan Creamer’s “ JavaScript Architecture for the 23rd Century”. If you’ve never seen it before, stop reading now and go watch it. I’ve stoically acknowledged the flaws levelled at the web’s front of house workhorse, including Gary Bernhardt’s tongue-in-cheek “ Wat?” lightning talk that still has me chuckling just thinking about it. That isn’t to say that it is the perfect tool for everything, but it’s served me well over the years. I can even write Android and iOS apps in JavaScript in a number of different ways. Node, which I once naïvely described as a “flash in the pan”, meets the needs of everything I write. My server side language of choice used to be C#, but nowadays it feels clumsy, albeit powerful. Python is fun to code in, but if I have something to automate, I reach for node. JavaScript may be the defacto language of the modern web, but it has long been my language of choice for scripting, too.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |