I don't see myself as that averse. To me, if they found a clever domain hack, or if the name is such that the TLD is part of it (like
https://teenage.engineering) - sure, go for it. Happy to see it actually! Gives it character and shows that a modicum of thought was put into the choice. For the website of my gamedev team (called secret industries) I was happy to see .industries being a TLD. Quite long, but easy to remember if you remember the name.
For personal use, as long as the TLD has a decent enough reputation to use with email (https://www.spamhaus.org/reputation-statistics/), I'd be fine with almost whatever, too. I personally use a ccTLD, but things like Jeff Gerstmann's site (https://jeff.zone) are fun. There are tons of other examples, this one just came to mind first.
What does feel dodgy and fake to me is when I see a known name with the new gTLDs. Sometimes SaaS have their landing/marketing site on a different TLD than the app itself. If you find both via web search, that looks weird to me.
The city TLDs and highly specialized or non-English ones (like .kaufen, .whoswho, .abogado) and the tons and tons of paid subdomains are so rare that they always seem out of place.
For personal use, as long as the TLD has a decent enough reputation to use with email (https://www.spamhaus.org/reputation-statistics/), I'd be fine with almost whatever, too. I personally use a ccTLD, but things like Jeff Gerstmann's site (https://jeff.zone) are fun. There are tons of other examples, this one just came to mind first.
What does feel dodgy and fake to me is when I see a known name with the new gTLDs. Sometimes SaaS have their landing/marketing site on a different TLD than the app itself. If you find both via web search, that looks weird to me.
The city TLDs and highly specialized or non-English ones (like .kaufen, .whoswho, .abogado) and the tons and tons of paid subdomains are so rare that they always seem out of place.