• 0 Posts
  • 80 Comments
Joined 1 year ago
cake
Cake day: December 9th, 2023

help-circle







  • This reminds me of the (probably apocryphal) Mozart quote where a student asked him to teach them how to write a symphony, and was told “start with something more simple and short, for one instrument”. The student complained “but you have been writing symphonies since you were a child!”. The reply: “yes, but I didn’t have to ask how”.

    The application of this idea here is that for someone to know the requirements for their system to the degree that they can really be sure that the most typical suggestions are not sufficient for them, they probably have to understand how the kernel handles swap and RAM to an extent that they don’t really need to ask this question.

    People are very ready to assume that their system is way out of the ordinary, but it probably isn’t.







  • In my experience which is pretty extensive with python but only moderate with typescript I’d say it’s probably better, easier to work with and offers a similar level of flexibility.

    Not sure what you mean by performance but it’s easy to be disciplined when you can’t commit something that isn’t fully annotated. I feel like I can trust it fairly well, except for rare occasions where external library code is wrongly annotated and I have to put some ugly shim in.

    Afaik you can just go to definition in literally any language, typing or no.

    I’m in total agreement about the packaging though, it sucks.




  • Type checking for python is not bad these days, just run pyright (or mypy, I would like to prefer the non MS solution, but we have found pyright much more rigorous) on your code. Yes obviously you can still get out of it with an ignore statement, and that might occasionally be necessary for some libraries, but if you enforce no errors in pre-commit or CI then it’s only a little worse than compile time.