https://spack.readthedocs.io/en/latest/build_settings.html#e...
People use this the tell Spack where the system cuda libs or system MPI are.
Wow, gen Z lingo has come into HN faster than I expected. Can someone translate this to traditional English? The definition I find for 'yeet' ("an exclamation of excitement") isn't particularly enlightening...
Update: I see, thanks all!
My definition of "Yeet" is to fling/throw/hurl something, typically with great vigor. Urban Dictionary defines it as "To discard an item at a high velocity." Derives from the Latin Iacio, From Proto-Italic jakjō, from Proto-Indo-European (H)yeh₁- ("to throw, let go"). JK I just made that up, but it's actually plausible.
Never heard the "exclamation of excitement" definition.
"The first empty soda can was yote many moons ago"
According to Wiktionary:
"yeeted
1. simple past tense and past participle of yeet" [1]
Worth noting there is a fair amount of discussion on whether the past tense is "yeeted" or "yote", or even "yaught": https://en.wiktionary.org/wiki/Talk:yeet
See also: https://linguistics.stackexchange.com/questions/28300/what-i...
[1]: https://en.wiktionary.org/wiki/yeeted#English
(I do think it would be pretty funny if the past tense ended up as "yote", though.)
I think you're way overestimating the people who come up with new words :P
I think it's the wrong abstraction. It encourages ridiculous amounts of bloat and duplication, of bandwidth, file systems, virtual environments, and docker images. It's really not actually that portable.
It encourages blindly installing unauditable giant binary blobs which run with all kinds of leaky abstractions. But boy howdy are they convenient.
I think "Allow external hosting" is the best case here. The first point of user expectation on PEP 470 is:
> Easily allow external hosting to "just work" when appropriately configured at the system, user or virtual environment level.
That's already out of the window once GPGPU is involved. The ecosystem is much better than it used to be, but there is still no plug-and-play GPGPU on linux without hiccups.
Let PyPI be the namespace, registry and lookup, and let users pass an --allow-external again, or (less optimal imho) do something like Conda channels. Improve the user experience for integrating with external hosts.
Pip is unlike NPM, Cargo, go get, etc because Python is much more intimate with linked libraries. It's unlike Brew because it's way more cross-platform. It's much closer to apt-get in this regard, and its challenges are different. Apt-get has sources lists, and I think that makes some sense for Python as well.