正在加载视频...

视频加载失败

Simon Peyton Jones is the co-creator of Haskell (pure functional programming language) and I interviewed him about functional programming, why it matters, and his thoughts on other programming languages. In this episode: • Useful and useless programming languages • Rust vs C • Haskell vs OCaml • Why functional...

128,294 次观看 • 2 个月前 •via X (Twitter)

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

Xavier Leroy (creator of OCaml) is an expert in compilers, formal verification of software and functional programming. This interview should be an approachable resource if you're curious about formal verification of software since I was learning that on the fly during it. In this episode: • OCaml compared with Rust and JavaScript • What is formal verification and how does it work • How languages call each other across boundaries • How to address "almost-correct" LLM code • How type inference works in programming languages Where to watch: • YouTube - • Spotify - • Apple Podcasts - • Transcript - Thank you to the sponsor of this episode for supporting my work: • WorkOS: makes your app Enterprise Ready with easy to use APIs to add SSO, SCIM, RBAC, and more in just a few lines of code, check them out at Chapters: 00:00 - Intro 00:43 - What sets OCaml apart 04:39 - OCaml vs Rust 07:57 - Why is manual memory management more performant 11:21 - Javascript vs OCaml 14:00 - Famous Rob Pike quote 16:05 - Type inference and how it works 22:12 - What is formal verification and how does it work 40:07 - What made multicore support difficult for OCaml 50:17 - How programming languages interface and call each other 57:41 - The danger of almost-correct LLM code 01:05:39 - How LLMs will change programming languages 01:10:26 - Industry vs academia 01:15:05 - Most interesting unsolved problems 01:18:30 - Top book recommendations for engineers 01:21:17 - Advice for his younger self 01:23:31 - Outro

Ryan Peterman

23,942 次观看 • 1 个月前

E133: Sam Blackshear - How Libra Sparked the Move Language and Why Sui Is the Real Endgame! Sam Blackshear is the Co-founder and CTO of MystenLabs.sui , the company behind the Sui, and the Creator of the Move programming language that's revolutionizing smart contract development. Timestamps: 0:00 Introduction 1:54 Partnerships: Jupiter, KAST (old), , Sui, Mantle, Forza! BTC 2:44 The Power of Preparation 5:14 Discipline Behind the Podcast 6:27 Translating Thought Into Code 8:19 Who is Sam Blackshear? 9:27 Choosing What Truly Matters 10:25 Self-Custody with Trezor 11:18 Crypto vs. AI Thinking 12:28 The Power of Support 16:04 From Court Dreams to Reality 17:55 Challenging the Limits of Code 22:52 Chose Learning Over a Job 24:09 The Internship That Changed Everything 27:35 PhD Skills Meet Facebook 29:05 Entering Crypto Through Facebook 32:15 Why Libra Needed Move 33:42 Solving Scarcity in Code 36:37 Bitcoin & Ethereum Mistakes 38:45 Creating a New Language 41:41 Problem-Driven Innovation 44:47 Avoiding Analysis Paralysis 48:11 What is Unstructured Thinking? 50:50 Why Unstructured Thinking Works 53:14 Future of Crypto Protocols 54:21 Why Move is the Best Programming Language 55:00 What is the Sui Network? 56:25 What Makes Sui Different? 57:05 Why is Sui The Best Blockchain? 59:05 Managing Energy Long-Term 1:01:02 Satisfaction Without Closure 1:03:37 90% Love, 10% Grind 1:05:37 Mental State of Surfing 1:06:47 Non-Consensus Beliefs 1:07:34 What is Memory Safety? 1:09:07 What Was the Equifax Hack? 1:10:53 Rethinking Software Safety 1:12:00 Right Dose of Regulation 1:13:00 Biggest Prediction for the Next 24 Months? 1:14:02 Scaling Crypto Developers 1:16:07 Concluding Remarks

MR SHIFT 🦁

164,299 次观看 • 1 年前

For over a year, Jeremy Howard has been in stealth mode. In this exclusive talk, he showcases what he's been working on. He & Jonathan Whitaker show us SolveIt, a new dev environment and programming paradigm. 🤯 Imagine this workflow: - Build a web app & interact with its UI on the same screen as your code. No more flipping to a separate browser. - Use live variables from your REPL directly in prompts to the AI. The AI knows your current state. - Turn any Python function into an AI tool instantly. No no registering tools or MCP. Just write a function in a cell and tell the AI to use it. This is a live, malleable environment that fuses the best ideas from Literate Programming (Knuth), the live-object world of Smalltalk, and the interactive cells of Jupyter. Who is Solveit for? Jeremy's take: SolveIt is best for programmers who are either very new ( 20 years). Why? Because developers in the middle (3-20 years) often have ingrained workflows and can find this different paradigm confronting. New devs are open-minded and build good habits from scratch, while veterans immediately recognize how this approach solves decades-old problems of complexity and state management. My Thoughts It's early days, but it is super cool. You get all the fun of trying a new programming language without learning new syntax (Python), because it will show you new patterns and ways of doing this. If you are wiling to climb the learning curve it is an extremely powerful tool that you can be productive with on real tasks like writing and coding. I'm personally addicted to it for several workflows and am afraid of losing it tbh. How Can You Try It? Just follow Jeremy Howard - he will announce something in the coming weeks or months (I suspect if this post is popular he might do something soon 🤣 ) TIMESTAMPS (00:00:00) - Introduction (00:00:30) - The SolveIt Method vs. "Vibe Coding" (00:04:00) - Investing in Yourself: Long-Term Skill Building (00:07:45) - Software Engineering vs. Short-Term Gains (00:12:15) - The Problem-Solving Loop: Understand, Plan, Implement, Review (00:18:50) - Example: Literate Programming with the Claudette Library (00:24:15) - First Look at the SolveIt Environment (00:28:34) - Demo Start: Building an Eval for Multimodal Models (00:31:16) - Iterative Development: Exploring the iNaturalist API (00:39:15) - Catching Bugs Instantly by Working Step-by-Step (00:43:37) - Prompting LLMs with Structured Outputs (00:51:54) - Demo: Building a Live Web App Inside SolveIt with FastHTML (01:00:24) - Demo: Exploring a Complex API (Cloudflare) (01:08:45) - Creating Custom AI Agent Tools with Zero Boilerplate (01:19:00) - SolveIt Ergonomics: Modes, Secrets, and Keyboard Shortcuts (01:28:30) - The Power of the SolveIt Community (01:30:45) - Who Should Use SolveIt? (01:34:30) - This is Just the Tip of the Iceberg YT Video and links in reply

