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

Re:PyTorch: Where we are headed and why it looks a lot like ... by amelius on Friday November 26, 2021 @08:10PM (#29356129)

I know what you mean. I especially dislike the use of an "end" keyword everywhere without a corresponding "begin" keyword.

[ Parent | on HN ]

Re:PyTorch: Where we are headed and why it looks a lot like ... by cookieater on Saturday November 27, 2021 @11:10AM (#29361172)

Does it really matter though? I mean, whether it's a closing bracket or a whitespace demarcated control flow - does it really effect anything you do in the language? Julia solves a lot of problems, like real problems - quibbling over begin/end vs {/} or white space seems kinda silly.

Meanwhile I have actually seen real world lost productivity due to white space in python. Curly brackets not so much. Never seen lost productivity over begin/end but I'm sure it's happened. It seems silly to me either way - it doesn't really effect anything.

[ Parent | on HN ]

Re:PyTorch: Where we are headed and why it looks a lot like ... by dnautics on Friday November 26, 2021 @09:55PM (#29356871)

I think that's inherited from matlab.

[ Parent | on HN ]

Re:PyTorch: Where we are headed and why it looks a lot like ... by edgyquant on Friday November 26, 2021 @10:57PM (#29357261)

Huh okay. I’ve never used Matlab but one of the first languages I played with was a basic for simple game development

[ Parent | on HN ]

Re:PyTorch: Where we are headed and why it looks a lot like ... by freemint on Saturday November 27, 2021 @07:24AM (#29359637)

begin is a Julia keyword though it.

But yes end closes begin, for, function and while.

[ Parent | on HN ]

Re:PyTorch: Where we are headed and why it looks a lot like ... by edgyquant on Friday November 26, 2021 @10:56PM (#29357258)

Yeah that’s exactly what I’m talking about

[ Parent | on HN ]