HN recommends it repeatedly as one of the best and most entertaining programming talks, and as the talk that makes the Y combinator click, even for people who do not use Ruby.
Topics › Software Engineering & Languages
The best python, ruby & scripting languages videos, according to Hacker News
115 videos about python, ruby & scripting languages that Hacker News commenters keep pointing each other to, ranked by how many separate months they were recommended. Part of Software Engineering & Languages.
HN treats it as the best starting point for really understanding backprop and neural nets, because Karpathy explains the why with intuition and builds everything in code.
It is HN's standard answer to why Python cannot easily get much faster, and is recommended by people who work on JITs and alternative runtimes.
HN treats it as a top-tier programming talk for learning refactoring and for the wrong-abstraction principle, recommended repeatedly over a decade.
HN commenters repeatedly name it as the best explanation of the JS event loop and the first thing to watch before tackling async code.
HN repeatedly names it the best resource on API design, a staple answer to any 'how do I design an API' question.
It is the go-to funny, accessible explanation of why you should never implement datetime handling yourself, linked in nearly every timezone thread.
Repeatedly urged on people choosing a stack, as a case against heavy SPA complexity and for shared web and native code.
HN repeatedly recommends it as the definitive explanation of why Java evolves cautiously and why compatibility matters in language design.
Frequently recommended as an influential talk on decoupled, testable architecture, though some commenters push back on Martin's TDD advocacy.
A classic recommended to people learning JavaScript, even though some find it dogmatic and dated.
Recurs in threads about RSI, accessibility and voice coding as the go-to demo of a custom spoken command language.
HN treats it as a must-watch classic for writing Pythonic code, though somewhat dated for modern Python.
HN treats it as the definitive, engaging talk on hash table internals and Python dict ordering, and recommends it in tech-talk lists.
HN returns to it repeatedly as the canonical argument for simplicity and against premature abstraction, and several commenters say it changed how they write code.
HN recommends it as a quick, compelling look at what Smalltalk tooling feels like, especially for Ruby programmers.
HN's standard reference when typing speed, ergonomics, or alternative input comes up, for its live demo and the open-source steno ecosystem.
HN commenters return to it as a worldview-shaping talk whose predictions about technology and startup ideas turned out to be prescient.
Regarded as a brilliant live-coding talk that teaches WASM and interpreter writing, with several calling it among the best conference talks they have seen.
Frequently recommended for an experienced game-engine builder's view on why GC pauses are inevitable and why Swift's approach is appealing.
HN calls it one of the best technical talks and the clearest explanation of decorators, generators and context managers.
It is the go-to funny, irreverent critique of notebooks, linked whenever HN debates notebooks versus testable code.
HN recommends it as the fastest way to understand what VisiData can do, since seeing it work is clearer than reading about it.
Repeatedly recommended as the canonical demo of org-mode for literate programming and reproducible research.
HN points to it as a practical way to separate business logic from I/O, which reduces mocking and underlies the functional core, imperative shell idea.
HN recommends it as an entertaining, technically masterful showcase of what Perl 6 can do.
HN treats Cliff Click's talks as an excellent source on JVMs, garbage collection and hardware-assisted Java.
HN cites it in discussions of language evangelism, community dynamics and zealotry, as an accessible account of how a good language can die for non-technical reasons.
Commenters call it a mind-blowing, beautiful talk and cite it among their favorite tech talks.
The default reference in Python performance threads for why removing the GIL is hard.
HN recommends it as an incredible talk whose testing principles apply beyond Ruby.
Strongly recommended in lambda calculus and Y-combinator threads as a mind-expanding half hour that clarifies the ideas.
HN calls it a brilliant, mind-bending introduction to lambda calculus for programmers.
A repeated recommendation for anyone interested in VMs, with Click's talks regarded as unusually informative on JVMs, JITs and the user/kernel boundary.
Recommended as a clear, charismatic starting point for understanding Python concurrency and the GIL.
HN commenters call it one of the best JavaScript courses: rigorous and deep but not boring, and freely available.
HN commenters recommend it as an approachable first step into machine learning for programmers, with an apples-vs-oranges classifier.
HN recommends it for changing minds about whether programmers can be called engineers, and for its take on how waterfall was misread.
The canonical recommendation for understanding the GIL, praised both for its clarity and for how well it explains a deep technical topic.
HN commenters point to it as a real-world case study of moving from React to htmx, especially in threads on boring web development and HTML over the wire.
Cited in threads about Python's rise as a first-hand, entertaining account of why it won in scientific computing.
HN points to it in discussions of programming as a creative craft and of how to write clear software.
HN treats it as a phenomenal demonstration that voice-driven development is viable and as an eye-opener on accessibility-unfriendly coding habits.
HN recommends it as a funny, smart and well-constructed talk on abstraction, duplication and object-oriented design.
It is the go-to reference in debates about whether open source maintainers are owed compensation, and commenters say it is worth watching even for non-Rails developers.
HN commenters recommend it as a simple, direct entry point for beginners who want to learn computer science, not just programming.
HN readers recommend it as a thorough, practical introduction to Postgres fundamentals and optimization for application developers.
HN commenters recommend it as a technically jaw-dropping talk, and it is the standard reference whenever the Night Watch gigapixel images come up.
HN commenters point to it as a primer on modern Rails and as a rebuttal to cloud 'learned helplessness', worth watching even by non-Ruby developers.
Recommended for explaining why Python is hard to optimize and the limits of making it fast.
HN points people to it as a funny and sobering warning about why parsing, validating, or implementing email software is far harder than it looks.
HN commenters point to it as a concise, convincing case for better testing practice short of full formal methods.
HN points Rails developers to it as a real-world case for migrating to Phoenix, backed by numbers.
HN recommends it as a Python talk with lessons that apply to any programming, especially chunking to manage complexity.
HN people recommend it as the best way to understand what async machinery actually does under the covers.
A favorite tech talk on HN for showing that hardware knowledge and generalist skills beat simply adding machines.
HN commenters point Rubyists and the Smalltalk-curious to it as an approachable introduction that shows the Smalltalk system browser and Pharo environment in action.
Recommended as a firsthand history of how Python became the language of scientific computing and ML.
Recommended as a fascinating technical account of the optimizations behind uv's speed.
HN recommends it as the best concise introduction to a practical framework for structuring documentation, the basis of what became Diataxis.
HN recommends it as a fast, accessible way to start learning Python.
HN commenters recommend it as a level-headed, practical take on design patterns without Java-style verbosity.
It is recommended to programmers who want to learn statistics through simulation rather than memorized formulas.
Recommended in Julia threading threads as an insightful, simple explanation of the new task scheduler.
HN commenters share it to show that modern PHP is much better than its reputation.
Recommended as an entertaining look at DHH's views and what the 37signals founders stand for.
Pointed to as the origin story of Hack and a real-world example of OCaml in production.
Recommended as a funny, engaging look at how Perl's quirks create real security vulnerabilities.
Recommended as the author's own explanation of the design and security of magic-wormhole.
HN commenters point newcomers to it as a solid starting point for getting to know Julia.
Linked whenever mixed Python and C++ debugging came up as a neat PTVS feature.
Recommended as a clear, well-paced introduction to Clojure and Lisp ideas like code as data and macros, straight from the language's creator.
HN loves it as a funny, inspiring hobby project and calls it one of the best conference talks ever.
HN commenters cite it as a clear account of the trade-offs between static and dynamic typing and why the industry is swinging back to types.
Recommended as an enjoyable look at the hacker mindset and a thoughtful interview worth rewatching.
Cited for showing how Julia's metaprogramming can beat C and Fortran, along with sound advice not to overuse it.
Recommended as a clear introduction to structured concurrency and as an explanation of subtle asyncio bugs that Trio avoids.
Commenters point to it as the clearest explanation of Python's bytes versus Unicode model and the Unicode sandwich, which finally makes the confusion click.
HN points to it for Guido's own views on the GIL, Python internals and using Copilot, especially in Python-related threads.
Recommended to people who call Rails bloated, as an argument that its size comes from features you eventually need.
HN points to it as the foundational argument for sans-I/O protocol library design.
HN treats it as the model for a compelling developer demo and a benchmark for how simple web development once felt.
HN commenters offer it as a good example of what Perl 6 does well and as a way to get started with the language.
HN suggests it as a free lecture for beginners that eases them into writing readable, reusable code.
HN commenters recommend it as an approachable talk from a respected Python core developer on dataclasses.
HN recommends it as an entertaining talk on how working memory shapes code and how to reduce cognitive load.
HN recommends it for specifics on how Truffle and Graal achieve strong dynamic-language performance.
Julia fans point to it as a concrete example of Julia working for soft real-time robotics, especially when avoiding heap allocation.
HN points to it in beginner-programming-education threads for its distinction between easy to learn and easy to teach.
Offered as a pragmatic, convincing counter to the idea that Perl 6 is too strange to use.
Cited again and again as the concrete case study behind the claim that NASA got a 15,000x speedup moving from Simulink to Julia.
HN points to it as an entertaining, insightful talk about the nature of programming, with memorable lines about programmers and a refreshing slide style.
Recommended as the author's own explanation of xonsh's design and how Python and shell interplay.
Recommended as a practical, approachable build-it-step-by-step introduction to writing compilers, light on theory.
It is the go-to explanation of how CPython's JIT works and why its design is so simple.
HN links it as the historical source for two projects: Hy's first announcement and the earliest recorded Docker talk.
HN cites it in Python testing and code quality threads, including his point that 100% coverage proves little.
HN cites it as a resource for decoupling Rails code and for faster tests.
Pointed to as the original talk by the author of the SIMD-in-JavaScript proposal, whenever SIMD on the web comes up.
HN mostly cites it as evidence that YouTube was built on Python and as background on how it scaled.
Pointed to as a general-purpose interview on Mojo's goals and design from its creator.
HN mentions it for its Perl 6 content, though some note the delivery is less lively than Wall's usual talks.
Cited in APL and Julia threads as a neat way to run APL-style syntax at Julia's speed.
Cited as the definitive public account of Python at massive scale, especially in discussions of monorepos and bank Python.
Cited in PHP compiler and language-implementation discussions as an honest account of the real difficulties of compiling dynamic languages.
Cited in Rails performance and Rack design discussions for Patterson's analysis of stack depth and garbage collection.
Cited in HN debates on testing and clean architecture as a concrete example of keeping domain code separate from Rails so tests run fast.
Pointed to in Java 21 and Loom discussions as the Kotlin lead's authoritative view on coroutines versus virtual threads.
Cited as the authoritative explanation, from the person who added it to OpenJDK, of Optional's narrow intended purpose.
Used as a running joke in discussions of programming by voice.
Cited as the classic, unintentionally hilarious example of early voice recognition failing, and of how dictation used to feel.
It is posted as an in-joke whenever Java GUI layout, Swing or desktop UI toolkits come up.
Cited as a real-world enterprise Java example, especially for JDK upgrades and ZGC results.
Cited in AOT discussions as evidence that Oracle was moving toward AOT in the JDK and as an explanation of the deoptimization concerns.
HN uses it as the primary source for PHP's origins as a templating system for C and for the story behind its inconsistent function design.
Which of these have you already seen?
Connect YouTube and HackerTube AI hides what you've watched and ranks the rest for you.