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

DigitalOcean S-1

sec.gov

Post reply on HN
Print view View original

101–110 of 442 posts

Re: DigitalOcean S-1

#101

Post by jiofih »

yte14 wrote: post #91
fastball wrote: post #88

Earlier quoted context omitted.

You might be experiencing a form of survivorship bias / confirmation bias here. If you work at Linode, presumably people would come up to you asking about something they then couched to you as a Linode clone. That doesn't mean it's how people were talking about DO when not directly speaking with someone at Linode.

I don’t understand how that impacts my point at all. If an opinion is only held in one context it’s not actually held? Is that what you’re saying? I’m sorry, I don’t follow. Before DO VPS was (and somewhat remains) a community even among competition. I’m not basing what I’m saying solely on the example given.

He is saying that your perspective as a Linode employee might not represent how others saw Digital Ocean at the time. Which for me is glaringly obvious from your comments.

EDIT: s/general public/others

Re: DigitalOcean S-1

#102

Post by yte14 »

jiofih wrote: post #101
yte14 wrote: post #91

Earlier quoted context omitted.

I don’t understand how that impacts my point at all. If an opinion is only held in one context it’s not actually held? Is that what you’re saying? I’m sorry, I don’t follow. Before DO VPS was (and somewhat remains) a community even among competition. I’m not basing what I’m saying solely on the example given.

He is saying that your perspective as a Linode employee might not represent how others saw Digital Ocean at the time. Which for me is glaringly obvious from your comments. EDIT: s/general public/others

I wasn’t talking about the general public. I was talking about the incumbents. I said competitors, not customers, and that wasn’t a corrected typo.

Edit: I responded to something that’s now been silently edited out and replaced with “others”.

Re: DigitalOcean S-1

#103

Post by hu3 »

edit: if you're going to downvote at least let me know why. I hold HN on high standards.

DO is a fantastic value proposition.

Reminds me when I was gathering cryptocurrency prices from exchanges and needed the lowest delay possible so an algorithm could protect me from pump-and-dumps.

In my testings, a $5/month machine from Digital Ocean was the fastest to fetch prices from Bittrex. I got prices within 0.2 milliseconds (yes, under 1 millisecond). It was unbeliavable.

The algo failed miserably ofc. Mostly because Exchanges price API tend to be unstable. Often giving stale or no data.

Re: DigitalOcean S-1

#104

Post by fourstar »

fastball wrote: post #88
yte14 wrote: post #75

Earlier quoted context omitted.

I remember Linode being hesitant to dip below $20 because the thinking was that it would diminish the quality of support. That thinking was reinforced when you started with $10 (if I recall, it’s been nearly a decade) and we started getting large numbers of refugees burned by experiences with your support organization. Neighboring comments tell me it’s still a problem. We consciously didn’t want to grow $5 fast becau…

You might be experiencing a form of survivorship bias / confirmation bias here. If you work at Linode, presumably people would come up to you asking about something they then couched to you as a Linode clone. That doesn't mean it's how people were talking about DO when not directly speaking with someone at Linode.

Lol. Typical HN midwit reply.

Edit: lol at the child poster to this who told me to “go back to my hole” before editing it with the HR-approved reply. Didn’t want to risk any precious karma eh?

And yes you’re right that this is “the wrong forum” — all the real hackers left HN years before you joined.

Re: DigitalOcean S-1

#105

Post by jtdev »

I was really considering moving from AWS to DO until I noticed this: https://www.digitalocean.com/company/contact/#abuse

So anyone who's offended by content you might host on DO can report your site and some identity politics obsessed bureauocrat decides if you're cancelled or not...? The public cloud has turned into an Orwellian nightmare.

Re: DigitalOcean S-1

#106

Post by sdflhasjd »

halfmatthalfcat wrote: post #10

I love DigitalOcean. The simplicity of their UI, friendly CLI tooling and (as a hosted k8s customer) the frequency of updates to their offerings. BUT: 1. Their web UI stability is terrible (constantly hangs and errors out) 2. Their hosted DB IOPS aren't competitive with other PaaS providers. There's also no way to scale DB size dynamically without upgrading to a new price tier which is overkill. 3. Their Kubernetes C…

I actually think their UI is too form over function. One particular annoyance I had recently was with the DNS zone editor.

It truncates both the record contents and the domain name, which means that if you've got a bunch of long domains with TXT records, telling them apart means copying the contents into a text editor to see the truncated text.

