wl

Isn't the usual case for physicians and dentists appointment reminders? (I don't understand why utility companies need to interrupt my day, so I ignore that.) I wouldn't mind them being able to actually reach me about urgent things via phone, but I keep a calendar like a grown adult and appointment reminders do nothing for me except interrupt my day.

That "repurposing" is more morphology than grammar. You also frequently find in Indo-European languages multiple cases having overlapping morphology, but that doesn't necessarily change the cases themselves. My point, in any case, is that Hittite has the older animate/inanimate genders from Proto-Indo-European (only attested in the Anatolian languages!) whereas Sanskrit has the later masculine/feminine/neuter genders.

Or learn Hittite. It's got the oldest corpus in the Indo-European language family. You've got your standard assortment of Indo-European cases. Grammatical gender is animate/inanimate and the animate gender has yet to split into masculine and feminine. The script is tons of fun, especially if you write it with a stylus on clay. And as a bonus, you get to learn a smattering of Sumerian and Akkadian vocabulary.

There's a lot of disagreement about Sumerian grammar. If you like to argue, that might be a bonus.

There's quite a bit more negligence going on here than a typical murder—unless you've got some information that the cops were out to intentionally harm the victim.

The public would probably be served by the shooters not carrying a badge anymore, but it doesn't take jail to accomplish that.

This guy needs to be compensated for his pain and suffering, his economic losses due to his disability, and for the care he'll need for the rest of his life. Jailing the people whose negligence is responsible for his injuries doesn't help him.

The big exception to this I've seen: The functioning bit of software was written in an oddball language that was already niche decades ago and the pool of developers who are competent to work on such a codebase is exceedingly small.

> You do not print a lower receiver compatible with standard parts.

I've personally seen 3d-printed polymer Glock frames and AR-15 lowers. I've personally seen them stand up to sustained automatic fire. You're not going to be printing with PLA and there's plenty of bad designs out there that can't take the stress, but good designs that are durable when printed with the appropriate filament or resin exist.

> Printing plastic has a very hard time confining the gunpowder.

Which is why printing Glock frames and AR-15 lowers works so well—they're the controlled part and they don't bear the pressure of the gunpowder combustion products.

> Printed guns are ghost guns, but the vast majority of ghost guns are not printed guns

Sure, you're probably seeing way more Polymer80 and aluminum 80% lowers than 3d printed ghost guns... but people aren't CNCing those at home, either. They were milling those out with special jigs and a drill press.

Correct.

Other countries regulate the pressure-bearing parts instead. It probably started off with a safety rationale (those parts are generally proof tested), but those parts ALSO tend to be the ones that are more difficult for someone to produce at home.

There are plenty of 3D printed guns that are good for more than one shot. The classic examples are 3D printed Glock-style frames and AR-15 lower receivers. As far as US gun laws are concerned, those parts are the firearm and the rest of the parts are uncontrolled. So you print those, buy barrels, triggers, magazines, etc to finish the build and voila, ghost gun.

There's a lot of people out there who blame their epidurals for lower back pain and the like, but the evidence for causality is not there.

If it were as simple as waving a magic wand and fixing the epidural or bringing on the anesthetic gas, we wouldn't have this problem.

The consensus seems to be shifting more towards converting to general anesthesia after epidural failure unless there are very clear reasons not to.

It's not as if people are pushing random drugs into epidurals. There's a small number of drugs that are commonly used and the differences come down to selecting the classes of drugs to be used, the particular drugs from those classes, and the dosing. There's no one right answer. In other words, it's just like the rest of anesthesia.

The problem that The Retrievals deals with is epidurals failing during cesarians, which, they're quick to emphasize, is painful, open abdominal surgery. The not-so-simple solution is to convert to general anesthesia (anesthetic gas, IV propofol, etc). This isn't without its risks to the mother and the child, so there's reluctance on the part of anesthesiologists to go that route if there's other options. The result is unnecessary birth trauma.

There's selection bias. High risk deliveries tend to start at or convert to cesarian at the first sign of trouble.

You can pay half that on eBay at the moment.

I downvoted the original comment because grammar pedantry adds nothing here. But if you're going to correct a pedant, you've got to be right. You're applying a test you don't understand and you messed it up.

"I" is the subject of the sentence, or the person who is doing the thing. "Me" is the object of the sentence, or the thing that is receiving the action. Since he and his friends are the ones who did the building, "I" is the correct pronoun.

