Live data from Hacker News

DigitalOcean’s quarterly report on developer trends in the cloud

digitalocean.com

61–70 of 94 posts

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

#61

> Serverless computing is in a much earlier stage of adoption, with nearly half of developers failing to clearly understand what it is. I've seen this called Function as a Service and honestly I think using that term instead of Serverless would go a long way to fixing this issue because 1) it clearly communicates what it is 2) there's not actually such thing as serverless since the functions are still running on serv…

> The first time I heard "serverless" I assumed it was a totally in-browser application.

So the term "serverless" made you think there was no server involved? What could have possibly made you think that?

"Serverless" is up there with "cloud" for the dumbest most overused words in technology right now.

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

#62
post #61

> Serverless computing is in a much earlier stage of adoption, with nearly half of developers failing to clearly understand what it is. I've seen this called Function as a Service and honestly I think using that term instead of Serverless would go a long way to fixing this issue because 1) it clearly communicates what it is 2) there's not actually such thing as serverless since the functions are still running on serv…

> The first time I heard "serverless" I assumed it was a totally in-browser application. So the term "serverless" made you think there was no server involved? What could have possibly made you think that? "Serverless" is up there with "cloud" for the dumbest most overused words in technology right now.

BitTorrent and Napster is what made me think that

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

#63
post #28

Earlier quoted context omitted.

In my experience, those VMs were used briefly then left to rot. Consuming a large reserve of resources while doing nothing. Serverless should at least reduce the overhead of orphaned projects out there.

There's a secondary problem: when there are more resources, application development becomes less efficient over time. Even though there will be less infrequently used resources, the applications will use up resources more frequently in an inefficient way. Example: I now need a minimum of 4GB RAM to browse the web, which is insane. 15 years ago my computer had 128MB RAM and I was browsing the web at approximately the…

Today it's possible to buy a laser-guided sleep-o-matic superbed that walks your dog and cures your back pain.

You can also buy a basic bed that's pretty nice and reasonably cheap.

15 years ago, you might have had a high-tech bed that didn't leave you sore in the morning.

1,500 years ago you had a bed of straw with fleas and bedbugs, but at least you had a place to sleep.

150,000 years you slept in furs on dirt by the fire, breathing smoke and aggravating your sciatica. Your bed was basically free, but since your livelihood depended on your full mobility, sleeping there was slowly killing you.

All these beds provided the feature of "sleep." So why would anybody need a sleep-o-matic, a bed worth more in 150,000 BC dollars than the yearly economic output of your continent? Why should we accept the massive waste of resources it represents?

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

#64
post #20
post #12

Like the Stack Overflow survey, this one does not distinguish server-side/client-side JavaScript, making it look far more popular than it actually is when considering the data in context of server-side technologies. If 100% of the servers were running PHP, the results would likely be 50% PHP, 50% JavaScript. These survey writers need to modify their question, or add another one specifically requesting server-side tec…

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..

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

#65
post #44

Earlier quoted context omitted.

There's a secondary problem: when there are more resources, application development becomes less efficient over time. Even though there will be less infrequently used resources, the applications will use up resources more frequently in an inefficient way. Example: I now need a minimum of 4GB RAM to browse the web, which is insane. 15 years ago my computer had 128MB RAM and I was browsing the web at approximately the…

if you have the resources use them? 15 years ago your browser had a small fraction of the features a modern browser provides. this argument is tiring.

Which is the problem. Everyone knows that I have resources, so everyone wants to use them by packing in every feature without any consideration for how much memory it uses. It's fine if I only wanted to run a browser or only wanted to run an IDE.

It's not that everyone should always strive to have the minimum footprint possible. It's that no one cares how big the maximum footprint can be.

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

#66
post #28

Earlier quoted context omitted.

In my experience, those VMs were used briefly then left to rot. Consuming a large reserve of resources while doing nothing. Serverless should at least reduce the overhead of orphaned projects out there.

There's a secondary problem: when there are more resources, application development becomes less efficient over time. Even though there will be less infrequently used resources, the applications will use up resources more frequently in an inefficient way. Example: I now need a minimum of 4GB RAM to browse the web, which is insane. 15 years ago my computer had 128MB RAM and I was browsing the web at approximately the…

Fifteen years ago, AJAX did not exist. Fifteen years before that our computers had VGA screens and megabytes of RAM. Yours is an oft-heard complaint in many quarters, but with respect, I have trouble taking it as indicative of anything other than the bitterness of age. Yes, the new technology is bloated and wasteful. As far as I am aware, this has been a fact of new technology for some time. Efficiency is one of the least important factors in software development.

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

#67
post #61

Earlier quoted context omitted.

> The first time I heard "serverless" I assumed it was a totally in-browser application. So the term "serverless" made you think there was no server involved? What could have possibly made you think that? "Serverless" is up there with "cloud" for the dumbest most overused words in technology right now.

BitTorrent and Napster is what made me think that

I think he was being sarcastic...

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

#68
post #28

Earlier quoted context omitted.

In my experience, those VMs were used briefly then left to rot. Consuming a large reserve of resources while doing nothing. Serverless should at least reduce the overhead of orphaned projects out there.

There's a secondary problem: when there are more resources, application development becomes less efficient over time. Even though there will be less infrequently used resources, the applications will use up resources more frequently in an inefficient way. Example: I now need a minimum of 4GB RAM to browse the web, which is insane. 15 years ago my computer had 128MB RAM and I was browsing the web at approximately the…

> 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 expectations you had then as the speed now is scaled to your current t expectations. So your perception of the speed is similar.

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

#69

Interesting to see the disconnect between hiring managers and what people say they care about most when considering a job offer (salary). Hiring managers claim there is a shortage of talent and that they do not care about offering a higher salary. Perhaps that talent shortage would mysteriously disappear if they increased their salary offers.

Computers are a tool of Automation. A seasoned engineer can build amazing things that does the work of many humans. Not only that 10X developers don’t work 10X hard, they are able to solve 10x problems with 1X effort because of their domain experience and approach to problem solving.

This kinds of people are hard to find. It’s a terrible business decision not to pay them well because their ROI is multiple times their salaries.

They are also very rarely on the market sending out resumes. Mostly because they get jobs mostly via friends of friends and referrals.

But I do agree a 100%, we should be getting paid more. If you’re not getting paid enough, look for other opportunities. There are plenty.

The tech industry has never been as profitable as it is now. We are in a huge tech boom right now. AppAmaGoogMsft are all poised to be the first trillion dollar corporations.

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

#70

Earlier quoted context omitted.

There's a secondary problem: when there are more resources, application development becomes less efficient over time. Even though there will be less infrequently used resources, the applications will use up resources more frequently in an inefficient way. Example: I now need a minimum of 4GB RAM to browse the web, which is insane. 15 years ago my computer had 128MB RAM and I was browsing the web at approximately the…

> 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 are no longer compatible with modern websites.
Post reply on HN