Skip to content
HomeVideos
AllLongsCategoriesPlaylists
BooksBlogsPodcasts
HistoryListsWatch laterLiked videosFollowing

The videos, books, blogs and podcasts Hacker News keeps recommending, all in one place.

VideosBooksBlogsPodcastsAboutPrivacySettings

Data from Hacker News, HackerTube, HackerBooks, HackerBlogs and Open Library. Credits · Not affiliated with Y Combinator.

HomeVideosBooksBlogsPodcasts
Ctrl K

    Building a Better Web Browser - James Mickens - Harvard CS Colloquium 2015

    Paul Irish

    4 HN recommenders · recommended in 8 months, 2017–2023

    YouTube

    1:07:46 · 29K views · Dec 11, 2015

    James Mickens's 2015 Harvard colloquium argues that browsers are bloated and insecure because feature races trump clean interface design. He presents a cleaner, more secure browser architecture (Atlantis) with a much smaller API surface.

    HN cites it whenever people discuss rebuilding the web platform or what a better browser architecture could look like.

    Software Engineering & LanguagesWeb developmentSoftware architecture & designSecurity & hacking
    1. 33:52
      Nordic.js 2014 • Douglas Crockford - The Better PartsNordic.js73K views • 12 years ago
    2. 45:05
      Servo Architecture: Safety and Performancelinux conf au 2017 - Hobart, Australia12K views • 9 years ago
    3. 44:36
      Hacker Way: Rethinking Web App Development at FacebookMeta Developers900K views • 12 years ago
    4. 52:23
      Nicholas Zakas: Scalable JavaScript Application ArchitectureYUI Library68K views • 15 years ago
    5. 43:33
      Andy Bell – Be the browser’s mentor, not its micromanagerHey! Presents23K views • 4 years ago
    6. 11:46
      James Mickens on JavaScripttablet reader49K views • 11 years ago
    7. 27:42
      Mark DiMarco: User Interface Algorithms [JSConf2014]JSConf52K views • 12 years ago
    8. 1:06:39
      Ruby Midwest 2011 - Keynote: Architecture the Lost Years by Robert MartinConfreaks172K views • 14 years ago
    9. 29:51
      Keynote: What is a Component (and Why)? - Luke Wagner, Distinguished Engineer, FastlyThe Linux Foundation6.9K views • 3 years ago
    10. 35:32
      Cheng Lou - On the Spectrum of Abstraction at react-europe 2016ReactEurope63K views • 10 years ago
    11. 27:21
      Daniel Henry Holmes Ingalls Jr.: The Live Web. Drag 'n drop in the cloudJSConf8.3K views • 13 years ago
    12. 2:59:19
      Brendan Eich: JavaScript, Firefox, Mozilla, and Brave | Lex Fridman Podcast #160Lex Fridman878K views • 5 years ago
    13. 29:32
      Pete Hunt: React: Rethinking best practices -- JSConf EUJSConf548K views • 13 years ago
    14. 20:21
      Humans can't read URLs. How can we fix it? - HTTP 203Chrome for Developers59K views • 6 years ago
    15. 51:22
      USENIX Security '18-Q: Why Do Keynote Speakers Keep Suggesting That Improving Security Is Possible?USENIX204K views • 8 years ago
    16. 43:29
      Servo: Building a Parallel BrowserLinux.conf.au 2015 -- Auckland, New Zealand23K views • 11 years ago
    17. 1:03:31
      Brian Goetz - Stewardship: the Sobering PartsClojureTV39K views • 11 years ago
    18. 54:20
      Bret Victor - Inventing on PrincipleRui Oliveira339K views • 14 years ago
    19. 14:34
      Blockchains Are a Bad Idea (James Mickens)HBS Digital Initiative68K views • 8 years ago
    20. 1:03:48
      JavaScript: The Good PartsGoogle TechTalks589K views • 17 years ago

    8 comments from Hacker News

    1. @zeronameSep 2018· in “Show HN: Thi.ng/hdom – S-expression based, pure ES6 UI/VDOM components”

      > Doesn't every freaking mainstream technology suck? I regularly come across rants from significant developers regarding this issue. There probably is no way to prevent this from happening. Because worse is unfortunately better. Web technology is fundamentally different in that you have a big standards body regulating everything from layout down to color blending, then leave it up to multiple vendors to implement all that stuff at great expense and with long delay. Worse, it's all shoehorned on top of some "document model" than was never designed with applications in mind. It's a waste. To see what a better platform could look like, consider this: [LINK] this video The key here is reducing surface area. It's entirely possible that WASM will bring us closer to that, but the web developers of today probably won't like that. > I regularly and seriously consider to leave software development because of this (as I'm really suffering) but then I remember how much power it gives me despite the horrible faults it has. I don't know what you do, but I find web development to be significantly more frustrating than other areas. That doesn't mean there isn't frustration elsewhere though and it's definitely part of the job.

      RecommendsView on HN
    2. @maxharrisAug 2020· in “‘CSS X’”

      I used to get really angry at CSS because of all of the things that made it a bad fit with component-based systems like React. It made me so unhappy that I worked full-time for about nine months on this project, which was a React-like component system that rendered to canvas. [LINK] I got pretty far! But I gave up working on it when I realized that I was going to be pushing this boulder uphill for years. So what changed? I picked up Swift and SwiftUI, and it turns out that some of the ideas that I had were the same ones the SwiftUI folks went with! For all the web has given us, I think its APIs are holding us back now. I still think we need something open and decentralized that competes with the App store and Play store, but one that offers apps that use basically the same APIs and technology that the native apps use. Last thing: I know Apple cripples browsers on their platforms. I've run into all those issues personally in my work! That still doesn't make the web the right thing. Here's James Mickens telling us how to fix the browser's busted architecture: this video

      RecommendsView on HN
    3. @VarFarYonderSep 2017· in “W3C abandons consensus, standardizes DRM, EFF resigns”

      James Mickens gave an interesting talk on what we could do to build a better browser: this video I'm hoping that WebAssembly might be a route towards allowing something like this to happen. If an alternative to HTML/CSS/JS could be developed in WebAssembly, then we could have a situation where HTML has competition, rather than being the only way to build a website. And browsers can become simpler as the rendering duties are moved out of the browser and to the website itself.

      RecommendsView on HN
    4. @foobiekrJul 2020· in “Why is CSS the way it is?”

      James Mickens has a talk about doing exactly this [1]. It's a perfectly sensible proposal and the talk is well worth the time to listen to. He makes a solid argument for why this should be done. Problem: in reality, it is unworkable and will never happen, and even if it did the actual level of "development" that we actually see in the real world would end up in a situation just as bad as the situation we are in now. [1] this video

      RecommendsView on HN
    5. @maxharrisNov 2018· in “Ask HN: What will future browser be like?”

      James Mickens at Microsoft Research presents Atlantis, which I definitely think this still the most forward-looking browser architecture out there: this video Ideas from this effort are going to be trickling into browsers for years to come. For example, if you squint a bit, you might see a conceptual resemblance between the Syphon interpreter in Atlantis and WASM in shipping browsers.

      RecommendsView on HN