4 ms·

This looks kinda cool. I have a hard time believing this is "for web developers" when most web developers used `.dev` for local development, which was broken b

This looks kinda cool. I have a hard time believing this is "for web developers" when most web developers used `.dev` for local development, which was broken because Google decided they wanted to own `.dev` for themselves. Bad taste in my mouth.

crooked-v 8y ago
> when most web developers used `.dev` for local development Most web developers were wrong. The reserved TLD for local development has been .localhost since 1999.
- CydeWeys 8y ago
  Or .test. See RFC 2606: https://tools.ietf.org/html/rfc2606 https://tools.ietf.org/html/rfc2606
  - shkkmo 8y ago
    I think .test is the TLD is the one most likely to work as expected as for all use cases as .localhost might be expected to only ever point to the loopback IP address. If anyone does something more complicated (like using a vagrant private network ip address), you might find some tools break unexpectedly. Edit: the newer version of the docs have more details (in section 6) on the differences to be expected between test, localhost, example and invalid domains. see: https://tools.ietf.org/html/rfc6761 https://tools.ietf.org/html/rfc6761
NelsonMinar 8y ago
It might be time to let this one go.
- Sir_Substance 8y ago
  Some of us are still tickets once a month or so over this. Kinda hard to let it go.
- omeid2 8y ago
  Slowly boiling the whole web.
gruez 8y ago
>Bad taste in my mouth. how's this any different than devs using 123.123.123.123 for test purposes (instead of private network addresses), then getting upset when they found out it has been allocated to China Unicom?