e.g

  somekey._dkim.subdomaina.domain.com     k=rsa; t=s; p=MIGfAAAA
  somekey._dkim.subdomainb.domain.com     k=rsa; t=s; p=MIGfBBBB
  somekey._dkim.subdomainc.domain.com     k=rsa; t=s; p=MIGfAAAA
getting truncated down to

  somekey._dkim.subdo...     k=rsa; t=s; p=MI...
  somekey._dkim.subdo...     k=rsa; t=s; p=MI...
  somekey._dkim.subdo...     k=rsa; t=s; p=MI...
Compared to AWS, which is visually unappealing, but I can actually see my DNS records....

Re: DigitalOcean S-1

#107

Post by bithavoc »

dstick wrote: post #97
jakelazaroff wrote: post #80

Earlier quoted context omitted.

Interesting — checked again and what I'm using is actually a snapshot. Not sure why that makes a difference, sorry for the confusion.

I guess that would be a slightly laborous work around? Install vanilla linux, configure as needed. Save snapshot. Treat it as a custom image :)

Yeah, Snapshots work quite well, you can even transfer them between accounts and copy them between regions in the same account, but it's a "transfer" meant to be used as a migration mechanism, not distribution.

Re: DigitalOcean S-1

#108

Post by jiofih »

fourstar wrote: post #104
fastball wrote: post #88

Earlier quoted context omitted.

You might be experiencing a form of survivorship bias / confirmation bias here. If you work at Linode, presumably people would come up to you asking about something they then couched to you as a Linode clone. That doesn't mean it's how people were talking about DO when not directly speaking with someone at Linode.

Lol. Typical HN midwit reply. Edit: lol at the child poster to this who told me to “go back to my hole” before editing it with the HR-approved reply. Didn’t want to risk any precious karma eh? And yes you’re right that this is “the wrong forum” — all the real hackers left HN years before you joined.

You seem to be in the wrong forum - personal attacks are not welcome here.

Re: DigitalOcean S-1

#109

Post by stephenSinniah »

From the risk factors summary:

Implications of Being an Emerging Growth Company

We are an “emerging growth company” as defined in the Jumpstart Our Business Startups Act of 2012, or the JOBS Act. We may take advantage of certain exemptions from various public company reporting requirements, including not being required to have our internal controls over financial reporting audited by our independent registered public accounting firm under Section 404 of the Sarbanes-Oxley Act of 2002, or the Sarbanes-Oxley Act, reduced disclosure obligations regarding executive compensation in our periodic reports and proxy statements and exemptions from the requirements of holding a non-binding advisory vote on executive compensation and any golden parachute payments. We may take advantage of these exemptions for up to five years or until we are no longer an emerging growth company, whichever is earlier. In addition, the JOBS Act provides that an “emerging growth company” can delay adopting new or revised accounting standards until those standards apply to private companies. We have elected to take advantage of certain of the reduced disclosure obligations in the registration statement of which this prospectus is a part and may elect to take advantage of other reduced reporting requirements in future filings. As a result, the information that we provide to our stockholders may be different than you might receive from other public reporting companies in which you hold equity interests.

Wow, I didn't know about this. Shouldn't financial reporting always be transparent?

Re: DigitalOcean S-1

#110

Post by derefr »

yte14 wrote: post #91
fastball wrote: post #88

Earlier quoted context omitted.

You might be experiencing a form of survivorship bias / confirmation bias here. If you work at Linode, presumably people would come up to you asking about something they then couched to you as a Linode clone. That doesn't mean it's how people were talking about DO when not directly speaking with someone at Linode.

I don’t understand how that impacts my point at all. If an opinion is only held in one context it’s not actually held? Is that what you’re saying? I’m sorry, I don’t follow. Before DO VPS was (and somewhat remains) a community even among competition. I’m not basing what I’m saying solely on the example given.

Perhaps it wasn’t their own mental model of the landscape at all, but just what they considered to be the most expedient way of getting the message across in terms customers would understand.

Hypothetical analogy: if I were describing my very-first-ever PaaS service, to competitors who’d only ever heard of IaaS services — and this wasn’t the point of the conversation (i.e. I wasn’t trying to sell them on the benefits of PaaS), but rather just a supporting statement to talking about how we do/don’t offer an IaaS feature, because we’re a PaaS — then I’d probably describe my PaaS by analogy to some popular IaaS that has a feature-set closest to a PaaS.

In my own mental model, I have a separate node for “PaaS”; but if I know that the people I’m communicating with don’t — and teaching them what a PaaS is would take time away from the real topic we’re trying to focus on — then I’m going to describe my PaaS provider as “basically like $foo IaaS provider” when talking about how it has the same feature X. To them.

Post reply on HN