Google JavaScript with Malte Ubl
Software Engineering Daily
Channel
Interviewed Person
Malte Ubl
Description
Visit our website https://softwareengineeringdaily.com Google Search is a highly interactive JavaScript application. As you enter a query, results are being automatically suggested to you before you even finish typing. When you press enter, some of your search results may be widgets that represent the weather, the price of a stock, a recipe for green bean soup, or a language translation for a phrase. These complex frontend components are loading dynamically–the Google Search application cannot prefetch every single possible widget that you might ask for–but the results do load very quickly. Google has many other examples of advanced JavaScript engineering. The company is mostly known for backend engineering inventions like MapReduce, TensorFlow, Dremel, and Spanner. To turn these backend tools into user facing products, Google develops its own JavaScript frameworks and infrastructure to deliver information from the backend to the frontend. “Backend” and “frontend” are not precise terms. At Google, there are so many layers of infrastructure between a user and the data center. If you are an engineer working on a service at Google, you probably have several “frontends” and “backends” on either side of you. Malte Ubl is a senior staff engineer at Google. He’s heavily involved in Google’s JavaScript infrastructure, and has written about managing large JavaScript applications in detail. He also works on AMP, an open-source project for delivering web pages in a fast, performant format. He joins the show to describe Google’s history with JavaScript frameworks, the process of building frontends and middleware to deliver JavaScript applications, and the engineering behind AMP. There are criticisms of AMP, but some of them misunderstand how the AMP technology actually works. AMP allows pages to be cached, prefetched, and served to a user more quickly. AMP does not necessarily centralize pages around being served from Google Search. A good example of AMP speeding up pages outside of Google is reddit . We recently launched a new podcast: Fintech Daily! Fintech Daily is about payments, cryptocurrencies, trading, and the intersection between finance and technology. You can find it on fintechdaily.co or Apple and Google podcasts. We are looking for other hosts who want to participate. If you are interested in becoming a host, send us an email: host@fintechdaily.co The post Google JavaScript with Malte Ubl appeared first on Software Engineering Daily .
Transcript
Google search is a highly interactive JavaScript application as you enter a query results are being automatically suggested to you before you even finish typing when you press enter some of your search results may be widgets that represent the weather or the price of a stock or a recipe for green bean soup or a language translation for a phrase these complex front-end components are loading dynamically the Google Search application is not prefetching every
single possible widget that you might ask for it's not pretty fetching the weather widget and the price of a stock widget and the currency conversion widget all of these things are a little bit expensive and they would slow down the page if Google were to prefetch the JavaScript for all of these different components but the results do load very quickly if you search for a currency conversion Google loads the results of
that currency conversion widget quite quickly so you know that Google is doing some advanced JavaScript engineering to deliver you the code for that currency conversion widget very quickly and Google has many other examples of advanced JavaScript programming the company is mostly known for back end engineering inventions like MapReduce and tensor flow and Dremel and spanner and to turn these back-end tools into user facing products Google develops its
own JavaScript frameworks and infrastructure to deliver information from the back end to the front-end back-end and front-end are terms that are not very precise a back-end is a back-end only relative to a front-end and at Google there are so many layers of infrastructure between a user and the data center that if you're an engineer
working on a service at Google you probably have several front ends on one side of you and several backends on either side of you it's a multi-layered multi-tiered sure Malta Ubel is a senior staff engineer at Google and he's heavily involved in Google's JavaScript infrastructure he has written about managing large JavaScript applications in detail and he also works on amp which is an open source project for delivering
webpages in a fast performant format malta joins the show to describe Google's history with JavaScript frameworks the process of building front ends and middleware to deliver JavaScript applications and the engineering behind the amp project there are criticisms of amp but some of them misunderstand how the amp technology actually works amp allows pages to be cached and pre fetched and served to a
user more quickly in the case of Google search when you search and you get some results that are amp pages accelerated mobile pages all that's going on is that the page is being pre fetched so when you click on the page it's going to load instantly because the page is actually already loaded on your phone and the reason it can do that is because amp pages are conforming to a specific
format that is easier to cash and prefetch and have predictable performance characteristics so the criticisms are often that amp centralizes pages around being served from Google search or some other confused accusation towards Google like that but amp does not necessarily centralize pages around being served from Google search another good example
Video Details
- Duration
- 1:05:31
- Published
- December 17, 2018
- Channel
- Software Engineering Daily
- Language
- ENGLISH
- Views
- 473
- Likes
- 6
Related Videos

Next js 15 with Jimmy Lai and Tim Neutkens
Software Engineering Daily
Interviewed: Tim Neutkens

eCommerce Tech Trends 2021: Tim Neutkens
Catch the Tornado
Interviewed: Tim Neutkens

Socket.IO and Realtime Applications with Guillermo Rauch
Software Engineering Daily
Interviewed: Guillermo Rauch

Static to Dynamic and Back Again: Future of Frontend
Sentry
Interviewed: Guillermo Rauch