6 ms·

I sort of get the appeal of a '.dev' TLD, but I wish that google donated the whole thing to those who were using it informally for local development. That wou

by denom 8y ago

I sort of get the appeal of a '.dev' TLD, but I wish that google donated the whole thing to those who were using it informally for local development. That would have been a good gift to all the devs out there.

francislavoie 8y ago
There are more devs than just web devs. Just sayin'
- organsnyder 8y ago
  Web devs aren't the only ones that need test/dummy hostnames. That being said, as mentioned in another comment, there are other TLDs already reserved for such use.
Twisol 8y ago
The `.test` and `.localhost` TLDs are already reserved for such purposes: https://tools.ietf.org/html/rfc2606 https://tools.ietf.org/html/rfc2606
- reaperducer 8y ago
  .test is OK, but as was pointed out in the HN discussion on this topic last week, .localhost is problematic in some operating systems.
- dragonwriter 8y ago
  localhost is reserved for a very different purpose, though .local is a reserved pseudo-TLD for a purpose encompassing much of what was suggest by GP for .dev.
  - btgeekboy 8y ago
    .local is for multicast. Don’t use it for anything else unless you want a headache.
    - dragonwriter 8y ago
      That's right,.local was a bad suggestions ; while the notional purpose is specifically residential, the local-use behavior that people are looking for is associated more with the reserved domain .home.arpa if .test isn't desired (.test is technically for testing DNS-related code.)
    - WorldMaker 8y ago
      Or support multicast/mDNS and use .local. I feel like mDNS isn't used enough in general so there are weird cross-implementation bugs in it. (Partly just because of weird overlaps between early Bonjour entities, modern mDNS stacks, and weird-in-betweeners like "UPnP".) A lot more peer-to-peer applications could bootstrap better from mDNS than currently do simply because bootstrapping from known HTTP(S) endpoints is easier and less buggy. I've wondered at times if, say, enterprise adoption of .local and proper mDNS might be a kick in the pants to sort out mDNS and make it better for everyone.
- jolmg 8y ago
  Interesting. Because my /etc/hosts file had the following as a default: 127.0.0.1 localhost.localdomain localhost ::1 localhost.localdomain localhost I thought it was `.localdomain` that was reserved.
  - Twisol 8y ago
    I really thought so too! But I can't find any reference for it.

by denom 8y ago

francislavoie 8y ago

There are more devs than just web devs. Just sayin'

organsnyder 8y ago
Web devs aren't the only ones that need test/dummy hostnames. That being said, as mentioned in another comment, there are other TLDs already reserved for such use.

Twisol 8y ago

The `.test` and `.localhost` TLDs are already reserved for such purposes: https://tools.ietf.org/html/rfc2606 https://tools.ietf.org/html/rfc2606

reaperducer 8y ago
.test is OK, but as was pointed out in the HN discussion on this topic last week, .localhost is problematic in some operating systems.
dragonwriter 8y ago
localhost is reserved for a very different purpose, though .local is a reserved pseudo-TLD for a purpose encompassing much of what was suggest by GP for .dev.
- btgeekboy 8y ago
  .local is for multicast. Don’t use it for anything else unless you want a headache.
  - dragonwriter 8y ago
    That's right,.local was a bad suggestions ; while the notional purpose is specifically residential, the local-use behavior that people are looking for is associated more with the reserved domain .home.arpa if .test isn't desired (.test is technically for testing DNS-related code.)
  - WorldMaker 8y ago
    Or support multicast/mDNS and use .local. I feel like mDNS isn't used enough in general so there are weird cross-implementation bugs in it. (Partly just because of weird overlaps between early Bonjour entities, modern mDNS stacks, and weird-in-betweeners like "UPnP".) A lot more peer-to-peer applications could bootstrap better from mDNS than currently do simply because bootstrapping from known HTTP(S) endpoints is easier and less buggy. I've wondered at times if, say, enterprise adoption of .local and proper mDNS might be a kick in the pants to sort out mDNS and make it better for everyone.
jolmg 8y ago
Interesting. Because my /etc/hosts file had the following as a default: 127.0.0.1 localhost.localdomain localhost ::1 localhost.localdomain localhost I thought it was `.localdomain` that was reserved.
- Twisol 8y ago
  I really thought so too! But I can't find any reference for it.