| ▲ | sublinear 2 hours ago | |
I'm disappointed there wasn't more written here about Javascript, and more broadly, the web browser. The browser is the platform of the modern era, and Javascript is the strongest example of a programming language being an "authoring tool". Web apps carry the weight of ecommerce, entertainment, social media, etc. The fact that those apps are frequently at the center of political debate and pop culture underscores their broader success far beyond the discussions that only developers understand. Along with the HTML and CSS, the code written for the corporate web is not up to the developers alone. You can't ship anything until it's been through far more review by non-technical stakeholders than the devs using other languages may get away with. Yes the quality can vary, but when it's bad it reveals the dysfunction of the organization in a very public way. There's so much cross-discipline human involvement that the developers are in roles that resemble a bureaucrat more than a programmer. | ||
| ▲ | jdw64 an hour ago | parent [-] | |
I'm the author. Thanks for pointing this out. I completely agree with your premise. JavaScript and the browser represent the quintessential modern authoring platform. I actually wanted to write more about JavaScript, but the problem was that there were fewer cohesive, codified sources to cite than I expected. When writing about this kind of historical narrative, the first issue is always whether there are books you can cite. JS has undergone organic changes along with the turbulent history of the web itself, but there's no clearly organized history of those changes.(To be more precise, it's not that there are none, but rather that the web environment was so fragmented in its early days, and each piece had its own history. Describing all of it would have required too much time) There is Allen Wirfs-Brock and Brendan Eich's 'JavaScript: The First 20 Years,' but it's so lengthy that I couldn't read all of it, so I had to cite only what I had actually read. That's why I ended up cutting a lot of the JS content. I completely agree with your point, but I hope you understand it was a matter of length constraints. | ||