Darin Fisher nos cuenta cómo diseñamos Google Chrome.
Te damos la bienvenida a Designer vs. Developer, un programa que busca resolver los desafíos que enfrenta la industria a través de la apertura de una conversación entre ellos, lo que proporciona recomendaciones, soluciones a flujos de trabajo, herramientas y debates sobre las dificultades cotidianas.
Mustafa habla con Darin Fisher, vicepresidente de Google Chrome, sobre cómo diseñar un navegador y el décimo aniversario de Chrome.
En este episodio:
Por qué decidimos crear un navegador
Arquitectura de Webkit y multiprocesadores.
El contenido no es Chrome.
Las cuatro "S": simplicidad, velocidad, seguridad y estabilidad.
[null,null,["Última actualización: 2024-08-09 (UTC)"],[[["This episode of Designer Vs.Developer features a conversation with Darin Fisher, VP for Google Chrome, discussing the design and development of the browser."],["The discussion covers the reasons for building a browser, the role of Webkit and multiprocessor architecture, and the importance of content over chrome."],["Key principles of Chrome, known as the four 'S's (simplicity, speed, security, and stability), are explored, as well as the balance of using native and web technologies."],["The conversation also touches upon both the accomplishments and regrets of the past 10 years of Chrome and forecasts what the future holds for the web."],["Listeners can find more episodes of the podcast and video recording via the links provided in the content."]]],["Mustafa and Darin Fisher, VP for Google Chrome, discuss the process of designing a browser. Key topics include the decision to build a browser, Webkit and multiprocessor architecture, and prioritizing content over chrome. The conversation covers the \"four S's\": simplicity, speed, security, and stability. They also look at using native and web technologies, past regrets and accomplishments, and future web predictions.\n"]]