Re:A serverless email server on AWS using S3 and SES
by chrischattin on Saturday January 04, 2020 @09:19AM
(#21954995)
Not at all. It's in this case, using the term serverless is akin to calling cloud based software (Google Docs, TurboTax, etc) softwareless. It's closer to calling a stop sign a "go sign" than descriptors from your example. Calling managed servers "serverless" is distinctively misleading.
[ Parent
| on HN ]
Re:A serverless email server on AWS using S3 and SES
by scarface74 on Saturday January 04, 2020 @09:29AM
(#21955036)
How is it any more misleading than “bugs”, “containers”, “the cloud”,”server farms”, etc.
Wouldn’t you be the first to criticize someone who didn’t take the time to understand other computer concepts that had been around for years and then attempted to speak intelligently about them?
Re:A serverless email server on AWS using S3 and SES
by c-cube on Saturday January 04, 2020 @12:21PM
(#21956055)
It's misleading because "serverless" intuitively means peer to peer, where everything runs on clients and there are truly no servers. So unlike "bug" it has an intuitive meaning that is the opposite of what the buzzword now means.
Re:A serverless email server on AWS using S3 and SES
by scarface74 on Saturday January 04, 2020 @12:28PM
(#21956101)
Serverless has never been used in the context of peer to peer. And “bug” isn’t anymore “intuitive” to the uninitiated.
Re:A serverless email server on AWS using S3 and SES
by chrischattin on Saturday January 04, 2020 @09:42AM
(#21955099)
The term serverless is not a metaphor like your examples, it's a contradiction. Big difference. I feel like understanding the "computer concepts" makes the term seem even more absurd.
Re:A serverless email server on AWS using S3 and SES
by scarface74 on Saturday January 04, 2020 @09:50AM
(#21955133)
It’s an abstraction - just like every other computer concept.
Re:A serverless email server on AWS using S3 and SES
by wodny on Saturday January 04, 2020 @10:13AM
(#21955269)
An abstraction where "positive" and "negative" mean the same just for safety so they can't be confused with each other.
Re:A serverless email server on AWS using S3 and SES
by scarface74 on Saturday January 04, 2020 @10:24AM
(#21955325)
You’ve never worked with C code that had to run on both big endian and little endian systems that had to share a common byte protocol. Where two bytes in the same order can mean something completely different.
There are a lot of things “confusing” about computer science when you don’t take the time to learn it.
Re:A serverless email server on AWS using S3 and SES
by wodny on Saturday January 04, 2020 @10:36AM
(#21955397)
On the contrary, I've worked with 8 and {32,64}bit x {LE,BE} chips many times and wrote quite a lot of network code in C. But you're mixing syntax with semantics.
Re:A serverless email server on AWS using S3 and SES
by scarface74 on Saturday January 04, 2020 @12:43PM
(#21956196)
Which byte is the high order byte is just as much semantics defined by the chip vendor that would be confusing to the uninitiated as “Serverless” would be to an old school net ops person who doesn’t know anything about cloud computing.