maccam94

I've wanted this as my business-hours pager sound for a very long time...

People can generally only output their max power for short durations. The output level they can sustain is generally much lower. I bet you could try to model higher limits for short distances, but what those should be could vary greatly depending on personal fitness.

DNS cache poisoning?

Dang, they aren't catching the booster this time, but I guess V3 is practically a new vehicle and validating the next Starship launch is probably too critical to risk damage to the launch site for now.

In Zulip, if a thread meanders with messages about a tangent, the authors/mods can choose to move those messages to a new thread (and IIRC messages with links between the two threads are created so it's easy to jump back and forth for any missing context)

If you're laying a communications cable, you should just do fiber. It can carry any type of traffic at high data rates, and you can upgrade the speed over time by just replacing the optics at the ends rather than having to replace the whole cable. Fiber plans are only expensive if your service level is expensive, or if you have to pay to get the line run to your building

Yeah, as far as I know the only way to be sure is by putting the parent process into a cgroup. Then to kill all of the child processes you have to freeze the cgroup, enumerate the pids, send sigterm/sigkill to all of them, before unfreezing again.

very slowly, with the radio at maximum power, and no obstructions

It uses a different transceiver on the satellite which is broadcasting a ~standard LTE signal, at a miniscule data rate

I looked around last week to see if they are on the market yet, and found that Philips already seems to have helium-free MRIs for sale. I'm not sure if they just sealed it better or switched to REBCO.

edit: nvm, finally found more info. it's just better sealed helium https://www.usa.philips.com/healthcare/resources/landing/the...

The Linux kernel doesn't have a stable ABI. Thus, if a kernel function signature changes, or a subsystem gets refactored, etc, drivers get updated as part of the process. If the drivers lived outside the kernel tree, they would have to be updated separately by their own maintainers. That's less efficient and prone to breakage, so generally driver modules are merged into the kernel tree. Often they can even share code with other hardware devices!

Not sure what you mean by "userland" drivers here, but support for kernel modules written in rust is actively being developed. It's already being used for kernel drivers like the Asahi Linux GPU driver for M1 Macs.

Wait, Commonwealth Fusion Systems is already building 20T REBCO magnets, can't those meet the requirements for MRIs?

Why would you use LVM with ZFS? ZFS should handle all of the features LVM has (as far as I can think of, at least).

I would have taken a full screenshot but I had my company's Gitlab open behind it.

This is called dog whistling, and is frequently used to subtly spread racist and fascist views. If you're not doing that, arguing in bad faith is a waste of everyone's time and provides no value to the world.

https://en.wikipedia.org/wiki/Dog_whistle_%28politics%29

Rust references are basically pointers with extra rules, so using a different symbol is reasonable, and rust is immutable by default rather than opt-in (which is an important design decision) so you have to have syntax to mark things as mutable. auto is horribly uninformative for new coders, and var is too overloaded to expect newbies to only use it for mutable variables.

Back in my Windows XP days I had an app installed called Desktop Sidebar[1], which would be exactly the place I'd want all of this functionality today. Or in some kind of widget layer, like with MacOS. Hmm it's been a long time since I thought about desktop customization, maybe I should see if there is anything similar for GNOME these days.

1: https://web.archive.org/web/20120527201322/http://desktopsid...

Because usually they are implementing a subset of the network stack that meets their needs for communication within their internal network. Porting the entire kernel stack that actually handles all of the complexities and quirks of the open internet is a larger task than they needed to tackle.

> no one ever bothered to put something together on UNIX-like systems that resembles any of those options.

What do you mean? io_uring is a Linux kernel interface, and there are several userspace projects that are building upon it.

If you didn't disable the write cache on those drives, flares could have caused bit flips in the cache memory before it was flushed to disk.

Are you able to store that data in reference-counted RC/ARC types? Those can help you avoid dealing with lifetime issues, though you'll still have to think about mutability and concurrency.

The only telemetry you get will be from users that are experiencing a severe problem who also have the technical know-how to turn it on. You will have no idea how prevalent the problem is amongst the general user base. There would be no way to prioritize debugging the issues.

How stable should property ownership be in an area experiencing growth? I think this could be tunable with short term price increase caps that expire 5-10 years out, and reset when the property is sold or the owner starts paying the full market LVT again.

No one is going to donate to something unless they're aware of it, so spreading awareness does help increase the potential pool of donors.

They don't want people distributing unofficial builds that claim to be Signal due to the risk of supply chain attacks against users.

You also need to futz with apt repo priorities to force it to install the deb package instead of the snap installer -_-

I had to do a double take when I read the parent, but I suspect they were referring to running Linux to avoid the Virtual Machine overhead on MacOS. However I doubt the Linux driver support for the M1/M2 has anywhere near the level of power optimization as the MacOS drivers.

The Firefox repo is 27% C++, 14% C, and 9.5% Rust - https://4e6.github.io/firefox-lang-stats/ AWS wrote Firecracker which powers AWS Lamba - https://github.com/firecracker-microvm/firecracker Cloudflare just replaced nginx with an in-house reverse proxy written in Rust called Pingora (not yet open source) Facebook rewrote Mercurial in Rust to help scale their monorepo (called Mononoke, now part of their EdenSCM project) Dropbox rewrote their sync client in Rust, and they wrote their block storage service (Magic Pocket) in it. A significant portion of Google's new Fuchsia OS is written in Rust, and it is currently powering Nest devices NPM's backend is written in rust curl can now use Rust's hyper library for making http requests