Upgrade to Pro — share decks privately, control downloads, hide ads and more …

A Future Python

A Future Python

A presentation about how Python could be.

Armin Ronacher

October 05, 2018
Tweet

More Decks by Armin Ronacher

Other Decks in Programming

Transcript

  1. a Python future

    View full-size slide

  2. Armin @mitsuhiko Ronacher

    View full-size slide

  3. what can I tell you?

    View full-size slide

  4. let me tell you about a future

    View full-size slide

  5. i can't tell you what the future
    will be, but here is what I
    wish it to become

    View full-size slide

  6. and the future
    will be different

    View full-size slide

  7. where are we now?

    View full-size slide

  8. and how we came here

    View full-size slide

  9. people love python

    View full-size slide

  10. stackoverflow most loved

    View full-size slide

  11. stackoverflow most wanted

    View full-size slide

  12. but what about the future?

    View full-size slide

  13. let's make a detour

    View full-size slide

  14. rust is hard

    View full-size slide

  15. rust is complex

    View full-size slide

  16. so why do people love Rust?
    (and what does it mean for Python?)

    View full-size slide

  17. the packaging story

    View full-size slide

  18. the distribution story

    View full-size slide

  19. reliability and trust

    View full-size slide

  20. zero cost abstractions

    View full-size slide

  21. a clear backwards
    compatibility story

    View full-size slide

  22. the community

    View full-size slide

  23. rust tells us a story

    View full-size slide

  24. rust's values are
    transparent

    View full-size slide

  25. […] the Rust programming language is
    fundamentally about empowerment:
    no matter what kind of code you are
    writing now, Rust empowers you to
    reach farther, to program with
    confidence in a wider variety of
    domains than you did before.

    View full-size slide

  26. it's okay to create
    something complex

    View full-size slide

  27. if using it is easy

    View full-size slide

  28. our approach so far

    View full-size slide

  29. we succeed despite
    our process

    View full-size slide

  30. the wider community
    vs
    the core developers

    View full-size slide

  31. the packaging story

    View full-size slide

  32. distribution

    View full-size slide

  33. we're afraid
    of complexity

    View full-size slide

  34. we work against
    each other

    View full-size slide

  35. how do we prevent this
    from happening?

    View full-size slide

  36. we need to work
    together

    View full-size slide

  37. not to be afraid

    View full-size slide

  38. we need a vision

    View full-size slide

  39. and that vision could
    be bold

    View full-size slide

  40. working groups?

    View full-size slide

  41. pay developers?

    View full-size slide

  42. embrace black and lint
    name violations?

    View full-size slide

  43. TypeScript for Python?

    View full-size slide

  44. py_modules and
    package.json?

    View full-size slide

  45. non indexable UTF-8
    strings?

    View full-size slide

  46. phase out cabi for ffi?

    View full-size slide

  47. load wasm modules?

    View full-size slide

  48. strip stdlib down?

    View full-size slide

  49. multi version import
    system?

    View full-size slide

  50. simplify object model?

    View full-size slide

  51. cross compile to wasm?

    View full-size slide

  52. Q&A
    lucumr.pocoo.org / @mitsuhiko

    View full-size slide