4 ms·
The media's job is not to inform you at this point. Their job is to get eyes on their product. That's no secret. However, the logic behind your approach is flaw
by NotZachari 7y ago
The media's job is not to inform you at this point. Their job is to get eyes on their product. That's no secret. However, the logic behind your approach is flawed.
Why? Money is king in every industry. Sure, hype exists. I had one instance where I felt exactly like you, and guess what hot new flavor of the month that was? React. It didn't take long to realize who the idiot was in that situation (me). It was hot because it was the next logical step, and no amount of being frustrated because I had just gotten comfortable with Angular could change that.
Containers aren't some snake oil racket. It's pretty easy to see why if you take off the tinfoil. They are cost and resource efficient, and they provide a large cushion for less than optimal situations. Containers are smaller than VMs and less resource intensive so they allow you to do more with less hardware. Sudden rush of people because Reddit or HN fell in love with you? Provision a few more with almost zero effort knowing exactly what you'll be getting. Working on bug fixes or improving shit? Cool. There's no difference between the local instances and what hits production.
I mean, it's kind of like the folks who get real passionate about only using basic code editors because all the extra tools are "cheating". Time is money, and it's the only thing we can't get back. If containers significantly reduce cost in terms of resources, man hours, or money for you or the company you work for, it doesn't take a rocket scientist to understand why it'd be pushed so hard.
I understand being cynical in this industry, but let's be realistic. Companies are only pushing what they believe will be good for their bottom line. No one's pushing containers because of some shitty agenda, just as they weren't when Node.js was blowing up to the same screams of "this is all manufactured hype".
There are definitely cons to using containers. You're pushing a bunch of shit with root access all sharing the kernel out there, and if a single one is compromised, they're all compromised by definition. That's a legitimate concern, but if I'm being honest, this sounds more like you haven't been in a situation where containers were the proper solution more than a tech industry scam to push an agenda.