Live data from Hacker News

Google .dev domain early access

domains.google

91–100 of 475 posts

Re: Google .dev domain early access

#91
post #73

Earlier quoted context omitted.

I recently found out that the sidebar menus on pages within https://developers.google.com/web don't work with JS off (usually a trivial thing: show sub-items by default and hide them with JS). Almost every Alphabet website has something like that. So yes, minor anecdote, and I genuinely appreciate the hundreds of Google employees who really help the Web and share useful knowledge (and don't lead developers into using…

Not working with JS disabled is bad, but not working on a major modern browser is ridiculous.

Safari is the new IE8.

Every web dev I know bitches about it.

Re: Google .dev domain early access

#93
Does anyone know how the “premium” renewal prices are set and governed? I’m going through this right now with .app domains (also owned by Google). Apparently domains categorized as “premium” have a much higher yearly pricing, and how it’s priced is not specified anywhere on the registry website. I called a few registrars and they said that the premium pricing is set by the registry. What’s concerning is that the registrars admitted that there really isn’t anything stopping the registry from increasing the premium pricing at will.

Anyone have anymore info about this? Seems concerning that a registry has no restrictions on what they can do with pricing after an individual has invested into an expensive domain.

Re: Google .dev domain early access

#94

How long until Google will start removing domains that don't fit their "values"?

What if they remove domains owned by open source projects that refuse to implement a CoC?

I don’t think they will, but buying a domain from a company that’s so involved in politics doesn’t seem wise.

Re: Google .dev domain early access

#96
post #12

The .dev TLD worked fine before it was bought. Now we have to use .test or .local. I don't get what Google thinks they'll get out of sponsoring putting sites under development online.

It's always best to follow the RFCs [1] to avoid issues like this. ".dev" worked but it was never safe to use it.

1: https://tools.ietf.org/html/rfc2606#page-2

Re: Google .dev domain early access

#97
post #12

The .dev TLD worked fine before it was bought. Now we have to use .test or .local. I don't get what Google thinks they'll get out of sponsoring putting sites under development online.

If you've any developers on your team that use MacOS, avoid .local since it does some listening on this for Bonjour: https://blog.scottlowe.org/2006/01/04/mac-os-x-and-local-dom... I believe .localhost is the "official" recommended TLD for local development.

According to RFC 2602 [1],

> The ".localhost" TLD has traditionally been statically defined in host DNS implementations as having an A record pointing to the loop back IP address and is reserved for such use. Any other use would conflict with widely deployed code which assumes this use.

So it might work but it could be problematic if the intent is to use ".localhost" as a local network domain rather than just the local host.

[1]: https://tools.ietf.org/html/rfc2606

Re: Google .dev domain early access

#98
post #85
post #70

Earlier quoted context omitted.

> But the three big public deprecations I'm aware of are Reader, Inbox, and G+. Google Code. Also Wave and half a dozen chat apps, but Code was a serious one that broke a lot of the developer web.

>Google Code. Also Wave and half a dozen chat apps, but Code was a serious one that broke a lot of the developer web. What did it break?

It hosted repos, and broke links to those repos and links within them. It also broke processes that relied on the repo, e.g. automatic issue creation in CI, but that's less serious.

URLs that change without good reason are a PITA.

Re: Google .dev domain early access

#99
post #60
post #18

A domain just for developers! Until it abruptly shuts down Feb 19, 2021. Why would anyone trust Google with something with any kind of long-term requirements as important as a name? They should have registered ".chump" instead, because that is really what users of a Google-managed TLD are declaring "Dear VALUED developer, thanks so much for being a part of the .dev experiment! After a long hard period of staring at o…

Somebody makes this post on every HN thread involving Google now. But the three big public deprecations I'm aware of are Reader, Inbox, and G+. All consumer products. All the other stuff on that killed by Google site is stuff I've barely even heard of, and all consumer products. To my knowledge, no major GCP component has ever been deprecated. Am I missing something? This seems like it has just become a groupthink HN…

You haven't been watching long enough https://cloud.google.com/appengine/docs/deprecations/
Post reply on HN