How is this the trolley problem for someone with a terminal disease? I assume the sick population are the people in the trolley and the experimental patient is the person on the track? In this scenario, by not pulling the lever you just extend the life of the people on the trolley to the end of the ride for a dangerous drug. Where as, pulling the level could save the life of the person on the track and the people in the trolley if the drug is successful.
What am I missing? For non-terminal diseases, it's a bit murkier, but still I don't follow the analogy.
Some people do go into remission from a terminal cancer diagnosis, either because the diagnosis was wrong or because they live long enough for an approved treatment to come on the market. Also, that you have terminal cancer doesn’t say anything about how long you’re going to live. You can live for many years with terminal cancer.
I do think we’re overly cautious with drug approvals and I think we should be more open to leaving the decision to patients and their medical teams, but it’s not as simple as saying someone’s terminally ill, so just do whatever. Reducing it down to the trolley problem makes it seem much more black and white and immediate than it really is.
Why don't recommend atop? When a system is unresponsive, I want a I want a high-level tool that immediately shows which subsystem is under heavy load. It should show CPU, Memory, Disk, and Network usage. The other tools you listed are great, once you know what the cause is.
My preference is tools that give a rolling output as it let you capture the time-based pattern and share it with others, including in JIRA tickets and SRE chatrooms, whereas top's generally clear the screen. atop by default also sets up logging and runs a couple of daemons in systemd, so it's more than just a handy tool when needed, it's now adding itself to the operating table. (I think I did at least one blog post about performance monitoring agents causing performance issues.) Just something to consider.
I've recommended atop in the past for catching short-lived processes because it uses process accounting, although the newer bpf tools provide more detail.
All of the features descried in the article are supported by clang except maybe for the constexpr keyword. By your own list, neither one supports all the features. Also, gcc only supports about 4 or 5 features more than gcc, and clang supports a few gcc doesn't. Hardly "much better".
For the Internet as a whole, yes, but not for this narrow case of legitimate news organizations. If Facebook could have building full of moderators to review flagged content on their site, Google could easily fix this issue with a team to handle reports of low quality AI content. Not to mention, how most of these sites sprung up out of nowhere. That should already be a red flag for the algorithm to de-rank until a human could review. And the example of reworded blog spam with identical photos, posted at a later date, again, should be trivial for a team that cared to catch manually(flagged) or through an algorithm.
It's not over, unless Google doesn't care enough about Google News to fix it.
So you prefer, the DSL or GPL over GPLv2? The Doom Source License (or DSL) is the original source code license under which the Doom source code was released in late 1997.[1] I'll take this over the years and years the past licensing has caused any day.[2]
This vulnerability is about injecting keystrokes into connected wireless keyboards and mice.[1] With the phone industry adoption of USB-C, they've made wired easier than ever before.
What does this have to do with the fact that now people have to switch on bluetooth for audio, instead of having a cable connection? And an attack requiring a physical cable connection is a little bit more visible, and less viable if I have my phone in my hand, than a wireless attack via bluetooth, don't you think?
You don’t “have to” switch to only wireless. There are plenty of inexpensive usb-c DACs and even the overpriced Apple usb-c to 3.5mm adapter is a whopping $9.
> This is great news now that the industry phased out physical **audio** connection on phones in favor of wireless.
I recognize that there’s still wired audio connectors but you know full well that the experience is not great because the industry wanted to remove audio jacks.
This comment is generating far more snark than the parent to be frank.
Not everyone wants to use a USB-C dongle so they can use their old 3.5 headphones, and even more people don’t really care about being able to have a mouse and keyboard on their phone in the first place.
If you want me to show you what the “thoughtful discussion” is: The parent made the point that phone companies have been following a trend of locking down physical access in favor of wireless tech. I’ll add that this has not only removed beloved features, but now that everyone is being forced down the Bluetooth/wifi stack we are far more susceptible in public when exploits like these rear their ugly heads. There are roundabout solutions like using a USB-C dongle but… really? Does anyone find that to be effective at all? What about when you want more than one connection? You need a splitter or a hub. It’s just such a seemingly useless “improvement” if it feels like we’re going backwards having to buy extra stuff.
If you want to reply with your disagreement, please do so in a thoughtful manner. Please think before you post. I come to this website not for snark, but for thoughtful conversation ;) Ty
The heuristics used were not sufficient to properly determine the capabilities of the hardware it was running on. Makers can fix this problem by giving users choices.
People like you need to learn that saying things you disagree with does not mean we're stupid or didn't read something. Maybe try understanding someone instead of being a dick. I doubt you have much to contribute to a tech conversation anyway.
Would be interesting to see a a Debian derivative that combines this with the Rust Implementation Of GNU Coreutils.[1] Could be a big win for memory safety and performance.
I looked into this a few years back when I was making my own toy Linux distro, and this is the list of packages provided by a typical GNU system that meet POSIX requirements for a userspace:
* `bash`
* `bc`
* `binutils`
* `bison`
* `Coreutils`
* `Diffutils`
* `file`
* `Findutils`
* `flex`
* `gawk`
* `glibc`
* `grep`
* `tar`
* `gzip`
* `M4`
* `make`
* `man-db`
* `man-pages`
* `procps-ng`
* `psmisc`
* `sed`
That's a reasonable start, but you also need, minimally, something to replace `pciutils`, `IPRoute2`, a bootloader, and an init system. For a close to expected experience, add in `TexInfo`, `XZ`, `ZStd`, and `bzip2`, plus `shadow` if you don't want passwords stored in plaintext.
POSIX doesn't dictate an editor, but you probably want something that can run in a terminal. Usually `cURL` and either `openssl` or `GnuTLS`, plus `bind-utils`, `ldns`, or something equivalent are there for actually using the network, something to replicate `gpg` functionality if you're going to install signed packages, and of course the package manager itself. Cargo is fine for Rust app developers, but can't replace an installer of system packages. You likely need an `ssh` implementation to replace `OpenSSH`.
I'm sure there's more I'm missing, but this is pretty close to what you'd get in a minimal server image.
If you're looking to fully get rid of C and not need a C compiler, though, Linux itself is a hurdle. You don't necessarily need a kernel quite as fully-featured, but you need something that at least implements the POSIX system calls. Just about every Linux distro I'm aware of seems to also provide Python and Perl these days as a whole lot of system utilities and build scripts use them. Presumably, rewriting all of Perl and Python in Rust is not feasible, so you either need some other interpreted scripting language good for system scripting that is written in Rust, or somehow make your shell a superset of POSIX but also much closer to a real programming language.
Don't underestimate the lift of replacing `libc`, either. It's not just the C standard library and interface to system calls. It also provides the linking loader that makes it possible to even run other programs, all of the locales and time zones, the system's name server, profiler, memory dumper. A whole lot of stuff.
A Linux distro is going to need to see compiler to self-host regardless of the user land. If you can live without Linux, there's redox ( https://redox-os.org/ )
Cat fluff piece. Owl’s are far more “evolved” to their predatory niche. In addition, every land animal of prey are on are on the menu for wolves. Cat’s lack of social evolution greatly limits their choice. So much for perfection.
Wolves have taking their social evolution one step further by allowing them to join forces, co-evolving with man. This cat biologist could use a lesson from a human evolutionary biologist.[1] There is a good chance we wouldn't be where we are today, if it weren’t for that perfect combination.
The author said he is just starting on the book, so he's not claiming it's perfect. And the beauty of github, open source is you can fix them with a pull request. For example, the svg is here:
https://github.com/abuseofnotation/category-theory-illustrat...
What am I missing? For non-terminal diseases, it's a bit murkier, but still I don't follow the analogy.