korrents

Python

FilterEveryone, all time7 from 7 people
Group All Technologists 2Writers & journalists 1
Who Everyone APAaron Patterson 1 ARAlice Ryhl 1 AHAnders Hejlsberg 1 DHDavid Heinemeier Hansson 1 ESElizabeth Stone 1 JEJulia Evans 1 TPThomas Ptacek 1
When All time Past 1 yearPast 3 yearsPast 5 years
  1. TP

    Thomas Ptacek quoted

    Security engineer; founder of Matasano Security and Latacora

    Our readingThe answer to every significant programming challenge in 2026 is a Python library people overlook for not being in Rust, though that no longer matters.

    Their wordsThe answer to every significant programming challenge in 2026 is a Python library you didn't think to go looking for because it's in Python and not Rust, as if that mattered anymore.

    ↗@tqbf on Xx.com

  2. 7 weeks earlier
  3. JE

    Julia Evans quoted

    Writes jvns.ca, a blog explaining networking

    Our readingSharing code between classes via inheritance in Python tends to produce a bad experience.

    Their wordsI've never had a good experience using inheritance in Python and I don't think I'll try to use it again.

    ↗Some more things about Django I've been enjoyingjvns.ca 1st of 2 in this piece

  4. 2 days earlier
  5. ES

    Elizabeth Stone quoted

    Chief Product and Technology Officer at Netflix

    Our readingWriting lines of Python or C++ may stop being necessary; understanding how code, computer systems and products work will not.

    Their wordsI think there's a difference between being able to write lines of code in a particular language like Python or C++ and understanding how code, computer systems, products work. And I don't think the latter is going away.

    ↗Why Netflix is betting on systems thinkers—not specialists—in the AI era | Elizabeth Stone (CPTO)youtube.com 16th of 20 in this recording

  6. 2 months earlier
  7. AR

    Alice Ryhl quoted

    Software engineer on Google's Android Rust team

    Our readingA language can keep changing without a Python-2-to-3 break, as long as code written under the old and the new rules can be mixed freely in one program.

    Their wordsReally the big idea is to say we want the old code to continue working but we still want to change the language. And so the the difference from other kinds of versions of languages I mean Python 2 version Python 3 comes to mind is that you can totally mix and match in any way you want.

    ↗Why Rust is different, with Alice Ryhlyoutube.com 17th of 23 in this recording

  8. 7 days earlier
  9. AH

    Anders Hejlsberg quoted

    Danish software engineer and Microsoft technical fellow

    Our readingThe language best suited to AI is simply the one the models have seen most of in training, which is why they do so well on JavaScript, TypeScript and Python.

    TypeScriptJavaScript

    Their wordsthat the language that's most suited for AI is the language that AI has seen the most of in its training set, right? And that's why you could argue AI does really well on JavaScript and TypeScript and Python because it's seen an awful lot of it

    ↗TypeScript, C# and Turbo Pascal with Anders Hejlsbergyoutube.com 19th of 26 in this recording

  10. 4 months earlier
  11. AP

    Aaron Patterson quoted

    Ruby and Rails core committer known online as "tenderlove"

    Our readingA tool's speed comes primarily from its design decisions rather than the programming language it is written in.

    design

    Their wordsI suspect it would be possible to write a uv in Python (PyUv?) that approaches the speeds of uv, and in fact much of the blog post goes on to talk about performance improvements that aren't related to Rust.

    ↗Can Bundler Be as Fast as uv?tenderlovemaking.com 2nd of 2 in this piece

  12. 6 months earlier
  13. DH

    David Heinemeier Hansson quoted

    Creator of Ruby on Rails, CTO of 37signals

    Our readingPython is ugly: full of superfluous instructions kept since 1987 for legacy reasons, and its __init__ offends the sensibilities to the core.

    Their wordsPython, to me, I hope I don't offend people too much. I've said this before, it's ugly. And it's ugly in its space, because it's full of superfluous instructions that are necessary for legacy reasons of when Guido made Python back in '87 that are still here in 2025.

    ↗DHH: Future of Programming, AI, Ruby on Rails, Productivity & Parenting | Lex Fridman Podcast #474youtube.com 2nd of 36 in this recording