Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

PyTorch: Where we are headed and why it looks a lot like Julia (but not exactly)

dev-discuss.pytorch.org

Post reply on HN
Print view View original

1–10 of 291 posts

Re: PyTorch: Where we are headed and why it looks a lot like Julia (but not exactly)

#3

Post by xbpx »

Java has a massive ecosystem yet we continue to see rapid replacement of backends in JavaScript (Node now Deno) and Golang. Each of those language ecosystems rapidly became both large (arguably too large) and robust.

Rust has been eating C++ lunch. Same rapid rise of ecosystem story.

Instead of forcing Python to be a language it isn't it might be more efficient and ultimately the "right choice" to invest the time in Julia.

Julia is great for numerical computing, it needs faster time to plot and more hands in the ecosystem. The former will be solved and the latter seems inevitable to me. Pitch in!

Re: PyTorch: Where we are headed and why it looks a lot like Julia (but not exactly)

#4

Post by forrestthewoods »

The more I use Python the more I hate it. It’s genuinely a bad language, with a stellar ecosystem. Ironically, the most valuable parts of the ecosystem are often written in C (NumPy).

It’d be interesting to see how much of the Python ecosystem is actually necessary to move PyTorch to a better language.

I’m afraid we’re stuck with Python for the next 20 years. That makes me very, very sad.

Re: PyTorch: Where we are headed and why it looks a lot like Julia (but not exactly)

#6

Post by jshen »

forrestthewoods wrote: post #4

The more I use Python the more I hate it. It’s genuinely a bad language, with a stellar ecosystem. Ironically, the most valuable parts of the ecosystem are often written in C (NumPy). It’d be interesting to see how much of the Python ecosystem is actually necessary to move PyTorch to a better language. I’m afraid we’re stuck with Python for the next 20 years. That makes me very, very sad.

100% this. I wish it weren’t so.

Re: PyTorch: Where we are headed and why it looks a lot like Julia (but not exactly)

#7

Post by doliveira »

adenozine wrote: post #5

Neither language have proper tail call elimination, which, is absolutely insane to me. Yall really just write procedural code for everything?

You must be in quite the functional bubble (I envy you for that, though)

Re: PyTorch: Where we are headed and why it looks a lot like Julia (but not exactly)

#9

Post by noitpmeder »

forrestthewoods wrote: post #4

The more I use Python the more I hate it. It’s genuinely a bad language, with a stellar ecosystem. Ironically, the most valuable parts of the ecosystem are often written in C (NumPy). It’d be interesting to see how much of the Python ecosystem is actually necessary to move PyTorch to a better language. I’m afraid we’re stuck with Python for the next 20 years. That makes me very, very sad.

What do you think the major drawbacks are? Speed would be the top of my list, but most projects to not need anything more than what python can currently pump out.

Re: PyTorch: Where we are headed and why it looks a lot like Julia (but not exactly)

#10

Post by justapassenger »

forrestthewoods wrote: post #4

The more I use Python the more I hate it. It’s genuinely a bad language, with a stellar ecosystem. Ironically, the most valuable parts of the ecosystem are often written in C (NumPy). It’d be interesting to see how much of the Python ecosystem is actually necessary to move PyTorch to a better language. I’m afraid we’re stuck with Python for the next 20 years. That makes me very, very sad.

Bad languages like Python, JavaScript, PHP are responsible for powering large part of tech revolution. Ability to write bad code easily is IMO large part of why they’re so popular. Low barrier to entry helps to build huge ecosystem.
Post reply on HN