Google owns the .dev TLD, and they bought it for entirely internal use. People got upset about this (any company owning a TLD for internal use only is pretty weird, and especially one as generic as ".dev") so they started to offer it to the public.
The bigger issue is that a lot of people use .dev for internal/development uses, and it should therefore never been made into a "real" TLD in the first place. It's like deciding to sell "example.com" to someone.
I could've swore .local was okay, as that's what I use. But maybe not. Apparently it can cause issues with Macs, but that's new to me seeing as how I primarily develop on one.
I registered a .dev for my company, but because it's a company of one I imagine this won't affect me then. Good to know though. I do recall using .dev for local/internal development years ago...
EDIT: so would this mean that registering a .dev for some BigCo domain could potentially cause problems? Curious what the real-world implications might be.
I don’t think there are really any implications moving forward. It only affected developers in the first place. Developers have since been forced to stop using .dev for development, thanks to the existence actual .dev domains.
Yeah, at this point the horse is out of the barn, so don't worry about registering a .dev. Any damage that would be done has already happened. The point is it shouldn't have happened in the first place.
Developers have been using <something>.dev as their localhost hostname even though the .dev TLD wasn't a designated test/reserved TLD[0]. Everyone's non-https development environments broke when Google added the TLD to HSTS preload, forcing browsers to load it in HTTPS.
The bigger issue is that a lot of people use .dev for internal/development uses, and it should therefore never been made into a "real" TLD in the first place. It's like deciding to sell "example.com" to someone.