This is the first time I've heard of Deno so I'm only going by their Security & Permissions doc page [1], but it looks like the doc page at the very end recommends using system-level sandboxing as a defense in depth. This suggests that Deno doesn't use system sandboxing itself.
To me this is a bit alarming as IIRC most app runtime libraries that also have this in-runtime-only sandboxing approach are moving away from that idea precisely because it is not resistant to attackers exploiting vulnerabilities in the runtime itself, pushing platform developers instead toward process-level system kernel-enforced sandboxing (Docker containers or other Linux cgroups, Windows AppContainer, macOS sandboxing, etc.).
So for example, .NET dropped its Code Access Security and AppDomain features in recent versions, and Java has now done the same with its SecurityManager. Perl still has taint mode but I wonder if it too will eventually go away.
Deno is a V8 wrapper, the same JS engine as Chrome. Vulnerabilities are very common there, not necessarily because it's poorly designed but more because there's massive financial incentives in findings them.
This plus what you mentioned is why I would never trust it to run arbitrary code.
Now in the context of yt-dlp it might fine, google isn't going to target them with exploits. I would still prefer if they didn't continue to propagate "DeNo iS SaFe BeCauSe It HaS sAnDbOxInG" because I've seen projets that were actually executing arbitrary JS rely on it thinking it was safe.
Consumer Reports' reviews of newer Mazdas always stress the infotainment system as a big negative, to the point that I would seriously reconsider them as a result.
Apparently it's a case of "right idea, wrong execution." The deep menu hierarchies and small text make the jog wheel knob controls even more awkward (in CR's view) than a decent touch-screen system plus a few buttons. [1]
Maybe that's one reason that BMW has just abandoned their Mazda-like wheel controller [2], despite having had it for years before Mazda.
(Interestingly CR says the latest Mazdas do have a touchscreen, but touches are allowed when the car is moving only for CarPlay/Android Auto.)
[1] https://www.consumerreports.org/cars/mazda/cx-50-hybrid/2025... - "the CX-50's infotainment system is frustrating and distracting to use while driving. [...] the text- and list-based menu structure forces drivers to glance away from the road for too long. Even simple radio tasks require multiple taps and twists of the rotary controller knob"
S. Jay Olshansky et al., "Implausibility of radical life extension in humans in the twenty-first century", Nature Aging (2024)
Open access, here is the abstract:
> Over the course of the twentieth century, human life expectancy at birth rose in high-income nations by approximately 30 years, largely driven by advances in public health and medicine. Mortality reduction was observed initially at an early age and continued into middle and older ages. However, it was unclear whether this phenomenon and the resulting accelerated rise in life expectancy would continue into the twenty-first century. Here using demographic survivorship metrics from national vital statistics in the eight countries with the longest-lived populations (Australia, France, Italy, Japan, South Korea, Spain, Sweden and Switzerland) and in Hong Kong and the United States from 1990 to 2019, we explored recent trends in death rates and life expectancy. We found that, since 1990, improvements overall in life expectancy have decelerated. Our analysis also revealed that resistance to improvements in life expectancy increased while lifespan inequality declined and mortality compression occurred. Our analysis suggests that survival to age 100 years is unlikely to exceed 15% for females and 5% for males, altogether suggesting that, unless the processes of biological aging can be markedly slowed, radical human life extension is implausible in this century.
Indeed, I have heard that at least early versions of Finale had painfully unmaintainable code that severely slowed its development.
This supposedly was/is in part because Finale's original author Phil Farrand [1] was a musician turned self-taught programmer and Finale was only his second software product.
These news reports quote responses from other interested groups like the New York Police Department itself, the New York Civil Liberties Union, and ShotSpotter, Inc.:
Note that the NYPD's leader, the New York City police commissioner, is appointed by and answerable to the mayor. Mayor Eric Adams supports the ShotSpotter gunshot alert system, which may explain the NYPD's position.
Also note that this audit is published by the New York City Comptroller's office. Both the mayor and comptroller are directly elected by the people, meaning both Adams and Comptroller Brad Lander are politicians as opposed to nonpartisan bureaucrats/civil servants. That may have something to do with Lander's framing of his office's report.
Fringe benefits not specifically excepted are also taxable wage income in the United States, but I don't think employers are forced to gross them up at the highest marginal tax rate or are otherwise discouraged from giving them out in lieu of cash.
The USA's income tax agency, the Internal Revenue Service or IRS, has a whole booklet to help employers figure out how to withhold taxes for fringe benefits:
It discusses the de minimis exception mentioned in the originally linked page, as well as exceptions for some meals - important if your employer gives you free or discounted cafeteria lunch or restaurant lunch discount coupons.
Personal story: Some of my relatives in Thailand play the piano or electronic keyboard as a hobby. Almost all their "sheet" music score books are printed in this notation, but some of my western friends didn't realize it was music at first until they saw the lyrics.
Later on, I learned that country music in the US uses a somewhat similar "Nashville System" [1], but I believe that system doesn't let you span multiple octaves the way this system does.
To me this is a bit alarming as IIRC most app runtime libraries that also have this in-runtime-only sandboxing approach are moving away from that idea precisely because it is not resistant to attackers exploiting vulnerabilities in the runtime itself, pushing platform developers instead toward process-level system kernel-enforced sandboxing (Docker containers or other Linux cgroups, Windows AppContainer, macOS sandboxing, etc.).
So for example, .NET dropped its Code Access Security and AppDomain features in recent versions, and Java has now done the same with its SecurityManager. Perl still has taint mode but I wonder if it too will eventually go away.
[1] https://docs.deno.com/runtime/fundamentals/security/