Pretty much. There's been a tendency among reactionary sorts to attack any piece they don't like by saying the writer is "just a journalist", ignoring the actual piece, and ignoring any credentials that the author has, like in this case, the writer of the piece is an Associate Professor at the University of Miami.
Number of variants to a large extent. Risc-V has a relatively few number of implementations that are about the same in terms of how they implement things. Aarch64 has a comparably huge number of implementations that have different pipeline descriptions, different extension APIs supported, etc. Aarch64 includes descriptors for everything from a low-end Cortex A53 designed back in 2012 to a a high-end Apple M2 that was released this year.
Noise is a big one. The more levels you have, the more likely it is noise is going to turn a 0 to a 1 or a 1 to a 2, for example. It also requires more complicated switching transistors, because you can't rely on things being simply on or off, but rather have to generate a number of intermediary voltages.
There's still a ton of equipment out there, from industrial CNC machines, to musical gear, to embroidery machines, that were built with floppy drives as the main, if not only, way of interchanging data. Replacing perfectly functional gear like that because the exchange medium is a bit old just doesn't make financial or logical sense in a lot of cases.
There's also a fourth thing to take into consideration. The pandemic caused a lot of people in san francisco to start working from home, so a huge number of people who would normally be in higher profile areas, like in downtown, aren't there. BART, for example, has been running at a third the ridership it was pre-2020 (1). Thus, the few people left, especially the homeless, become all the more visible. When all you see are homeless people when walking down Market Street, it becomes easy to think that the problem is a lot more out of control than it is.
Honestly, I think one of the biggest reasons is that it just became easier and cheaper in the linux world to throw a stack of raspberry pis at the problem. Windows, multi-seat became advantageous because the cheapest Windows box was at least a couple hundred dollars. Linux, however, why bother messing with a stack of $100 multi-seat adapters when a pi, memory stick, and power supply is $50? Had the pi and similar super cheap boxes not come out, I imagine you'd have seen more work polishing up the multi-seat experience to be extremely seamless, but a lot of that work just wasn't needed.
OpenBSD is much more strict than FreeBSD with regards to release cycles. You get N-1 releases, period, which ends up being any version gets you about a year of support.
Keep in mind as well that your employer probably pays a significant chunk of your insurance premiums right now, usually around 3/4 of the full costs of providing you insurance. This is what tends to bite people when they need COBRA coverage or other gap coverage when changing jobs, etc.
Domains are used for more than just webhosting. The owner could have email accounts, etc, that use the haiku.org domain that they don't want to switch to another less recognizeable name.
A lot of bits of security rely on some level of non-determinism. Things like TCP initial sequence number generation, where every TCP connection sequence starts with a random number. There have been numerous attacks where the RNG wasn't good enough, so an attacker could determine the TCP sequencing and perform various malicious activities. Additionally, things like in-kernel VPNs, like IPSEC and WireGuard, also need RNGs for their own internal functions. Calling out to userspace for that would be painful and could potentially break in a lot of unexpected ways.
It's more secure because you're minimizing the attack surface. The jailed process has no binaries an attacker can use to further exploit the system, not even a shell. It means that there's a minimal to non-existent /etc directory, meaning there is less information about the server and the network it's on. It also means there are fewer places to hide modules to persist, because you control so much of the tree.
Going further, you can place the few executable files you need in a read-only filesystem, so attackers can't copy their own payloads in, further restricting what they can do. You can continue that process with firewall rules that are much more restrictive than what you could use with a more general purpose server, such as blocking any traffic that isn't to or from port 80/443. You can also virtualize the network of a jail, so an attacker wouldn't even get information about the network's layout from a compromised jail.
When Autorun, and Windows 95, were being developed, CD-Rs were multi-thousand dollar machines with media that cost $15+/disc, and USB was still being hashed out in the research labs. As such, the only real removable media that would have been used under Autorun would have been professionally mastered CDs, which had a $450+ minimum outlay for a master, and usually a minimum lot size atop of that, which was more than most people up to no good would have been willing to spend. Yes, as Autorun became a more viable attack vector, more protections should have been put in place, but in 1995, it was pretty low-risk.
I'd argue the opposite. xGPL makes it easier for the founding company to just run away with it. We saw it with MongoDB, where it being AGPL means one company can control and unilaterally relicense it. Other examples I'd see of being GPLed doing little to nothing to prevent such shenanigans are any Oracle owned GPLed properties -- Java, MySQL, and VirtualBox all have user-hostile projects and misfeatures added even with the GPL. Conversely, permissive Free projects like LLVM and Postgres have had a lot harder time with one company controlling, because its non-copyleft nature means that everyone has a fair footing in controlling the direction.
Because that would make llvm a lot less useful and a lot more restrictive on the kind of places the compiler infrastructure could be used in. LLVM would not easily be able to be used in places like mesa if it were under the GPL, for example.
You have a url that purports to be a certificate of authenticity. What happens to that certificate of authenticity when the site goes down, or gets sold to someone who decides to replace all the images there with poop emojis?
It's a shame that that lobby's been closed to the public for decades. Seems like it would have been an interesting place to kill a half hour or so on an idle saturday. Though if you go around the corner on the street view, you can see them doing work on the well, bringing in a crane of some sort
LA's got a few more well-hidden oil wells nearby. While Hope Tower's now gone, LA Magazine had a feature a few years ago that described a couple other oil wells hidden in plain sight. https://www.lamag.com/citythinkblog/hidden-oil-wells/
The first question that comes to mind here is if Ford's going to offer a crate battery pack too. A crate motor in and of itself is huge, but an electric crate powertrain that's equivalent to GM's Connect and Cruise, would be huge for people looking for a mostly drop-in electric conversion.
Offhand, one of the big issues that comes to mind is latency. DDR4 has a much higher latency than DDR2 between requesting and receiving, so could be potentially slower in a simpler core that doesn't have as big of a cache, and less aggressive cacheing/fetching algorithms.
Lots of reasons. Sometimes concurrency is a relatively soft need where you could get by with multiple processes, but it would be nice if the language itself provided some capability for things like threads. Or your dev team is much more familiar with python than with other languages, and the time to retrain and rewrite would be greater than the benefits. Or the rest of the language could have greater issues and you don't want to give up excellent libraries like numpy.