AWS services explained in one line each

Re:AWS services explained in one line each by scarface74 on Tuesday May 26, 2020 @11:59PM (#23319263)

Since some subset of people will invest time in learning technology even if it's complicated, therefore it doesn't matter if it's too complicated? If so, you'd have to show that the number of people using it wouldn't increase were it simpler, with clearer names, etc.

Well, two points.

1. From a completely selfish standpoint, if people aren’t willing to learn about AWS, it helps me out a lot. I’m able to make more money by taking the time to learn it.

2. There are three credible cloud providers -AWS, Azure, and GCP - and Oracle. Amazon is twice as large as Azure and 5 times larger than GCP. It doesn’t seem to be hurting them.

Just like the obtuse clusterf%%% that is modern front end development doesn’t seem to be hurting the adoption by the $cool_kids.

[ Parent | on HN ]

Re:AWS services explained in one line each by jonahx on Wednesday May 27, 2020 @12:59PM (#23326239)

> Just like the obtuse clusterf%%% that is modern front end development doesn’t seem to be hurting the adoption by the $cool_kids.

This is true, and it may even help with adoption among "cool kids." But the adoption could be much, much higher if it weren't such a clusterf%%%. There is an almost infinite amount of marketshare from a wide spectrum of technologies ranging from Wordpress down to "vanilla jquery" that could be eaten into.

Again, you can't look at some successful thing S lacking quality X and conclude "quality X doesn't matter." You have to compare "S with X" to "S without X". Sometimes a direct experiment is possible, sometimes not.

[ Parent | on HN ]