Lars Bak - The Making of a Secure and Robust IoT Development Platform
Curry On!Cited 5× on HN, 2019–2020
talk · advanced · evergreen · 2019–2020 on HN
A Curry On talk by Lars Bak, known for V8 and Dart, on building a secure and robust IoT development platform. It discusses language and VM design choices for small devices.
Referenced mainly for Bak's firsthand account of why the Dart VM never shipped in Chrome and for his IoT language design points.
Up next
13 mo on HNRich Harris - Rethinking reactivity
You Gotta Love Frontend
15 HN recommender · 2019–2026
12 mo on HNLexical Scanning in Go - Rob Pike
GoogleFOSSSydney
13 HN recommender · 2012–2025
12 mo on HNWilliam Byrd on "The Most Beautiful Program Ever Written" [PWL NYC]
PapersWeLove
11 HN recommender · 2017–2026
10 mo on HNCppCon 2016: Jason Turner “Rich Code for Tiny Computers: A Simple Commodore 64 Game in C++17”
CppCon
13 HN recommender · 2016–2024
8 mo on HNClasp: Common Lisp using LLVM and C++ for Molecular Metaprogramming
Google TechTalks
8 HN recommender · 2015–2024
7 mo on HNCompiling C to printable x86, to make an executable research paper
suckerpinch
8 HN recommender · 2018–2023
7 mo on HNBreak Me00 The MoVfuscator Turning mov into a soul crushing RE nightmare Christopher Domas
Adrian Crenshaw
6 HN recommender · 2017–2026
7 mo on HNA Talk Near the Future of Python (a.k.a., Dave live-codes a WebAssembly Interpreter)
David Beazley
7 HN recommender · 2019–2025
7 mo on HNMiguel de Icaza: Swift Godot: Fixing the Multi-million dollar mistake #GodotCon2023
Godot Engine
6 HN recommender · 2023–2026
6 mo on HNCppCon 2017: Matt Godbolt “What Has My Compiler Done for Me Lately? Unbolting the Compiler's Lid”
CppCon
7 HN recommender · 2018–2022
5 mo on HNCo-dfns Live Stream: Compiler Design and Architecture
Aaron Hsu (arcfide)
3 HN recommender · 2018–2025
5 mo on HNEric Bier Demonstrates Cedar
Computer History Museum
3 HN recommender · 2020–2025
5 comments from Hacker News
Lars gave a talk last year and said the intent was to put dart vm in chrome, then the whole mobile thing happen and there was no room for extra stuff in chrome. ▶ this video
They certainly did find a new purpose for Dart outside of it being used in parts of their Ads platform, but Flutter, when is was the chrome experiment called sky, first started out using Javascript. The chrome guys decided to move on and look at several language before going with Dart, Swift may have been an option, if it was opensource at the time. Seems a reason for Dart's failure in the web space was mobile. Lar gave a talk last year about his and Kasper iot startup link he mentions why dart didn't make it into chrome, saying "then the whole mobile shift happen and there was no room for extra stuff in chrome" ▶ this video
> my strong suspicion is the Chrome team killed the idea of shipping a Dart VM in Chrome Yeah in a video last year, Lars said "then the whole mobile shift happen and there was no room for extra stuff in chrome" ▶ this video
And then Lars Bak left, I guess desilusioned with out things turned out for Dart, and is now doing "Dart for IoT" back in Denmark. ▶ this video
minute 21: ▶ this video * Object-oriented * Indentation-based syntax * Clean object model * Blocks with non-local returns * No eval and no runtime reflection * Tracing garbage collection