Going back to the test you gave, the correct way to apply it is to replace entire the noun phrase with "I" or "me". The noun phrase here was "me and my friends together". "I built an 8 bit CPU" vs "Me built an 8 bit CPU". The former is the obviously correct one.

Even those annual blood tests can be problematic.

When I first started getting annual blood tests there were two values in particular that were consistently elevated. A bunch more tests and some specialist visits later the explanation was that I have a harmless genetic mutation that just causes those values to be high.

A few years back I had some different values pop high. They implied scary things. More specialist visits than before. A lot more tests. After months of that all of the scary things were eventually ruled out. And then the values went back to normal. Nobody has an explanation even now.

This is just with a pretty standard battery of tests: CBC with differential, comprehensive metabolic panel, lipid panel, TSH with reflex, vitamin D. They catch enough bad things that they're generally worth ordering on a regular basis for healthy people at annual physicals. The occasional wild goose chases like what happened with me is the price we pay for catching the more serious things.

I guess we'll see just how valuable monthly whole body ultrasounds are. There's a real risk that it will catch a lot of benign things without catching enough serious things.

I did an undergraduate electrical engineering degree some years ago. Building a CPU much like this one was the final project in our second digital design class. The difference here from the usual approach, as they point out, is that this is a gate-by-gate design you could assemble out of 74-series logic gates on a breadboard rather than the more common Verilog/VHDL designs that target FPGAs. Definitely a more tedious, time consuming approach, but I'm not convinced it's more conceptually difficult. By the time you're building a CPU, you've probably already built the component parts like the adders out of pure logic gates, anyway.

Not to say that this is easy, but I think you'd find that a whole lot more people are doing this kind of thing than you might think.

I wasn’t talking about military parades.

In my experience as an American, most of the parades I'm personally familiar with are organized by local groups rather than the government. Maybe you can read some ideology into the American Legion marching with flags, but it's more an exercise in giving the local high school band a chance to march, the Shriners an excuse to break out their clown cars, and maybe the whole thing is an advertisement for the 4H or FFA fair. That's not to say that the US doesn't have parades in the genre the article talks about—the Army 250th Anniversary Parade probably counts. But not every parade is a propaganda exercise.

> We're not anti-gun. Just anti the "only used explicitly for killing people" kind of gun.

That doesn't square with Canadian classifying tasers (purely defensive, non-lethal) and anti-materiel rifles as prohibited firearms. Not that those kinds of bans don't have some sort of legitimate public policy basis, but there's something else going on here.

With very few exceptions, you can’t acquire handguns in Canada anymore. They’ve also banned most semiautomatic rifles.

Maybe Canadian public opinion isn’t anti-gun, but the current government seems to be.

There's this notion from the Supreme Court case Burdick v. United States (1915) that accepting a pardon is an implicit admission of guilt. Therefore, a person can refuse a pardon. There isn't anything in the decision to justify the argument that accepting the pardon is an admission of guilt, it's just stated as a fact. It seems at odds with situations where pardons have been used to correct miscarriages of justice in cases of factual innocence.

Clocking in and out serves little purpose if you're salaried.

I wear Lycra, ride a funny-looking carbon road bike, and average about 3,000 miles a year. In college, I rode a beater bike everywhere for transportation instead of owning a car. I’ve never experienced that kind of thing, though I’ve heard occasional stories.

Drivers don’t pay attention and seem like they’re trying to kill you, but that feels more like recklessness than malice.

I recently had an experience with a family member's Ubuntu LTS machine where it was stuck on an old release, /etc/apt/sources.list needed to be edited because of Ubuntu's obnoxious habit of breaking old repositories, and then I needed to debug apt issues to get do-release-upgrade to actually work.

The Macs and iPads have their own problems, but nothing like that.

I think I'm probably coming at this from a different perspective than IT people.

I've worked on IoT products where we've deployed fleets of thousands of devices without user interfaces placed all over the world in random, inaccessible places, hanging off cellular radios. We're definitely not managing those manually. Architecting management systems for that is always interesting. Sometimes the question would come up, "why don't we do X?" where X necessarily included the ability to brick the entire fleet (and probably kill the company) in 5 minutes. My philosophy was that certain things are too dangerous to exist, no matter how useful they might be.

I think IT departments also tend to underestimate the risk they pose when they manage machines. Look at Stryker, where intruders used Intune to wipe all the company's devices. The ability to do that shouldn't exist, but the IT department happily rolled out the means of their own destruction in the name of compliance and making their lives easier.

Don't. The USB C port is poorly designed and will break at the drop of the hat, leaving you unable to charge the thing. And the company won't do anything to help you.