Live data from Hacker News

DigitalOcean’s quarterly report on developer trends in the cloud

digitalocean.com

71–80 of 94 posts

Re: DigitalOcean’s quarterly report on developer trends in the cloud

#71
post #20

Earlier quoted context omitted.

Do you think a lot of people are running JS in a container for frontend? I wouldn't consider a webserver container a "JS container", even it were mostly serving a React/Vue/Angular app. By the way it's worded, it sounds like the question is specifically talking about NodeJS.

> Do you think a lot of people are running JS in a container for frontend? Hold my beer. --Frontend developers

If the rest of a web app is running on containers, what's the downside to having the test/build process for the frontend in a container as well?

Re: DigitalOcean’s quarterly report on developer trends in the cloud

#72
post #25
post #9

Has anyone chosen digital ocean over aws/gcp/aZure when building a scalable setup (for pricing reasons). Eg setting up your own load balancers/ private master slave dB machines / bunch of ansible to organize it all.

Yes. We are using DO over AWS. Our bill is $120/month. We serve 21m web requests per month for that amount.

possible to share analysis of what the equivalent would've cost in infrastructure on AWS/GCP/Azure?

Re: DigitalOcean’s quarterly report on developer trends in the cloud

#73
post #9

Has anyone chosen digital ocean over aws/gcp/aZure when building a scalable setup (for pricing reasons). Eg setting up your own load balancers/ private master slave dB machines / bunch of ansible to organize it all.

Fwiw, Digital Ocean keeps adding more and more options on the service front. Several storage options, load balancers w/ Let's Encrypt built in, etc. Keeps growing. IMO the biggest gap for them is lack of a database service like RDS. There are providers of that service that can be deployed to DO...but the cost of those providers is high enough to disincentivize the price appeal of DO in the first place. It would be re…

FWIW, I have found one of the best parts of using Digital Ocean is their fantastic documentation and tutorials. As a relative newbie, I was encouraged to deploy to a PaaS such as Heroku but grew frustrated at the black box aspect of what was going on underneath the hood. The tutorials on DO allowed me to learn and gain an understanding of how servers really work.

On your point about database services, I was able to set up Postgres on my droplet with relative ease and it has been serving me well ever since, again all thanks to clear and well made tutorials. I think if I could do it without any prior experience, most other people can too. So IMO, these providers aren't necessary at all.

Re: DigitalOcean’s quarterly report on developer trends in the cloud

#74

Earlier quoted context omitted.

> 15 years ago my computer had 128MB RAM and I was browsing the web at approximately the same rate. You probably weren't; perceptions of speed are often based on expectations set by experience, and your expectations were probably a lot lower then. If you actually could go back and browse the web of 15 years ago and the sites you could then, you would be disappointed, but the speed then was similar scaled to the expec…

I know I could have four browser windows open with 20 tabs each, to a random selection of web pages. If I try to do that today on a laptop with 2GB RAM on a moden browser, it dies from running out of memory. I tried using an older browser, but it won't render modern pages and uses legacy crypto. So I know for a fact that modern browsers simply can't work on older hardware, whereas the older browsers used to work, but…

Firefox didn't even have tabbed browsing in 2003 and everyone else was in the IE6 winter. FF was only 1 year old at this point. Were you using another browser?

Re: DigitalOcean’s quarterly report on developer trends in the cloud

#75

Earlier quoted context omitted.

I know I could have four browser windows open with 20 tabs each, to a random selection of web pages. If I try to do that today on a laptop with 2GB RAM on a moden browser, it dies from running out of memory. I tried using an older browser, but it won't render modern pages and uses legacy crypto. So I know for a fact that modern browsers simply can't work on older hardware, whereas the older browsers used to work, but…

Firefox didn't even have tabbed browsing in 2003 and everyone else was in the IE6 winter. FF was only 1 year old at this point. Were you using another browser?

Firefox didn't exist in 2003, it was released in November 2004. Before then, the name of the browser was Phoenix. It had tabs since version 0.1, released in September 2002. Later it was renamed Firebird and then Firefox.

Pre-tabs I probably had only 40 windows open at a time.

Re: DigitalOcean’s quarterly report on developer trends in the cloud

#76

Earlier quoted context omitted.

Firefox didn't even have tabbed browsing in 2003 and everyone else was in the IE6 winter. FF was only 1 year old at this point. Were you using another browser?

Firefox didn't exist in 2003, it was released in November 2004. Before then, the name of the browser was Phoenix. It had tabs since version 0.1, released in September 2002. Later it was renamed Firebird and then Firefox. Pre-tabs I probably had only 40 windows open at a time.

It existed but was still under development and not enabled by default. E.g. there was no graceful handling of tab overflows https://wiki.mozilla.org/Tabbed_Browsing/User_Interface_Desi...

Re: DigitalOcean’s quarterly report on developer trends in the cloud

#77

Earlier quoted context omitted.

Firefox didn't exist in 2003, it was released in November 2004. Before then, the name of the browser was Phoenix. It had tabs since version 0.1, released in September 2002. Later it was renamed Firebird and then Firefox. Pre-tabs I probably had only 40 windows open at a time.

It existed but was still under development and not enabled by default. E.g. there was no graceful handling of tab overflows https://wiki.mozilla.org/Tabbed_Browsing/User_Interface_Desi...

Yes, I definitely enabled all the beta/testing features. Tabs may have been limited "depending on screen resolution", but as a gamer I had probably one of the biggest screen resolutions you could run, with a CRT to match. I'm pretty sure I was using an AMD K6-2 500Mhz with between 128 and 256MB RAM. Sometime after 2002 I built an Athlon-based system with a gig of RAM, so I could be mis-remembering my computing platform when "peak browsing performance" happened, but I know that no browser has ever been as fast as Phoenix was.

Re: DigitalOcean’s quarterly report on developer trends in the cloud

#78
post #64
post #20

Earlier quoted context omitted.

Do you think a lot of people are running JS in a container for frontend? I wouldn't consider a webserver container a "JS container", even it were mostly serving a React/Vue/Angular app. By the way it's worded, it sounds like the question is specifically talking about NodeJS.

actually! at my old job there was a project where the frontend webpack build was running in a docker container..

Yeah, I guess when you think about it that way it makes sense. I think I might have assumed this was for production and not build environments.

Re: DigitalOcean’s quarterly report on developer trends in the cloud

#80
post #73

Earlier quoted context omitted.

Fwiw, Digital Ocean keeps adding more and more options on the service front. Several storage options, load balancers w/ Let's Encrypt built in, etc. Keeps growing. IMO the biggest gap for them is lack of a database service like RDS. There are providers of that service that can be deployed to DO...but the cost of those providers is high enough to disincentivize the price appeal of DO in the first place. It would be re…

FWIW, I have found one of the best parts of using Digital Ocean is their fantastic documentation and tutorials. As a relative newbie, I was encouraged to deploy to a PaaS such as Heroku but grew frustrated at the black box aspect of what was going on underneath the hood. The tutorials on DO allowed me to learn and gain an understanding of how servers really work. On your point about database services, I was able to s…

Oh, I totally agree. That's actually how I learned this stuff. Years ago there was a company called Slicehost that was very similar to what Digital Ocean is now. It had a treasure trove of great documentation and articles.

Eventually they were acquired by Rackspace and folded into the Cloud Servers line.

Great company though.

Post reply on HN