Live data from Hacker News

PyTorch 1.0 is out

github.com

71–72 of 72 posts

Re: PyTorch 1.0 is out

#71
post #47

Earlier quoted context omitted.

But you're familiar with cin/cout right? Same thing. Weird at first every C++ programmer should be familiar with it now. I pronounce > as 'goes to' and 'comes from' or something similar.

Of course. But what I'm not used to is seeing something like this: cin >> foo(x);

This is common in many functional languages, and even in the shell. Think of pipes such as input | sed ... | grep ..., or in F#, xs |> List.map (fun x -> x.Value). Basically, each input goes into the function and is piped through to get to the output.

Re: PyTorch 1.0 is out

#72
post #27

Earlier quoted context omitted.

I love PyTorch, but my experience with jits embedded in Python (eg. Numba) has been everything but simple, nevermind trivial. I'll really have to try it to believe it.

I’ve had the opposite experience with numba in production. It works almost flawlessly, very easy to reason about the generated code and inspect annotations, easy to debug.

Do you interact with numpy or other compiled numerical packages? this is where it usually breaks for me. The thing is that I use numpy, scipy, keras, tensorflow, etc. in literally every project, making numba not too useful
Post reply on HN