You seem to think the entire world is connected by fiber now. Not the case. 98% of long distance cable runs across the world are still air run copper. That won’t immediately impact high dollar facilities like datacenters or undersea cables that are interconnected, but everything else it will take a hit.
Just convenience. That’s what packages provide. There’s no special magic under the hood in most cases as a downside to packages, and in most cases for specific projects, this is why stacks have containers, because you set the build steps to include the things you need in a pragmatic way, but now have to mess with static files on a filesystem.
The only thing that could take the entirety of the Internet for a bit of time is a massive EMF event that damages enough infrastructure to disable point-to-point communication between nodes. This means something like a Coronal Mass Ejection so large it cooks all satellites on its way in (on one side of orbit at least), then toasts a lot of other protected hardware on the ground.
The P2P nature of the internet would be hard to kill in totality with one event in any sense of the word. At the the very least, it would quick to get local infrastructure up within hours, assuming the entire DNS system isn’t destroyed.
I think you were told MANY times in the last thread…that’s not all Clevis is used for. You misunderstood the tool.
That’s not a NAS, that’s a full-on PC.
What you want for a NAS is a low power CPU, minimal memory, and hot swap capability.
If you’re looking more an application server, then that’s a different story. In either case, you probably want the lowest end non-APU chip.
You are not reading or understanding comments, child. That’s not what I said whatsoever.
You’re of the opinion that DevOps engineers can be automated away. I proved you wrong. Now you’re talking about the tooling, which is in my first comment to you. Automated tooling is NOT all DevOps is, and the fact you think shows me you’re unseasoned in whatever it is you do, have no concept of the role.
It would be people like you who would not pass the first round of interviews from answering a question about this topic exactly as you’ve stated, because you don’t understand the core function of the team, and you’re role in it.
You make some code, and obviously have no idea how to run it, let alone at scale. All the working pieces of a platform at large need to be understood and vetted by a DevOps team in order to make it run, and run well. That’s understanding everything from start to finish, in ways you wouldn’t be able to comprehend being one part of team that is building one part of a platform. You can’t make an agent that understands all the underpinnings of all the services or metrics, and why they fail, that then takes action on them, because it’s not something AI does. Case in point, the AWS outage and others I mentioned.
Now, you could make MANY agents that take actions on many things, but that doesn’t give situational awareness or comprehension to any singular agent, something AI also doesn’t do. That’s what DevOps teams do.
I don’t even need to keep arguing with you about this, because the down votes on your comments speak for themselves. I’m just trying to educate on your false understanding about how it all works so you don’t stumble through your career making the same comments and mistakes.
Smart. Kids are really hyping physical media again, akin to when 80’s kids brought vinyl back in the 2000’s.
Been running Ops teams for decades, kid. Look at alllll the people agreeing with me, and disagreeing with you. You have the unearned wisdom of a struggling Junior Dev. If you had any experience, you’d know how embarrassing it would be to attempt to brag about working for “multi-billion dollar companies” 🤣🤣🤣🤣
Yes, those big, big companies are where ALL the good engineering jobs are at. Where all the interesting work is being done 🤣🤣🤣🤣
My GAWD, child. W O W 🤦
Again, refer to my first comment because you’re out of your league here 🤣🤦
🤣
Okay bud, go and tell AWS, Google, Salesforce, and any other of these companies who think “AI” is an answer to everything, because they’ve all had very public outages due to this exact same thing in the past few months.
You have no idea what DevOps is or how it works if you think any of this is easily done or solved with these junk tools.
Try disabling hardware acceleration on whatever browser she’s using, or switch to using a different YT frontend: https://github.com/mendel5/alternative-front-ends?tab=readme-ov-file#youtube
No, it actually hasn’t. It’s also not any better than any other battery tech out there right now. Longer term but less volume storage is a trade off.
What happened to these Graphene batteries and capacitors we were supposed to have by now?
If you’re this familiar with all the moving bits of this, why are you asking?
I’m only saying this because this is obviously someone who read a bunch of stuff about various things that are beyond their technical expertise but have no idea why they would even need such a stack.
Kind of a crazy thing to ask about here.
…noooooo, it most definitely isn’t.
While the job does deal heavily in automating things, it only automates Boolean things. Looking at a platform and seeing why and where it’s failing is not a Boolean thing, and never will be. It’s the same reason we still don’t have machines that repair cars over 100 years after their introduction.
DevOps cannot be automated away. So stupid.
Anybody buying internet connected furniture is a sucker.
If you’re running the exact same version, just do an apt update and then see if upgrade packages show up.
Honest question: who even uses this bullshit?
It’s an environment variable…
Does this warrant and entire novel about it if you’re working within external source builds? No.
In fact, I think you’d be better off writing a deep dive into what/how environment variables work at build time, and also invoking commands on the CLI.