JavaScript

`0:24:38`

Some of it was an overhang all the way back from IE5. So IE5 essentially put the whole internet development experience into a deep freeze, because Microsoft won the browser wars in the mid 2000s, and then they basically disbanded their browser development team. 'Cause they're like, "All right, job done. We don't need any more innovation on the internet. Can we just go back to writing Windows forms or something now that we control everything?" And it really wasn't until obviously Firefox kind of kindled a little bit of something. Then Chrome got into the scene and Google got serious about moving to web forward. That you had a kindling of maybe the browser could be better. Maybe the browser wasn't frozen in time in 2005. Maybe the browser could actually evolve like at the development platform that it is. But then what happened was you had a lot of smart people who poured in to the web because the web turned out to be the greatest

`0:25:38`

application development platform of all time. This was where all the money was being made. This was where all the billionaires were being minted. This was where the Facebooks and whatever of the world came to be. So you had all of this brain power applied to the problem of how to work with the web. And there were some very smart people with some, I'm sure very good ideas who did not have programmer happiness as their motivation number one. They had other priorities and those priorities allowed them to discount and even rationalize the complexity they were injecting everywhere. Some of that complexity came from organizational structure. When you have a company like Facebook, for example, that does depend on the web and wanna push it forward, but have sliced the development role job into these tiny little niches. I'm a front-end glob pipeline configurator.

`0:26:41`

Oh yeah, well, I'm a front-end whatever engineer. And suddenly the web developer was no longer one person. It was 15 different roles. That in itself injected a ton of complexity. But I also wanna give it the bold case here, which was that some of that complexity was necessary to get to where we are today. That the complexity was a bridge. It wasn't the destination, but we had to cross that bridge to get to where we are today, where browsers are frankly incredible. The JavaScript you can write in a text file and then serve on a web server for a browser to ingest is amazing. It's actually a really good experience. You don't need any pre-processing. You could just write text files, send them to a browser, and you have an incredible development. — And we should also say that it can kind of be broken, at least the HTML, but even the JavaScript could be a little bit broken and it kind of still works like maybe a half-ass works. But like, just the amount of mess of smelly code that a browser has to deal with is insane.

`0:27:44`

— This is one of the hardest problems in computing today is to parse the entire internet. Because thankfully for us as web developers, but perhaps not so much for the browser developers, every webpage that has ever been created minus the brief period with Flash still runs today. The webpage I did in ninth grade would render on a modern browser today, 30 years later. — That's crazy. — That is completely crazy. When you think about the amount of evolution we've had with the web, how much better we've made it, how many more standards browsers have adopted. It's essentially an Apollo project today to create a new browser, which is why it doesn't happen very often, which is why even companies like Microsoft had to throw into towel and say, "We can't do it." Now I actually don't think that's good for the web. There is the danger of the monoculture if we just get a single browser engine that runs everything, and we are in danger of that. I love the fact that the Ladybird project, for example, is trying to make a new browser engine from scratch.

`0:28:46`

I've supported that project. I would encourage people to look into that. It's really a wonderful — Nice. — thing. It's staffed by a bunch of people who worked on other browser projects in the past. — Truly independent web browser. — We really need that. But I can hold that thought in my head. At the same time, I hold the thought in my head that Google's Chrome was pivotal to the web surviving as the premier web development platform. If it had not been for Google and their entire business depending on a thriving open web, Apple, Microsoft, I think would've been just as fine to see the web go away to disappear into being something that's just served native web applications or native mobile applications and native desktop applications that they could completely control. So I have all sorts of problems with Google, but it's not Chrome. Chrome is a complete gift to web developers everywhere,