Why is it never mentioned that Sam the lone genius Gross who is "interested in PyTorch training workflows" is a fulltime Facebook employee? Not that it's bad but it should be mentioned that it's a corporate initiative.
Notes from the Meeting on Python GIL Removal Between Python Core and Sam Gross
31–40 of 105 posts
Re: Notes from the Meeting on Python GIL Removal Between Python Core and Sam Gross
#32Re: Notes from the Meeting on Python GIL Removal Between Python Core and Sam Gross
#33Why is it never mentioned that Sam the lone genius Gross who is "interested in PyTorch training workflows" is a fulltime Facebook employee? Not that it's bad but it should be mentioned that it's a corporate initiative.
Re: Notes from the Meeting on Python GIL Removal Between Python Core and Sam Gross
#34Why is it never mentioned that Sam the lone genius Gross who is "interested in PyTorch training workflows" is a fulltime Facebook employee? Not that it's bad but it should be mentioned that it's a corporate initiative.
Re: Notes from the Meeting on Python GIL Removal Between Python Core and Sam Gross
#35I think Python core developers should not worry about closed-source enterprise Python code. If users are gaining performance, they will bend over backward porting their code to this new version. At minimum, I predict, all FAANGMULA would jumped in the bandwagon and create a pretty big ripple effect.
And Python is not a business with customers. It’s an open source volunteer project.
Re: Notes from the Meeting on Python GIL Removal Between Python Core and Sam Gross
#36I can't help but read all the interjections from the core developers as a strong indication of why all these sorts of things tend to fail on the vine. From Unladen Swallow onward there have been these groups off doing interesting and awesome experiments to try and make Python faster, and they never actually make it into something that Python end-users can use (yes, I know US had shortcomings). This is the work of one…
> Would you prefer to support some weird arbitrary nameless closed source extensions, or have a multicore Python? There's nothing wrong with staying on an older LTS version of Python. Let the people with the nameless closed-source stuff stick with that. The beauty of open source is that they can fork the older, GIL-ful version of Python and maintain it, if they like. Multicore would be a tremendous boon to the langua…
There was an older LTS version of Python called Python 2.7. Last I checked people hated the transition and were still bitching about it in 2021.
Re: Notes from the Meeting on Python GIL Removal Between Python Core and Sam Gross
#37I think Python core developers should not worry about closed-source enterprise Python code. If users are gaining performance, they will bend over backward porting their code to this new version. At minimum, I predict, all FAANGMULA would jumped in the bandwagon and create a pretty big ripple effect.
Re: Notes from the Meeting on Python GIL Removal Between Python Core and Sam Gross
#38Why is it never mentioned that Sam the lone genius Gross who is "interested in PyTorch training workflows" is a fulltime Facebook employee? Not that it's bad but it should be mentioned that it's a corporate initiative.
Is it actually a corporate initiative? The project is hosted on Sam's personal GitHub[1]. [1]: https://github.com/colesbury/nogil
Re: Notes from the Meeting on Python GIL Removal Between Python Core and Sam Gross
#39Why is it never mentioned that Sam the lone genius Gross who is "interested in PyTorch training workflows" is a fulltime Facebook employee? Not that it's bad but it should be mentioned that it's a corporate initiative.
At least the "Brand Guidelines" PDF makes it clear that “PyTorch, the PyTorch logo and any related marks are trademarks of Facebook, Inc.”: https://pytorch.org/assets/brand-guidelines/PyTorch-Brand-Gu...
Also a small hint in `CONTRIBUTING.md`: https://github.com/pytorch/pytorch/blob/master/CONTRIBUTING....
Re: Notes from the Meeting on Python GIL Removal Between Python Core and Sam Gross
#40I think Python core developers should not worry about closed-source enterprise Python code. If users are gaining performance, they will bend over backward porting their code to this new version. At minimum, I predict, all FAANGMULA would jumped in the bandwagon and create a pretty big ripple effect.
I have heard of FAANG. I guess M stands for Microsoft. Who's ULA?