The historical definition of the word vulgar was more or less equivalent to "mainstream" or "in common usage," so... yes, hundreds of years ago.

You've got your morality wires crossed on this.

Eating meat is taking an organ from an animal for your own benefit, however brief that may be. In this case, we are pretty much doing the same thing, except that that organ will serve a purpose for longer than it takes to pass through a human's digestive tract. I can also imagine this sort of tissue engineering research bringing us closer to viable lab-grown organs which could lead to practical lab-grown meat, ultimately reducing animal exploitation though this is speculative and a long way off. Even if that never happens and we are mass-breeding pigs for organ transplants, the number of pigs used for this in the next 25 years will be far less than what the US kills for meat production in a month. Also, it's not like the rest of the pig will be wasted; I wouldn't want to eat medically sourced pork, but I'm sure it will make its way into the pet food supply chain.

I’m sorry but what the heck are you talking about? Static typing reduces the number of tests you write because the type system itself guarantees thing like a toString() call actually returns a string. Dynamic typing can help you test really untestable code due to its flexibility, but stubbing isn’t exactly an unsolved problem in static land.

It forces EC2 users to think about whether their hosts actually need a public IPv4 address. Most services really only need a couple for their load-balancers and NAT gateways; every other host just lives happily in your VPC without a public address. I just checked my company's infrastructure, and in us-east-1, we have a grand total of 6 public IPv4 addresses, and this is for a very large deployment. Of course there are other regions, our on-prem addresses, and so on, but for even somewhat badly planned out AWS deployments, this should be less than $100/month

These kinds of tools work okayish for single users willing to jump through hoops. For even marginally more complex use cases, the ease of use of cloud-managed password managers more than outweighs the slightly decreased security. Bitwarden for example is still very secure, as well as being open-source, audited, etc. there's even Vaultwarden, an independent reimplementation of their server, available as well as a cli client if that's your thing. It has sophisticated organization support which lets me easily implement family sharing for certain credentials. If my wife needs the Amazon password, my response is "It's on Bitwarden," any tool that doesn't match this level of useability is essentially worthless to me.

I think you're overthinking this. Every other cloud password manager has a Chrome extension already; not having one would render the products largely useless. The extensions don't feed into the Chrome password manager, they directly operate on web pages, looking for username and password fields and populating them (if you have autofill turned on) based on whatever passwords are bound to that URL.

I'm not saying implementing a browser extension for a password manager is trivial, but it's a problem that's been solved many times. Knowing a bit about the internal processes at Apple, this feature has certainly been through several rounds of design, security reviews, etc.

Like a propane tank swapping service any viable battery service would need to maintain the batteries and retire or recondition ones with a high number of dead/dying cells. I'd imagine something even at 80% capacity would be well past the threshold for needing service.

There is one upside to the tank exchanges: you can swap out expired tanks. So for $20 and an expired tank, you can get a fullish tank with like 10 years left on it and then go back to filling it at the U-Haul store, Ace Hardware, or whatever else sells cheap propane. Recertifying a tank is $15-20 on its own, is only good for five years, and you have to actually find a place that does it.

He commented on this on this a few days ago https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fold.reddit.com%2Fr%2Fapoll.... This change was made before everything completely fell apart. I'm guessing that's a Canadian screenshot which would account for the price discrepancy vs what is discussed in the thread.

Why spend $4 on an energy drink when you can get the same taurine from a can of cat food for 50 cents?

The part you are alluding to but glossing over a bit is that divide-and-conquer sorting algorithms (e.g. quicksort) function by breaking up a large sorting problem into many smaller sorting problems, eventually arriving at a point where they must sort many small lists. Because of this, optimizing these small sort operations will improve sort performance for inputs of any size. Also, lists don't need to be an integer multiple of the sort-n in size for a faster sort-n to get benefit them; the sizes of the sub-problems in a typical sorting algorithm are generally random, and at the end stages of the algorithm, you'll end up with lists of varying single digit sizes.

Would you be willing to bet a kidney that a well resourced actor could not recover data from those wiped drives? I know how to securely erase a drive to the extent that it is possible to do so, but if customer data ever lived on the same rack as that drive, thereâ(TM)s not a chance the device is leaving the data centre except as confetti.

TRIM isnâ(TM)t a security feature and doesnâ(TM)t necessarily wipe the backing memory, it just tells the SSD that itâ(TM)s no longer considered in use and the data thereâ(TM)s no longer needs to be preserved. Subsequent garbage collection cycles will probably wipe the memory but thereâ(TM)s no guarantee on when or if that happens.

Not only was it authentic tech gibberish, it expressed a courage little seen in this day and age.

Perhaps because it's a poorly worded headline or maybe in this age of subscription-based software, tech journalists working for mediocre websites like cnet think it necessary to call out that the license doesn't expire, unlike that licence for JetBrains products I fork out for year after year (though to be fair that does come with a perpetual fallback license).

Regardless, an Office 365 subscription also allows for installing the native versions of Office apps in addition to the browser-based versions. Microsoft has for years sold access to Office as both a subscription and as a perpetual license to a specific year release (2021, 2019, 2016) without access to the cloud version. Either way, you get more or less the same product with the subscription giving you access to the latest versions of everything, whereas the perpetual is bound to a specific "year". I don't know why you, seemingly not really knowing much at all about MS Office licensing, would be willing to take the multiple deductive leaps to arrive at "this license requires you to use the web version of Word but only from a web browser on a specific computer running a specific operating system".