Hamel Husain

111,916 次观看 • 1 年前

Aidan Gomez (Aidan Gomez) is a computer scientist, co-author of the seminal paper ‘Attention Is All You Need,’ and the CEO of Cohere. In this episode, we discussed his upbringing in the cabin his grandfather built in Codrington, a small town North of Brighton, and the values that were instilled in him through his family. We explored his path from Codrington to his undergraduate studies at the University of Toronto, emailing Geoffrey Hinton, and joining Google Brain where he co-wrote the paper on transformers. We discussed how he met his co-founders Ivan Zhang and Nick Frosst, and his insights on what it means to build a meaningful, successful company in Canada. Aidan shares his conviction about what is at stake — for Canada and for the world at large. This is a conversation about family, values, and what it means to live with conviction. The Other Stuff is hosted by internetVin — filmmaker, entrepreneur, and possibly the most curious man on Earth. Produced by New. The Other Stuff #29 — Aidan Gomez: Empathy and Conviction — Timestamps 00:00:00 Intro 00:03:10 The Malleability of Toronto 00:11:06 Growing Up in Codrington 00:13:50 The Story of Aidan Gomez’s Family 00:27:23 Introduction to the Internet 00:30:39 Values and Work Ethic 00:35:46 University of Toronto’s AI Scene 00:40:48 Emailing Geoffrey Hinton 00:42:16 Google Brain 00:45:15 Dropout: A Simple Way to Prevent Neural Networks from Overfitting 00:49:48 The Beauty of Research 00:54:24 One Model to Rule Them All 00:59:54 Meeting Ivan Zhang and Nick Frosst 01:04:00 The Birth of Cohere 01:06:56 Twitter Influencers and Alex Friedland 01:11:48 Being the CEO 01:12:51 Building for Canada 01:15:01 Three Fundamental Ingredients of Building a Company 01:21:39 Working with the Canadian Government 01:24:39 Reflexivity in Canada 01:36:22 What Is Evil? 01:42:40 The Role of AI in the World

The Other Stuff Podcast

45,297 次观看 • 8 个月前

Why is Rust different than many/most programming languages? Alice Ryhl works on Google's Android Rust team, is a Rust language team advisor, and is a core maintainer of Tokio (the most widely-used async runtime in Rust) Timestamps: 00:00 Intro 04:09 Tokio: an overview 05:11 What Alice likes about Rust 12:48 Rust for TypeScript engineers 13:51 Moving from C++ to Rust 14:34 Memory safety 18:12 Garbage collection tradeoffs 21:46 Ownership, references, and borrowing 26:59 Unsafe in Rust 31:21 Crates and Cargo 35:55 Language design and RFCs 43:02 Building new features 46:30 Editions vs. versions 49:47 Getting paid to work on Rust 51:27 Contributing to Rust 53:03 Rust in the Linux kernel 55:45 AI use cases for Rust 1:01:35 Learning Rust 1:03:54 Book recommendation Brought to you by: • Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. • Sentry – application monitoring software considered “not bad” by millions of developers Three things worth knowing about Rust: 1. Rust was designed to turn implicit failures into compile errors. Where other languages allow you to forget something, Rust makes an omission into a compilation error for things like null checks, uninitialized variables, or error propagation with the ‘?’ character. If you mess something up, it’s almost certain your program will not compile. If it does, at the very least you should see a lint warning. 2. Refactoring in Rust is safe and easy, thanks to the compiler. Alice: “I change a return type or struct field, then just fix the compiler errors until the compiler stops shouting. And then once I’ve done that, I’ve updated every place I need to update.” Rust’s focus on correctness makes refactoring it more straightforward than dynamically-typed languages and Java-style typed ones are to refactor. 3. “Editions” allow Rust to make breaking changes without ‘breaking’ anyone’s code. Rust editions (2015, 2018, 2021, 2024) can be mixed freely across crates. A library on the 2021 edition works seamlessly with a binary on the 2024 edition. This is how Rust evolves syntax (like adding async/await as keywords) without forcing an ecosystem-wide migration. Thanks a lot, Alice for this great discussion! And for your work on Rust.

Gergely Orosz

51,961 次观看 • 3 个月前