51–57 of 57 posts
Earlier quoted context omitted.
It's below on the thread, see: https://threadreaderapp.com/thread/1824872498363523537.html Honesty I wished every HN post linking to Twitter was just changed to a threadreader link because otherwise only registered Twitter users can see the content being posted.
Oh, thanks. I didn’t realize there’s context that can’t be seen if I don’t have an twitter account.
https://www.npmjs.com/package/systeminformation
https://github.com/sebhildebrandt/systeminformation/blob/mas...
https://github.com/sebhildebrandt/systeminformation/blob/mas...
> this person has never programmed on windows in their lives https://nitter.poast.org/da_wamwoowam/status/182487490957266... How about some fucking empathy? Yes, maybe the dev isn't a windows expert, but I'd guess most devs aren't. Most people don't have the luxury of pulling in a specialist to do every little feature, nor the luxury to do a deep dive to figure the absolute correct way. Such is the reality of (commer…
> Discord Applying Forced Arbitration - opt-out before it is too late!
> https://news.ycombinator.com/item?id=40252525
We're talking about a corporation handling our private communications, not a group of unpaid volunteers. Corporations act out of greed. That's the way capitalism works and we shouldn't pretend otherwise. Two decades ago, there were lots of empathy for the company that promised to "not be evil" and just look at how well that went. Accountability is what we should be pushing for, not empathy for those who abuse us.
The code in question supposedly gathers system information to send back to Discord. It's sensitive information gathered for Discord's own sake. Maybe, just maybe, they should be more aware of what their own code is doing at the very least when doing such things.
> this person has never programmed on windows in their lives https://nitter.poast.org/da_wamwoowam/status/182487490957266... How about some fucking empathy? Yes, maybe the dev isn't a windows expert, but I'd guess most devs aren't. Most people don't have the luxury of pulling in a specialist to do every little feature, nor the luxury to do a deep dive to figure the absolute correct way. Such is the reality of (commer…
I have also never programmed on Windows in my life. Seriously, not so much as a trivial script. But I would look up the right way to find the system installation if I were writing production code, or even personal-use code, that needed to know where it was. I also wouldn't walk the filesystem looking for a program I was relying on (and assuming filenames and installation locations, but evidently not with a definitive…
> This is amazing. Started as a small project just for myself, it now has > 15,000 lines of code, > 600 versions published, up to 8 mio downloads per month, > 300 mio downloads overall. #1 NPM ranking for backend packages. Thank you to all who contributed to this project!
It's fair to blast Discord here, but not the library's authors. When you want "production code", maybe do better* than npm-installing a project with lifetime donations of, let's see, $624.
* Like donate, audit and upstream improvements, or build it yourself from scratch.
Earlier quoted context omitted.
I have also never programmed on Windows in my life. Seriously, not so much as a trivial script. But I would look up the right way to find the system installation if I were writing production code, or even personal-use code, that needed to know where it was. I also wouldn't walk the filesystem looking for a program I was relying on (and assuming filenames and installation locations, but evidently not with a definitive…
So what's the enterprise-quality solution for querying the GPU for the information they need? If I search Google for "nvidia-smi.exe", one of the top results is a Stack Overflow answer with 70 upvotes, describing exactly the approach taken by the linked code. https://stackoverflow.com/a/57100016
On all my Windows/Nvidia systems, the current version of nvidia-smi.exe is present in %SystemRoot%\System32.
OTOH, …\FileRepository*\nvidia-smi.exe matches anywhere from one to eight versions, dating back to 2023.
Perhaps this is only true because I use official Nvidia mechanisms (.exe installer from Nvidia Web site or Nvidia-supplied app) to install drivers, rather than Windows Update or INF install?
Incidentally, the wildcard …\FileRepository\nvdm* suggested in the Stack Overflow answer returns zero directories on my systems, as all Nvidia driver repository directories start with either nv_dispi (GeForce) or nv_dispwi (workstation).
Which makes sense, because obviously the INF file name used to generate these directory names is subject to change without notice.
In any case, per "nvidia-smi --help":
Note that the functionality of NVSMI is exposed through the NVML C-based
library. See the NVIDIA developer website for more information about NVML.
Python wrappers to NVML are also available. The output of NVSMI is
not guaranteed to be backwards compatible; NVML and the bindings are backwards
compatible.
http://developer.nvidia.com/nvidia-management-library-nvml/
http://pypi.python.org/pypi/nvidia-ml-py/> this person has never programmed on windows in their lives https://nitter.poast.org/da_wamwoowam/status/182487490957266... How about some fucking empathy? Yes, maybe the dev isn't a windows expert, but I'd guess most devs aren't. Most people don't have the luxury of pulling in a specialist to do every little feature, nor the luxury to do a deep dive to figure the absolute correct way. Such is the reality of (commer…