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

281–290 of 442 posts

Re: DigitalOcean S-1

#281

Post by jjav »

jamroom wrote: post #141
stanmancan wrote: post #131

Earlier quoted context omitted.

I was a huge Linode fan for years. I used them exclusively. DO showed up and slowly but surely started being the better deal. Lower entry points, better specs, and then finally a more robust product line. I slowly found myself going to DO for new servers and eventually moved everything there for simplicities sake. Linode still has a special place in my heart, but they have some work to do if they want to remain compe…

Wow - really? I use both Linode and DO extensively and Linode is better on almost all fronts in my experience. Faster servers, better network, Linode's Object Storage is way better than DO's "spaces" and Linode's support is hands down the better of the two. If you're going to spend $5 on a server why would you go with DO unless you're already there?

Same here, I use both but prefer Linode in every aspect. Much better support and reliability in particular.

I moved a few very low-end hosts to DO when the $5 price point appeared but have never been overly impressed. Later Linode matched prices so no real reason to look into DO anymore.

But I do still use both. Partly to avoid migrating the DO hosts I have but more because I just like to keep aware of how both are evolving.

Re: DigitalOcean S-1

#282

Post by benatkin »

brightball wrote: post #270
yte14 wrote: post #54

Earlier quoted context omitted.

The thesis of DigitalOcean was literally “this very established market needs a venture capital growth play because we saw Slicehost exit to Rackspace”. In the beginning the entirety of DO’s offering, tech for tech, was almost a direct lift of Linode and, as they scaled, made all the same technical mistakes and learning experiences that Linode did. I guess you could call that a fantastic product idea. I’d call it appl…

As a happy Slicehost customer, I definitely saw Slicehost in every aspect of the DO approach.

Some are saying that about Linode and I just don't get it.

Loved Slicehost!!!

Re: DigitalOcean S-1

#283

Post by jjav »

maximus024 wrote: post #182
jamroom wrote: post #141

Earlier quoted context omitted.

Wow - really? I use both Linode and DO extensively and Linode is better on almost all fronts in my experience. Faster servers, better network, Linode's Object Storage is way better than DO's "spaces" and Linode's support is hands down the better of the two. If you're going to spend $5 on a server why would you go with DO unless you're already there?

> If you're going to spend $5 on a server why would you go with DO unless you're already there? I would go with anyone other than Linode, considering they left the control plane running a publicly accessible unpatched version of ColdFusion, which led to multiple instances of them losing control of customer's data. Anyone but Linode.

I mean that was terrible, but I know full well that every company ever will have dumb vulnerabilities occasionally, so by that metric I could never use anyone.

Re: DigitalOcean S-1

#284

Post by jjav »

grey-area wrote: post #113
yte14 wrote: post #54

Earlier quoted context omitted.

The thesis of DigitalOcean was literally “this very established market needs a venture capital growth play because we saw Slicehost exit to Rackspace”. In the beginning the entirety of DO’s offering, tech for tech, was almost a direct lift of Linode and, as they scaled, made all the same technical mistakes and learning experiences that Linode did. I guess you could call that a fantastic product idea. I’d call it appl…

As a user of both services for years, the only point on which they are similar was/is that they both offer shared cheap VMs (as do lots of other services). Presenting early DO as a ripoff of linode is frankly absurd, the UI, user experience, API, Load balancing, backups, and docs were all vastly superior to Linode, and it honestly felt like the copying was more the other way round as Linode tried to catch up with the…

I'm puzzled by the praises on DO UI, since in the early days in particular I always found it intolerably terrible. Far less useful than Linode UI. Nowadays it's ok, but Linode is still has better UI.

Re: DigitalOcean S-1

#285

Post by kchr »

1shooner wrote: post #248
shiftpgdn wrote: post #215

Earlier quoted context omitted.

Lol, what? DO was basically a page for page copy of linode's site and product offering in 2011-2013.

I remember at that time feeling almost bad for Linode because they had built up so much valuable educational content about what you could run on their services, and I was using it step-by-step on DO. The only differentiator was the price. Of course DO quickly replicated and excelled in providing that tutorial value as well.

But were they really doing anything other than copy/pasting HOWTOs by Falko Timme?

Re: DigitalOcean S-1

#286

Post by jtdev »

1f60c wrote: post #256
jtdev wrote: post #105

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.

From your link: > Report abuse: > > - DMCA Takedown > - Trademark Infringement > - Spam > - Phishing > - Malware > - Botnet > - Intrusion/exploit attempts (Bruteforce, Scans etc) > - Child Abuse > - Violent Threats and Harassment > - Other That seems like a reasonable list of stuff I wouldn't want to have my platform be used for, either. Though, one might reasonably take issue with that "Other" category, but note tha…

I think you’re downplaying the “Other” category, which literally gives DO carte blanche in cancelling those they don’t approve of, or worse who the mob pressures DO to cancel.

Do you not see how problematic this is? I agree with all of the other categories wholeheartedly, but even then, application of the policies of these organizations should be uniform, i.e., if both right wing and left wing websites publishes “Violent Threats and Harrassment”, both should be taken down. That’s not what we’re seeing in practice from the major cloud providers.

Re: DigitalOcean S-1

#287

Post by sitkack »

staticautomatic wrote: post #33
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…

They also have some of the best technical documentation on the web.

I hold up this part of DO as one of the single best uses of the amazing tech writers our industry has, under appreciated and under paid, to punch way above their weight in a crowded market.

Really really well done DO!

Re: DigitalOcean S-1

#288

Post by 1f60c »

jtdev wrote: post #286
1f60c wrote: post #256

Earlier quoted context omitted.

From your link: > Report abuse: > > - DMCA Takedown > - Trademark Infringement > - Spam > - Phishing > - Malware > - Botnet > - Intrusion/exploit attempts (Bruteforce, Scans etc) > - Child Abuse > - Violent Threats and Harassment > - Other That seems like a reasonable list of stuff I wouldn't want to have my platform be used for, either. Though, one might reasonably take issue with that "Other" category, but note tha…

I think you’re downplaying the “Other” category, which literally gives DO carte blanche in cancelling those they don’t approve of, or worse who the mob pressures DO to cancel. Do you not see how problematic this is? I agree with all of the other categories wholeheartedly, but even then, application of the policies of these organizations should be uniform, i.e., if both right wing and left wing websites publishes “Vio…

> Do you not see how problematic this is?

Their platform, their rules.

Re: DigitalOcean S-1

#289

Post by dbyrd »

I used to work at DigitalOcean. Can confirm we didn't think a lot about Linode. We saw AWS as the real competitor. If there was someone in the VPS market we respected and tried to emulate it would have been OVH, not Linode.

Re: DigitalOcean S-1

#290

Post by hisyn »

jandrese wrote: post #198
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…

5. Their IPv6 support is pants on head. https://www.digitalocean.com/docs/networking/ipv6/ Yes, you read that right, they assign a /124 if you enable IPv6. There is no provision for getting anything larger. All configuration is totally static as well. It's really incredible how botched the setup is, and it has been like this for years . If you're wondering if you're sharing the same /64 with an entire datacenter wort…

This -- this has me a bit frustrated and I'll eventually email them about it.

I haven't contacted them about it but that makes sense sadly. So they're getting a /64 from their upstream and just sharing that out to everyone. This isn't IPv4, they need to make this right.

Vultr, OTOH, gives each HOST a /64. I've been doing most of my work on Vultr right now so I can use more than 16 IPs on a single host. I was/am hoping that providers would standardize somewhere in the middle: Every customer account in each datacenter gets a /64. I wouldn't mind all of my hosts having their own /64 to subdivide.

Post reply on HN