-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
why julia but not pytorch? #16
Comments
Hi, But in general, Julia offers the same features as PyTorch, actually quite a bit more such as native JIT compilation of the whole code (which was just recently added in PyTorch). So yes, a rewrite in PyTorch would be possible too but there is no reason why PtyLab should be faster or easier to implement in PyTorch. And the Python version uses CUDA too and one of the heavy operations are FFTs which are effectively the same in PyTorch, Julia, Jax, CuPy, ... |
I see. Thanks, Felix. I asked that questions as I wondered which should be the base language when open-source resources in computational imaging/optics. Currently, there are many choices: pytorch/julia/jax etc. Best, |
There is no "perfect" language, it depends on your needs, I would say. I would recommend to stick with the one you are most proficient and convenient with. In my case it's Julia but I also use PyTorch daily. However, if you need heavy ML tasks PyTorch and TensorFlow might be the best options currently because of their huge user base and the thousands examples. |
Sure. Like your last sentence most 😄 |
Hi Ptylab team,
Interesting project.
Could you pls tell me why you chose Julia but not Pytorch as the base language?
Best,
Guangyuan
The text was updated successfully, but these errors were encountered: