Not hating the player nor the game. Point was that it's hard to adopt something that one can't be confident will be maintained and supported a year from now.
> For those who use debuggers regularly, would you be willing to share how you learned to use them or any tips and resources that helped you?
I use debuggers a lot. I learnt the most when I implemented my own toy debugger. Everything made a lot more sense afterwards. It also made me realize that debuggers give you only a limited view of what is really going on in a CPU. If you want to truly understand how a program is executed on a CPU you'll need to learn a lot more about CPUs and likely about the specific CPU you work with.
Not a fair comparison IMO. Jax is low level library used to make ML frameworks while pytorch is a full blow ML framework.
In terms of is it worth using it - that depends on what you're doing. If you just want to start with ML training probably not. If you have something already and you want to take it to next level (e.g. influence how training and inference work) than it's a good choice. You might be interested in looking into flax or haiku instead of using vanilla Jax. These are closer to pytorch.