kobzol

6 ms·

1. 31.▲
   by kobzol 3y ago

   Yep. This is actually one of the most useful features for me, autocompletion and Go to definition. I don't actually even use an actual type checker in most projects, unless they are more production-critical.
2. 32.▲
   by kobzol 3y ago

   I will someday :) But unless there's Tensorflow and about a gazzillion other packages in Nim, it's not easy to switch.
3. 33.▲
   by kobzol 3y ago

   Sorry :) Not that kind of "like Rust".
4. 34.▲
   by kobzol 3y ago

   This probably plays a role. But for me, I started with C#, but still after I later used Python, I wasn't using types at all. Only after I got more experience in programming, and especially was exposed to Rust, then I started to write P
5. 35.▲
   by kobzol 3y ago

   Someone else also mentioned this on Reddit, good point.
6. 36.▲
   by kobzol 3y ago

   I didn't know about that, thanks. I kind of agree with a sibling comment that in most cases you don't want to expose an indexer if the fields are named, but it might be useful sometimes.
7. 37.▲
   by kobzol 3y ago

   Good point! Guido mentioned that maybe in the future, the new "mini-JIT" in CPython might be able to leverage the type hints. I also want to have this as a thesis topic for my students, to try it out.
8. 38.▲
   by kobzol 3y ago

   I agree that it's not easy to explain this to other people, and Python tooling in general is pretty terrible. OTOH, having types in the code and giving newcomers to the codebase the ability to actually see what types "flow" t
9. 39.▲
   by kobzol 3y ago

   Hey now. Async in Python ain't that bad :)
10. 40.▲
    by kobzol 3y ago

    https://dropbox.tech/infrastructure/rewriting-the-heart-of-o...
11. 41.▲
    by kobzol 3y ago

    I agree that in most cases it should be rewritten for production, but in my experience that quite often doesn't happen, and AI stays in Python even for production usages.