4 ms·

> The answer of course is to petition the Internet Darling Google... > Why? Who knows. Maybe because Android is “open”, whatever the hell that means. Maybe it

> The answer of course is to petition the Internet Darling Google... > Why? Who knows. Maybe because Android is “open”, whatever the hell that means. Maybe it is because Google is strongly pro-net-neutrality, and Apple has made their customary “no comment”. Maybe because Google employees have blogs. The world may never know. What? Did this person even read PPK's rant? He was saying the group that could force Apple's hand on Pointer Events is Google, and then proceeds to give explicit reasoning for this. No need to speculate on invent a convenient strawman for the rest of your post. It has nothing to do with hand-wavey openness, it's that they are the developers of the other browser that makes up a huge chunk of the mobile web. If they supported PE, over time it would certainly put some pressure on Apple (though situations like WebSQL/IndexedDB indicate that the pressure might not be that effective). The rest of this is nonsense. A closed TLD is not an attack on the open internet. Honestly, who on earth cares. You couldn't get a .dev address before, you won't be able to get one now. Personally I don't think they should have opened up TLDs in the first place, but, whatever. Meanwhile, quotes like > This is a methodical, coordinated, long-running and well-planned attack on the open web that comes from the highest levels of Google leadership make this article more than a little bit of a joke.

bsimpson 12y ago
I can't help but wonder if they registered `.dev` because they have it internally routed on their corporate network now, and they don't want to all of a sudden have to deal with an employee not being able to read an article on a new blog help.dev because they also have a product called Help being tested at the internal URL help.dev. If that's the case, them registering `.dev` might help everybody. It will give you a TLD that you can use for internal projects, knowing it will never conflict with a real site. Considering Apple's asinine handling of .local domains on iOS, a known-good alternative TLD could be a good thing.
- geofft 12y ago
  Yeah, that was my first thought -- if Google registers .dev and keeps it in-house, this is good for the open web everywhere because we can all use it internally. Probably they can't say that to ICANN's face, but that sounds like it could have been a plausible intention all along. In fact, if Google registers .dev and promises to keep it in-house, they can then tell the Chrome team that it's okay to trust self-signed certs for .dev, or something, thereby letting us all use HTTPS for development.
  - Kalium 12y ago
    That... actually sounds hugely valuable for software houses everywhere.
  - emmelaich 12y ago
    You won't be able to use it internally unless you get split DNS and mangle your dns lookup configuration. Everything .dev resolves to 127.0.53.53 now. That ip address is a shot across the bow to warn you of the impending TLD registration. $ host blahflurgle.dev blahflurgle.dev has address 127.0.53.53 blahflurgle.dev mail is handled by 10 your-dns-needs-immediate-attention.dev.
    - geofft 12y ago
      You're going to have to set up split-DNS anyway if you want the records to resolve, right? Otherwise they would all NXDOMAIN.

bsimpson 12y ago

I can't help but wonder if they registered `.dev` because they have it internally routed on their corporate network now, and they don't want to all of a sudden have to deal with an employee not being able to read an article on a new blog help.dev because they also have a product called Help being tested at the internal URL help.dev. If that's the case, them registering `.dev` might help everybody. It will give you a TLD that you can use for internal projects, knowing it will never conflict with a real site. Considering Apple's asinine handling of .local domains on iOS, a known-good alternative TLD could be a good thing.

geofft 12y ago
Yeah, that was my first thought -- if Google registers .dev and keeps it in-house, this is good for the open web everywhere because we can all use it internally. Probably they can't say that to ICANN's face, but that sounds like it could have been a plausible intention all along. In fact, if Google registers .dev and promises to keep it in-house, they can then tell the Chrome team that it's okay to trust self-signed certs for .dev, or something, thereby letting us all use HTTPS for development.
- Kalium 12y ago
  That... actually sounds hugely valuable for software houses everywhere.
- emmelaich 12y ago
  You won't be able to use it internally unless you get split DNS and mangle your dns lookup configuration. Everything .dev resolves to 127.0.53.53 now. That ip address is a shot across the bow to warn you of the impending TLD registration. $ host blahflurgle.dev blahflurgle.dev has address 127.0.53.53 blahflurgle.dev mail is handled by 10 your-dns-needs-immediate-attention.dev.
  - geofft 12y ago
    You're going to have to set up split-DNS anyway if you want the records to resolve, right? Otherwise they would all NXDOMAIN.