Hacker Newsnew | past | comments | ask | show | jobs | submit | more waiwai933's commentslogin

That must be a typo in the title; .wed continues to be operated by the emergency backend registry operator.

https://www.icann.org/en/blogs/details/next-steps-for-the-we...

https://registrars.nominet.uk/gtlds/ebero/


http://nic.wed redirects there.

Maybe ICANN had a heart and decided not to break unsuspecting people's wedding sites lol


I believe this is similar to EC2 Fast Launch which is available for Windows AMIs, but I don't know exactly how that works under the hood.

https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/win-a...


It does launch an instance and take a snapshot but what's happening is the sysprep and OOBE stuff that can take 10 mins or so (you can find it in the console and startup logs). That's a lot more overheard than just hydrating an EBS volume.

https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/win-a...


I'd simplify the guidance on using full/short hashes to:

* Automated use? Always use full hashes

* Human use? Short hashes are usually fine, but a full hash doesn't hurt (and please make it available in a link/hovertext)


I'd simplify the guidance even more: short hashes are fine if and only if the repository hasn't been modified since they were generated (AFAIK, git automatically increases the length of the short hash it displays whenever it would otherwise cause a collision).


I'm not sure that's necessarily practical though - if I'm dropping a link in Slack to a colleague

> You want to look at [a123456](some.git.url/a12345678...) to see where we've done this before

I can't promise that the repo won't have changed by the time they look at it (but because the full hash is linked, it's not a problem in practice).


R2 bandwidth is free, but storage is not.

R2 also doesn't have all the features that S3 does - including an equivalent of S3 Glacier, which is cheaper storage than R2. R2 also doesn't have object tagging, object-level permissions, or object locking. Sure, you could build your own layer in front of R2 that gives you these features, but are you necessarily saving money over just using S3?


Anyone know why the rule against perpetuities wouldn’t apply? Also, is there anyone who could meaningfully enforce this covenant? I appreciate that you wouldn’t necessarily want to risk it anyway, but just to ensure I understand the issue here.


The rule against perpetuities places some limitations on the creation of future interests in land. The kind of covenant in this case doesn't create a future interest.


Presumably someone has a claim for damages if the covenant is violated, in which case they have a future interest in it. If no-one can enforce the covenant, well, it might as well not exist.


Have you bothered to research this at all or are you under the impression that arguing about it on HN will somehow make you right?


This is no longer necessarily true in the EU as of last month - https://developer.apple.com/support/alternative-browser-engi... - though I don't know if any browsers have in fact changed their rendering engine from Webkit yet.


That works while OpenTofu and Terraform files are compatible - but once they no longer are, presumably you'd have to standardise on one or the other.


The point is that once they are no longer compatible, people would standardize on the one that they're familiar with which is most likely the one that's running on their machine.


There are enough pretty annoying and long standing terraform issues that if opentofu started picking them off I'd consider switching.

You can kinda see this with vim and neovim where both are continuing to exist and benefit each other.


Encrypted state files are either done or coming soon. That's going to be a big one, since Hashicorp used that as a selling point for Terraform Cloud.


But currently, people are equally comfortable with both; the CLI commands are exactly identical between the two, save for the name of the binary itself. In any org where both are in use, if people are forced to choose at some point, they will have to balance many other factors besides familiarity, such as features and confidence in the platform.


Part 2 does


The UK energy market is complicated.

The high-voltage transmission grid is operated by National Grid, which is a British company. Distribution to end-users is operated at a regional level by one of six* Distribution Network Operators [1], three of which are British-owned.

Consumers can purchase electricity from any electricity supplier that is willing to sell to them. Naturally, since it all goes into one grid, suppliers are responsible for ensuring that they purchase from generators and sell to consumers an equal amount of electricity. EDF is one of several suppliers in the market. (There were many more until energy prices rose following the Russian invasion of Ukraine and many suppliers collapsed.)

The gas distribution system works similarly, but I'm not familiar with the details.

* It's slightly more complicated, but it rounds to six.

[1]: https://en.wikipedia.org/wiki/Distribution_network_operator



I want a CIA coffee mug so bad


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: