Maybe dumb more general question, but when is it then available on the stock market?
DigitalOcean S-1
341–350 of 442 posts
Re: DigitalOcean S-1
#342I just cannot fathom why people would use a tier 2 cloud provider over AWS or GCP. It can't possibly be significantly cheaper. The tooling is non-existent. There is little third party tutorials/documentation compared to tier 1. Why would anyone buy this?
Because (comparing DO to AWS) it is much cheaper for many use cases, there is good tooling and documentation, and the user experience is dramatically better. I'm curious - on what did you base your assumptions?
Years of tier 1 experience and trying to replicate those workloads on DO to see what the fuss is about. They are not remotely the same. How is the user experience better? Third party support like Terraform is objectively worse for DO
Re: DigitalOcean S-1
#343Earlier quoted context omitted.
We give new hires a homework project that is directly work related. We don't consider it unethical. It's really a fantastic way to sort out who can deliver. We used to have it be part of the onsite interview - they could sit for a few hours and do it. I like these because they are not games. If you want something done, you'd ask an employee to do it. So just ask someone to do something you need done. In our case at l…
You are misunderstanding. They are saying it is unethical to ask an interviewee to code for free and use that in production. In your case you are not doing that, although if I interviewed with you and saw the same feature added after I submitted the code I would definitely assume you did something unethical.
But is that what is happening? They said it was a work related project. That's exactly what we do.
Why would a place like google even use an interviewees code without careful copyright assignment and work for hire protections (ie, you need to pay someone in USA generally to own their code).
I've found some potential hires are randomly paranoid - and if they start giving you lots of hypothetical disaster / ripoff scenarios early, not worth the hire?
Re: DigitalOcean S-1
#344Earlier quoted context omitted.
Out of curiosity where did you move to?
I moved to BuyVM, https://buyvm.net/ . I had already been using their services for a few years, I just expanded on what I already had. They are not as large an enterprise as DigitalOcean, by a long shot, but the upside of that is you can speak with the owner and his small staff personally and get personal service. They made me a very good deal. I also know from their Discord that they have some conservative political…
BuyVM's wiki has things in it like https://wiki.buyvm.net/doku.php/kvm#pagefileswap_disclaimer, which, without any numbers behind it would make me extremely uneasy to use the service. Other cheap hosts just put hard IO limits at the VM host level.
Re: DigitalOcean S-1
#345Congrats to DO. Really like the direction DO is going. Which is something in between millions of small VPS firm and giant like AWS. It also forced Linode to React. And proved the space in Cloud Hosting exist, which company like Vultr and UpCloud are now joining. And I think their features are finally close to hitting the perfect spot. With all the essential like DBaS, Object Storage and K8s. They have also ( finally…
I'm a fan of DO too. In terms of "what's missing?", how about the equivalent of AWS Lambda@Edge or Cloudfront EdgeWorkers? ie, a NodeJS runtime as close to the end user as the nearest CDN edge.
The problem with Runtime at Edge is that they are extremely engineering intensive, given it isn't just hosting but the whole software stack involved. ( See CloudFlare Workers for Example ) Which is sort of outside the sweet spot that DO is currently enjoying or operating in. I am not sure if it is a sound strategic decision to persuade. Although I would certainly love to see competition in that area.
Re: DigitalOcean S-1
#346I 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…
I don't know if I'm doing something wrong but am I right that a droplet firewall doesn't have any ability to create source exceptions to lock an open port down to a singular IP. Seems like a basic enough feature but I can't seem to find it.
Re: DigitalOcean S-1
#347Excellent growth, fair margins. Probably worth about $3bn. If it IPOs at less than $5bn it's probably worth picking up. Long term digitalocean will struggle to maintain its margins when competing with Azure and AWS on one side, and Cloudflare edge computing on the other side, so I don't think it can command the same kind of premium we've seen from other tech IPOs. A big red flag is that 570,000 customers bring in onl…
They raised money over the past several years at over $10bln valuation, there's no way they're going to debut at $3bln.
Re: DigitalOcean S-1
#348Earlier quoted context omitted.
> Do you not see how problematic this is? Their platform, their rules.
“Their platform” has become the public square. If you think allowing unfettered control of such a utility by a small number of mega corporations - with political biases that change to suit their bottom line - is a good thing then I’m not sure we’re on the same page, in the same book, on the same planet.
These companies, and the systems and platforms they own, have not become "the public square" any more than a widely read newspaper, or the only Kinkos in town have. Nor are they utilities.
You're using words and phrases with significant legal implications to characterize things that don't meet the well-understood legal definitions.
I don't think you're being dishonest, but I fear you've been bamboozled by the dishonest arguments of others, and are now parroting them.
I may not like the decisions made by private companies, but private companies doing things I don't like w/r/t hosting speech is preferable to getting state power involved.
I don't like Nazi's marching in Skokie. And I don't like what the right insists of calling "cancel culture". But both of those things are constitutionally protected for good reason, and those rights are worth defending.
Re: DigitalOcean S-1
#349I 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…
Not being on the same level of feature parity with AWS/GCP can be considered a feature. Not everyone wants to drown in service orchestration and configs
100% - it's clear how everything works because they've pared down to the essentials. For their target market of small dev teams who just need to ship code, it's a godsend.
Re: DigitalOcean S-1
#350Earlier quoted context omitted.
I remember interviewing with DO back in late 2014 and it was nuts! The entire interview process took ~3 months and it was clear that they were defining the process as they went. The entire process was basically: 1. initial call with recruiter 2. homework project 3. call with engineer to discuss said homework project 4. two phone screens with engineers 5. onsite interview with 6 engineers Finally I had was at the fina…
Not to hijack this sub-thread, but just a general question: how does one deal with unethical 'homework projects'? I've had a case during an application where I was given a 'homework project' that seemed to me very much not like a theoretical scenario, but more like the company wanting me to do free work for an actual real-world issue they had. Have people had situations where you suspected the same? How do you deal w…
Simple - you give candidates assignments you've designed solely for interviewing. Ones that you clearly state up front are not real, not based around current project deliverables and commit that the code will ever be used in production.
Then it's no different to the rest of the candidate's time spent interviewing - it's cost of doing business that no one expects to be remunerated for.
The other benefit is that you then keep a benchmark of deliverables by having each candidate complete the same task (you have to change tasks over time as the details of the project get leaked/discussed).