Stay organized with collections
Save and categorize content based on your preferences.
Welcome to Designer Vs. Developer, a show that tries to solve the
challenges faced in the industry by opening a conversation between
the two, providing take aways, solutions to workflows, tools and
discussions on everyday struggles.
Mustafa speaks to Darin Fisher, VP for Google Chrome, about how
design a browser and the 10 year anniversary of Chrome.
In this episode:
Why we decided to build a browser.
Webkit and multiprocessor architecture.
Content not chrome.
The four 'S's; simplicity, speed, security & stability.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-08-06 UTC."],[[["\u003cp\u003eThis episode of Designer Vs.Developer features a conversation with Darin Fisher, VP for Google Chrome, discussing the design and development of the browser.\u003c/p\u003e\n"],["\u003cp\u003eThe discussion covers the reasons for building a browser, the role of Webkit and multiprocessor architecture, and the importance of content over chrome.\u003c/p\u003e\n"],["\u003cp\u003eKey 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.\u003c/p\u003e\n"],["\u003cp\u003eThe 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.\u003c/p\u003e\n"],["\u003cp\u003eListeners can find more episodes of the podcast and video recording via the links provided in the content.\u003c/p\u003e\n"]]],["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"],null,["# Darin Fisher on how we designed Google Chrome.\n\nWelcome to Designer Vs. Developer, a show that tries to solve the\nchallenges faced in the industry by opening a conversation between\nthe two, providing take aways, solutions to workflows, tools and\ndiscussions on everyday struggles.\n\nMustafa speaks to Darin Fisher, VP for Google Chrome, about how\ndesign a browser and the 10 year anniversary of Chrome.\n\nIn this episode:\n\n- Why we decided to build a browser.\n- Webkit and multiprocessor architecture.\n- Content not chrome.\n- The four 'S's; simplicity, speed, security \\& stability.\n- Using both native and web technologies.\n- Both regrets and accomplishments.\n- What the next 10 years holds for the web.\n\nSubscribe to Designer Vs Developer Podcast via\n[Spotify](https://bit.ly/MustafaOnSpotify)\n[Feedburner](https://goo.gl/USHXv8),\n[iTunes](https://goo.gl/1E9U0G) Or\n[Google Music](https://goo.gl/qCBlST)\n\nWatch [the video recording](https://www.youtube.com/playlist?list=PLNYkxOF6rcIC60856GnLEV5GQXMxc9ByJ). \nWas this page helpful? \nYes \nWhat was the best thing about this page? \nIt helped me complete my goal(s) \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nIt had the information I needed \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nIt had accurate information \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nIt was easy to read \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nSomething else \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nNo \nWhat was the worst thing about this page? \nIt didn't help me complete my goal(s) \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nIt was missing information I needed \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nIt had inaccurate information \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nIt was hard to read \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nSomething else \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new)."]]
