4 ms·

Ugh, while I appreciate the work that goes into these tools and see the value, I hate the needlessly critical language about “irrelevant” details and “bloated”

Ugh, while I appreciate the work that goes into these tools and see the value, I hate the needlessly critical language about “irrelevant” details and “bloated” cloud infrastructure. These components are lightweight and simple and trivially easy to use because they are lightweight and simple and cover trivial use cases. But if you build anything beyond the trivial you will eventually have to get into the weeds, and the details are no longer irrelevant, and the “bloat” will happen to your beautiful lightweight and simple Serverless configuration. There’s no need to ridicule the inevitable complexity of complexity to sell this stuff. It’s just pointless negativity.

ac360 7y ago
"Complexity is inevitable" is a self-fulfilling prophecy.
- skywhopper 7y ago
  I think you misread what I wrote.
  - ac360 7y ago
    Not all infrastructure configuration options are relevant to every use-case. By focusing on specific use-cases, you can hide "irrelevant" config options. This is a fact. The full statement from the source material says bloated cloud infrastructure "configurations", referring to verbose configuration files. Needlessly critical? It depends on your experience with these. These, serverless, cloud, and more are abstractions. Fortunately, if the abstraction doesn't fit your needs, you aren't forced to use them.
jedberg 7y ago
I think the implied missing phrase is "for a simple deployment". How the web server works and and how the certificate is issued are irrelevant to launch a personal blog, but before this, if you wanted to do that on Serverless, you had to worry about that stuff. Their point is that you don't have to worry about any of this stuff to get simple tasks done, which you used to have to worry about.
ehnto 7y ago
In time we will have an article about serverless components being bloated, and how what we really need is componentless components. Why bother with all the configuration and deployment? Just write it as procedural javascript and serve it from your laptop!

ac360 7y ago

"Complexity is inevitable" is a self-fulfilling prophecy.

skywhopper 7y ago
I think you misread what I wrote.
- ac360 7y ago
  Not all infrastructure configuration options are relevant to every use-case. By focusing on specific use-cases, you can hide "irrelevant" config options. This is a fact. The full statement from the source material says bloated cloud infrastructure "configurations", referring to verbose configuration files. Needlessly critical? It depends on your experience with these. These, serverless, cloud, and more are abstractions. Fortunately, if the abstraction doesn't fit your needs, you aren't forced to use them.

jedberg 7y ago

I think the implied missing phrase is "for a simple deployment". How the web server works and and how the certificate is issued are irrelevant to launch a personal blog, but before this, if you wanted to do that on Serverless, you had to worry about that stuff. Their point is that you don't have to worry about any of this stuff to get simple tasks done, which you used to have to worry about.

ehnto 7y ago

In time we will have an article about serverless components being bloated, and how what we really need is componentless components. Why bother with all the configuration and deployment? Just write it as procedural javascript and serve it from your laptop!