petree

AWS' Nitro platform is no longer based on Xen and the Xen stuff is being replaced/deprecated, including moving some of the old Xen instance types to run on Nitro instead of Xen.

Latin 1 doesn't cover all languages that use a Latin script, and has an incomplete character set for others.

Sometimes the lack of diacritic can change the meaning of the name for the worse and either way, names are deeply personal things that people are attached to, so they might want to have it written correctly, regardless. I wouldn't want someone to mispell my name.

Sure, it is definitely more expensive than I would like. But you still have the option to watch the ads if you don't like paying a sub. Expecting it to be completely free is unrealistic though.

Having a loss leader like this is exactly monopolistic behavior though. The fact that Google are trying to make money from it is expected and more fair to their competitors than just having it completely free, and not having ads either.

You can use NoScript to disable JS and see how well that works.

But more to the point, yes, a browser is a client, but without the economic incentive of either ads or direct monetization from users, many sites, YouTube included, would simply not work. Storage and bandwith costs money. Unless we decided to somehow fund all of this through some sort of additional tax through the ISPs or governments, ads or subscriptions are a necessary evil.

Beyond being way less carbon intensive and less polluted, they're objectively better places to live.

I think I first found this site around 2007 or 2008. I've been using Ian's Secure Shoelace Knot ever since.

An open source maintainer is a person volunteering their time and resources to offer something usually free of charge. As such, they decide what usecases they want to support and for how long. You can't expect someone to do work for free to support you.

There is a very good reason: the maintainers want to make the change. They don't even need a good technical need to do it, but usually there is at least something that drives the change.

Either pay someone to maintain it for as long as you need or engineer around whatever issues you encounter; it's a you problem, and possibly the development process or software stack you are using is not flexible or robust enough to support your own usecase. Unless you specifically pay for how many years of support you need, then you don't get to decide the terms of whatever support is offered for free.

They're not really VMs. They are metal instances, which run without a hypervisor, but have virtualized network and storage attached instead.

A star is just a giant fusion reactor. We just need to add more fusion material (hydrogen) and remove the waste material, which gathers in the core and makes it more difficult for the fusion reaction to continue. It would be possible to prolong the life of the Sun for a while by adding more hydrogen to it, and ideally taking out the heavier elements at the center, which might also be valuable on their own. This seems pretty impossible today, but given we survive enough time until this becomes a problem, then we might find ways to also fix it.

You're right, it's not believable that only 1/3 don't know the rules, most likely it's 2/3 of people that don't know the rules, given how people drive.

Firecracker uses KVM, but KVM is only part of the equation. KVM exposes some very basis functionality (vcpus, memory) that an application like Firecracker or rust-vmm (or more commonly QEMU) use to create a Virtual Machine. The Virtual Machine usually needs additional components that are outside of the scope of KVM, such as serial ports, disks, network interfaces, BIOS which the VMM emulates. In the case of Firecracker, the emulation layer is much simplified and doesn't necessarily aim to replicate a real machine (QEMU sort of does), but one that has the bare minimum to function. This is done so that it's faster to boot and uses less resources overall.

I'm not sure this answers your questions exactly, there are good reasons to sometimes use a more faithful emulation of a real machine, but it's also sort of legacy for many of the cloud use cases like multi-tenant architectures, where VMs are mainly used to keep hard boundaries between customers.

For me 21:9 is the ideal resolution right now. It can be split in 2 or 3 screens side-by-side and it still works well. A single 4:3 doesn't really give a lot of flexibility in the same way and bezels are annoying.

3:2 is very close to a 16:10.

Sounds like great customer service from Tesla, the most valuable car company in the world... Hopefully people can at least recover their money easily.

You install Linux and tell Microsoft to fuck off with their stupid ideas.

It can't scale up if it still needs to be produced in the same quantities. It takes a lot of farmland, about 80% in fact, to produce feed for livestock (especially for cattle) even with calorie-dense feed like cereals. You'd have to cut down a lot of forest to make pastures.

The whole world economy relies on 3 countries in balistic rocket range of each other; not great. Having foundries distributed around the world sounds way more resilient to any conflicts or disasters that might arise in that particular region.

Having expicitly optional/nullable types is great in languages which are religious about it, since they remove a lot of useless branching and complexity from the code. If it's just tacked on, then it just tends to look ugly, without solving any problems.

I think the issue there is that versions are arbitrary and being able to tell when a library is 1.0 is a non-decidable problem. There are lots of 0.x crates which are stable and feel feature complete, but aren't specifically versioned as 1.0.

I would actually prefer if the Rust std would not include functionality that's not essential, for example sockets don't seem essential and the standard library does not implement them in a particularly complete and well thought out manner either IMHO.