Yeah, I found it myself. And yes, it's nasty stuff. But in the context of the article, it’s pure nonsense.
Should we ban anhydrous ammonia, chlorine, or gasoline? They are nasty and dangerous too. The article is purely scare-mongering to make it seem true while obviously pushing an agenda. This is not science. See my reply at the same level after I did a review.
It's by far the most common phrase I've heard used to wipe+reinstall a system in the past 20 years? 25 years? Not just the most popular colloquialism, the most popular phrase, period.
My experience is US/West Coast/Tech companies, for reference.
I’ve spent 20+ years in tech in roles ranging from IT to engineering at west coast and midwest companies and this thread is the first time I’ve heard “nuke and pave”.
At the places I’ve been, systems got “wiped” or “re-imaged” most commonly. I suspect this terminology is hyper local.
I've worked in tech in the Bay Area for 30 years, started in IT at UC Berkeley and then at Sendmail. Never heard this term before. We always "wiped and re-imaged".
Probably because it is a leftover from the 1990s/2000s when you had to completely reinstall your os. That’s no longer necessary, as long as you’re not using windows.
Their Jellyfin client for iOS and Apple TV was a bit flaky for a while, but last year some update fixed those issues and it's been rock solid for me. I also bought Infuse and it's a decent alternative interface.
jellyfin handles my 12 TB media library with transparent ease. i use infuse as a client on my apple tvs, including devices at my family and partners' places via tailscale on aTV
if it's good and it works well, then the human using the LLM did a good job, and need not credit their LLM of choice as one would not credit their rubber duck.
This thought process begs the question, why not just review code and deny what's bad, rather than blanket ban any code with LLM involvement? That way you retain the productivity benefits of LLMs, and can still deny flawed code.
I use the great, free, "Suspicious Package" app [0] to inspect installers like these.
In fact, it was Supertone Shift's installer that prodded me to seek it out (I happened to find and install Shift a couple of weeks ago).
In this case, it needs admin permissions to install to `/Library/Application Support` as well as `/Library/Audio`.
It needs to restart in order for the HAL driver to be loaded (this provides the virtual audio interface for using the app with Teams, Zoom, etc.)
The preinstall/postinstall scripts simply handle the app's directory in Application Support.
I decided it was safe enough, and had some fun playing with it. It contacts what it claims are licensing servers (when it starts), and won't start without it. It wanted to keep contacting those servers constantly, but blocking its network access via Little Snitch didn't prevent it from functioning. The network traffic was in the single-digit kilobyte range, so I felt reasonably confident no audio data was being looted.
i have found the recent crop of SotA LLMs to be extremely useful for the latter few tasks you mentioned. Give it my full, comprehensive CV, as well as a prospective job description, then ask "tailor a condensed resume from the info in my CV to match this job description."
Of course you'll want to review and edit, but it's taken a huge amount of drudgery out of the process, for which I am grateful.
- [0] https://pubmed.ncbi.nlm.nih.gov/33769492/
- [1] http://www.rimed.org/rimedicaljournal/2023/06/2023-06-40-ima... (via https://rimedicalsociety.org/rhode-island-medical-journal/)
- [2] https://en.wikipedia.org/wiki/Paraquat
reply