Share this page!

Enter Twitter Thread URL to Unroll

Needs to be the full URL like: https://twitter.com/threadreaderapp/status/1644127596119195649

How to get URL link on Twitter App

  1. On the Twitter thread, click on or icon on the bottom
  2. Click again on or Share Via icon
  3. Click on Copy Link to Tweet
  4. Paste it above and click "Unroll Thread"!
  5. More info at Twitter Help
Gergely Orosz Profile picture
@GergelyOrosz
Jun 16 • 8 tweets • 3 min read Twitter logo Read on Twitter
Wow: Google IS killing Google Domains; selling it to Squarespace.

This is 10 million domains sold. Millions of customers like me learn again (and again!) that you cannot trust Google to keep their own products alive.

Show me another vendor that throws away customers like this…
Source of news:

I didn’t become a Google Domains customer to be handed over to Squarespace who will move me to another product and then bombard me to build a Squarespace site.

Cannot believe Google screwed me, as a customer, again.

newsroom.squarespace.com/blog/googledom…
I’m sorry but I’ve been burnt by so many things by Google as a customer:

1. Google App Engine, 2011 (lesson: never use Google cloud services again)

2. Nest, ~2019 (lesson: never buy home products from G again)

3. Domains, 2023 (lesson: never buy hosting / domains from G again)
Whats really short-sighted about this move:

These millions of Google Domains customers were techical. Many of them either now or the future decision makers on what cloud solution to choose. GCP? AWS? Azure?

Well, now they all learn what NOT to choose: Google #businessstrategy
Also: as a Google Domains customer, why am hearing about this news from Squarespace’s press release?

Google (my provider, and where I’m a customer) has not told me this is happening.

I assume same with the other 10M impacted domains’ owners.
You don’t need to be a prophet to predict that Google Sites won’t be alive for much longer in the wake of this news. I would not onboard to it: and choose any other vendor instead.

Google is getting itself into this loop where people assume it will kill products - b/c it does!
"Could those domains not have been migrated to GCP?"

Oh but they could totally have! GCP added this feature recently.

Typical Google to sell off all 10M domains to Squarespace, not even offering any of their customers to stay on Google, via GCP.

Ofc should add that this looks like a major win for Squarespace.

They just bought a billion-dollar business, likely on the pennies.

Google charges $12 per domain. Squarespace: $20-70. And in 12 months, Squarespace will raise prices to all 10M domains (the ones that remain)

• • •

Missing some Tweet in this thread? You can try to force a refresh
　

Keep Current with Gergely Orosz

Gergely Orosz Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @GergelyOrosz

Gergely Orosz Profile picture
Jun 15
Interesting to see a swarm of startups that raised VC seed funding to build a thin wrapper around ChatGPT.

While doing so would look like a fair bootstrapped product: I do wonder, where is the venture scale in this? Aka the opportunity to grow into a ~$100M ARR business.
Being a wrapper around ChatGPT is a risk for two reasons:

1. If the use case is truly profitable, OpenAI could just build and sell it themselves, with the next, better version of ChatGPT. They'll see and monitor high-growth use cases.

2. Trivial for a competitor to copy.
Fair observation that for a larger VC fund, making eg 50-100 small investments could be just a way to hedge, and see if 1 or 2 of the group will take off. High-risk, high-reward.

The real winner seems to be ChatGPT where a lot of the funding ends up at!

Read 4 tweets
Gergely Orosz Profile picture
Jun 14
This thread describes a more advanced social engineering scam. It has nothing specific about Coinbase, can be used w any other service.

Never trust someone calling on the phone regardless of phone number: assume it can be a scammer.

NEVER hand over 2FA authentication codes.
These social engineering scams are all similar:

Attackers obtain some personal information that could make it sound they are legit.

Then use pressure tactics (“we’ll have to suspend your account” or similar) to get you to hand over what they need: 2FA, CC info over phone etc.
One good way to reduce changes of being scammed:

Refuse to take *any* action on the phone (share no information)

Tell them to send you an email / a letter or that you will contact them via customer support.

Legit providers will contact you via these means (email, post) anyway.
Read 5 tweets
Gergely Orosz Profile picture
Jun 10
Google already has a major perception problem on how they don’t care much for their cloud customers - not nearly as much as eg AWS or Azure.

Every one of these hard to digest events happening to a big spender - and that big spender moving off - just reinforces this perception.
Every time I say how I don’t trust GCP as infra thanks to having been burnt very, very bad in 2011 as an early Google App Engine customer (when Google showed all their early adopters the middle finger) people from Google assure me a lot has changed in 12 years.

Has it?
As context, Railway is an infra platform where you can provision infrastructure, develop with that infrastructure locally, and then deploy to the cloud. Growing rapidly. They type of “golden goose” customer thanks to ever-growing spend.

That spend will probably not be on GCP.
Read 5 tweets
Gergely Orosz Profile picture
Jun 10
One silent revolution happening that I don't hear much about:

Cloud-based development environments.

A game changer for companies that have this, and can set it up with a few clicks. Allows engineers to change between stacks *with ease* and opens up cross-domain collaboration.
It makes a huge difference for

1. Onboarding

2. Having the same development experience

3. (Ideally) Speed of development

4. Platform teams to measure what things are slowing engineers down

Something that did not exist a few years ago. Now even tools like VS Code support it.
Local dev environments work just fine for small teams/companies.

But get above a certain size, and it is *always* a hue pain to:

1. Onboard a new engineer to a stack/team

2. How that dev can setup another stack (eg another BE service in another repo)

3. How to test, debug etc
Read 4 tweets
Gergely Orosz Profile picture
Jun 9
In the year from September 2021 to Sep 2022, Shopify's stock fell by 79%. This hurt a lot the compensation of employees with stock-heavy packages.

Shopify then introduced Flex Comp, where people could choose how to allocate between cash and equity. What happened next (cont'd) Shopify’s stock price chang...
What happened next is people could decide how much of their compensation target to split between cash and equity, with this tool.

At the time, most people I talked with opted for all cash (or as much as they could). So how did the stock perform since? (cont'd) Shopify’s Flex Comp tool. W...
Well, the stock has done exceptionally well since that point. Easy to look back: but those who allocated more stock definitely saw better outcomes... at least until now.

So should you optimize for cash compensation if you can, or not? My take: blog.pragmaticengineer.com/should-you-opt… Shopify’s stock price chang...
Read 4 tweets
Gergely Orosz Profile picture
Jun 7
It’s disappointing when a company with transparency at its core, and integrity and kindness as values conducts layoffs in an obscure way: employees learning about this from Twitter DMs.

HashiCorp just let go 8%. Investors listening to earnings heard it before most employees.
I am helping out a few people let go by sharing bits and pieces I heard about severance: as HashiCorp has not communicated this in writing.

None of this would be surprising for a company that is known to not be transparent.

For HashiCorp: how this is done goes against values.
Unfortunately, cuts done are not surprising, given the economic outlook of companies.

But ~12 months after mass layoffs have started, there’s little excuse to leave employees in the dark on what is happening, and why.

Do it humanely if it must be done:

newsletter.pragmaticengineer.com/p/preparing-fo…
Read 7 tweets

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

Send Email!

:(