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 Slide

  2. Armin @mitsuhiko Ronacher

    View Slide

  3. View Slide

  4. what can I tell you?

    View Slide

  5. let me tell you about a future

    View Slide

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

    View Slide

  7. and the future
    will be different

    View Slide

  8. View Slide

  9. where are we now?

    View Slide

  10. and how we came here

    View Slide

  11. people love python

    View Slide

  12. stackoverflow most loved

    View Slide

  13. stackoverflow most wanted

    View Slide

  14. but what about the future?

    View Slide

  15. let's make a detour

    View Slide

  16. View Slide

  17. View Slide

  18. View Slide

  19. rust is hard

    View Slide

  20. rust is complex

    View Slide

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

    View Slide

  22. the packaging story

    View Slide

  23. the distribution story

    View Slide

  24. reliability and trust

    View Slide

  25. zero cost abstractions

    View Slide

  26. a clear backwards
    compatibility story

    View Slide

  27. the community

    View Slide

  28. rust tells us a story

    View Slide

  29. rust's values are
    transparent

    View Slide

  30. […] 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 Slide

  31. it's okay to create
    something complex

    View Slide

  32. if using it is easy

    View Slide

  33. our approach so far

    View Slide

  34. we succeed despite
    our process

    View Slide

  35. the wider community
    vs
    the core developers

    View Slide

  36. the packaging story

    View Slide

  37. distribution

    View Slide

  38. typing

    View Slide

  39. why?

    View Slide

  40. we're afraid
    of complexity

    View Slide

  41. we work against
    each other

    View Slide

  42. how do we prevent this
    from happening?

    View Slide

  43. we need to work
    together

    View Slide

  44. not to be afraid

    View Slide

  45. we need a vision

    View Slide

  46. and that vision could
    be bold

    View Slide

  47. working groups?

    View Slide

  48. pay developers?

    View Slide

  49. embrace black and lint
    name violations?

    View Slide

  50. TypeScript for Python?

    View Slide

  51. py_modules and
    package.json?

    View Slide

  52. non indexable UTF-8
    strings?

    View Slide

  53. phase out cabi for ffi?

    View Slide

  54. load wasm modules?

    View Slide

  55. strip stdlib down?

    View Slide

  56. multi version import
    system?

    View Slide

  57. simplify object model?

    View Slide

  58. cross compile to wasm?

    View Slide

  59. 0

    View Slide

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

    View Slide