Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google .dev domain early access

domains.google

Post reply on HN
Print view View original

61–70 of 475 posts

Re: Google .dev domain early access

#61

Post by luckylion »

bhartzer wrote: post #42
pexaizix wrote: post #35

Earlier quoted context omitted.

Yeah, well. That's got nothing to do with .dev. All the new TLDs are fucking dumb. Just a cash grab for the ICANN. Might as well get rid of TLDs altogether.

Honestly I don’t think it’s a cash grab for icann. There are plenty of registries that are making plenty of money, as well as domain owners selling the domains in the aftermarket. The reason the new tlds were needed is the lack of options for buying a new domain. I know plenty of smaller biz and startups who couldn’t get the dot com they wanted and ended up choosing a really good keyword rich new tld.

> Honestly I don’t think it’s a cash grab for icann.

Wasn't it $10k upfront to have your application for a new gTLD considered? This times ~1200 ... works out quiet good.

Re: Google .dev domain early access

#62

Post by ninkendo »

delinka wrote: post #32
jtreminio wrote: post #25

Earlier quoted context omitted.

Chrome requires an SSL certificate for all .dev hostnames.

if you have the technical savvy to be using .dev before the Google deployment, you have the technical savvy to install an additional root cert for use with Chrome.

That is such specious logic it’s kind of sickening.

I use TLDs like .dev exactly because it’s convenient. Not because I’m “savvy”, and even if that were true, it doesn’t follow that it would be just as convenient to set up a local CA.

Using `echo ip >/etc/resolver/dev` to have a custom dns server for everything in the .dev domain is trivial. It’s one command. Getting a custom CA for all of that is not.

Re: Google .dev domain early access

#63

Post by wolco »

aboutruby wrote: post #29

Pretty sure the first domains acquired will be targeted at local development setups, like tmp.dev, staging.dev, production.dev, etc. etc. edit: just a reminder that .local is the reserved one https://en.wikipedia.org/wiki/.local

I've been collecting country level three character long domains and using them. I suggest everyone does the same.

Re: Google .dev domain early access

#64

Post by dpwm »

gkoberger wrote: post #43
_wmd wrote: 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…

I mean, I get your point, but I think this is a meme exclusive to HN. Other than Google Reader, there really isn't much Google has shut down without having a newer, better product you can transition to. When it comes to something like this (AKA not a consumer product, makes money, relatively easy to run, etc), I genuinely can't see them shutting down a TLD like this. If anything, the complaint should be the lack of o…

Google Wave shut down without a replacement google service. [0]

Google code shut down without a replacement google service. [1]

Google plus is shutting down too. [2]

[0] https://support.google.com/answer/1083134?hl=en

[1] https://opensource.googleblog.com/2015/03/farewell-to-google...

[2] https://support.google.com/plus/answer/9195133?hl=en

Re: Google .dev domain early access

#65

Post by thaumaturgy »

gkoberger wrote: post #43
_wmd wrote: 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…

I mean, I get your point, but I think this is a meme exclusive to HN. Other than Google Reader, there really isn't much Google has shut down without having a newer, better product you can transition to. When it comes to something like this (AKA not a consumer product, makes money, relatively easy to run, etc), I genuinely can't see them shutting down a TLD like this. If anything, the complaint should be the lack of o…

You may've missed the recent news on Google Fiber pulling out of Louisville (https://news.ycombinator.com/item?id=19106998) as well as Google Plus shutting down.

Some folks make a hobby out of the stuff Google spins up and then abandons: https://killedbygoogle.com

Re: Google .dev domain early access

#67

Post by ninkendo »

fastball wrote: post #54
sascha_sl wrote: post #37

Earlier quoted context omitted.

What about internal use in organizations? Sorry but this is pure malice by Google. I can invert this argument by saying if you're buying a .dev domain you have the technical savvy to get on an HSTS preload list, except you haven't broken anyone's workflow. EDIT: And I mean... have you USED openssl's x509 toolchain? That's a few steps up from editing the hostsfile.

Editing the hosts file isn't a solution for internal use in organizations. If it's just you, editing your hosts file, switch to .local or whatever. There was always a chance when using a "local" domain (which isn't actually some sort of standard) that such a TLD could be created in the future. If it's for an organization, create the root cert, and have that be one of the steps users need to take in order to access th…

.local is reserved for multicast DNS/zeroconf, by the standard. You literally can’t use it on macos because it will always try to look it up in with mDNS first, and only fall back on /etc/hosts once that fails.

If you use .local for fake DNS for a dev setup, you’ll probably notice lookups are slow; that’s why.

(This is why I’ve always used .dev actually, although this may make me switch to .fuckgoogle or something instead)

Re: Google .dev domain early access

#69

Post by sascha_sl »

fastball wrote: post #54
sascha_sl wrote: post #37

Earlier quoted context omitted.

What about internal use in organizations? Sorry but this is pure malice by Google. I can invert this argument by saying if you're buying a .dev domain you have the technical savvy to get on an HSTS preload list, except you haven't broken anyone's workflow. EDIT: And I mean... have you USED openssl's x509 toolchain? That's a few steps up from editing the hostsfile.

Editing the hosts file isn't a solution for internal use in organizations. If it's just you, editing your hosts file, switch to .local or whatever. There was always a chance when using a "local" domain (which isn't actually some sort of standard) that such a TLD could be created in the future. If it's for an organization, create the root cert, and have that be one of the steps users need to take in order to access th…

Maybe you've never been in an environment where having to change internal domains is near impossible.

I work at the intersection of 3 corporations within our group. We provide a sort of "internal Heroku" using Kubernetes for anyone in the group that needs it. We recently ran into the 63 character limit on domain name labels (we have to use a wildcard cert because nothing else is approved by legal). You wouldn't believe the time developers would've had to spend on fixing the domain schema across hundreds of services if we hadn't found a way out of that dilemma. We're talking thousands of internal names, some of them given our to external partners (we use a partially publicly resolvable name, but we could've exposed our DNS as well) and some used in systems long forgotten.

Re: Google .dev domain early access

#70

Post by ebg13 »

gipp wrote: post #60
_wmd wrote: 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…

> 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.

Post reply on HN