One of our customers does that. It happened multiple times already that one dev fixed an issue in production, and the next regular deployment overwrote everything.
But fortunately, it's just critical infrastructure and nothing important.
The older generations kept leaking contaminated water (reactor coolant), many harbors simply refused entry because they didn't know the risks involved, and I'm pretty sure the decommissioning isn't clear either. The way current laws are set up, it's quite possible that these things go through a few hands and end up on a beach in some underdeveloped country and get dismantled like any other ship under horrible working conditions - but now with the added benefit of nuclear contamination.
No, I'd argue you simply didn't want to invest in the other tools.
Think about it, you probably spent hours on customizing and automating vim, and then say you're faster in that. Well, that's called a habit.
IDE are objectively more powerful and since you can actually see options and navigate quickly, you don't need to memorize every obscure feature.
All the terminal editor enthusiasts are actively holding us back, because they insist everything outside vim is garbage for enterprise and kiddies.
If your tool of choice is actively hostile to new users for no reason other than "that's how it's always been, and thus it's better", well then you're digging a moat to automate your gatekeeping.
I understand it very well. And that's exactly why I'm writing this.
Ok, I can see you have no idea what you're talking about.
Then say, grandmaster delusion, what purpose does vim serve, where it is actually the best tool? Writing code? Hardly, it's way too limited and requires a ton of upfront investment and headspace. Writing config files? Hardly, because if you write these by hand, you're living in the 90s, that's what Ansible, Terraform etc are for.
You just don't want to admit, that vim is nothing more than a habit. Muscle memory.
You're using the terminal, because you're used to it. It is not the better tool, it's simply what you happen to know already.
People who argue with productivity because of some key bindings live in the world of the 80s. You don't just sit there and type code 12h a day, that's not how modern software development works.
And all those blockheads down voting me are caught up in their weird superiority complex. They are the powerful superhackers, and don't understand that we are just highly qualified plumbers.
VIM may have been a very useful tool 20 or 30 years ago, but today it's nothing else but a tool for one's sense of superiority. It's the vinyl of editors.
If you have to type that much code in a terminal, your infrastructure is outdated. Simple as that.
Of course it is like that. You're saying that the complaint is wrong because the author doesn't know the history, and now you accuse me of not understanding you, because I pointed this out.
If you have to accuse everyone of "not understanding", maybe you're the one who doesn't understand.
It's easy to criticize something when you don't understand the needs and constraints that led to it.
And that assumption is exactly what led us to the current situation.
It doesn't matter, why the present is garbage, it's garbage and we should address that. Statements like this are the engineering equivalent of "it is what it is shrug emoji".
Take a step back and look at the pile of overengineered yet underthought, inefficient, insecure and complicated crap that we call the modern web. And it's not only the browser, but also the backend stack.
Think about how many indirections and half-baked abstraction layers are between your code and what actually gets executed.
Most plastics can't be recycled in any meaningful way, so just burn it and use the energy. There are some legitimate uses for plastics, but most of it is wasted.
And always remember: most of the plastic in the ocean is fishing gear, not household waste.
It's always "in mice" or on an extremely small scale for ridiculous prices.
Scientists only develop the first stepping stones, most of which lead to nothing, that's okay. But the university PR > newspaper pipeline leads to everything being a major breakthrough, and that leads to fatigue with the reader.
And that's especially true for Linux and other big projects.
I'm not a kernel or C developer by any stretch, but a few years ago fixed a small bug that caused my knockoff PS2 controllers to act super weird. Nothing serious, something like one constant and maybe 5 lines of code. Would have gladly pushed that upstream, but fuck me sideways is that a complicated process. Patches via email??? And the argument is always "but it works for us", yeah burning witches and slavery also work for some people, doesn't mean it's something to continue doing.
If there isn't a serious revamp, Linux will die a slow death or become just a corporate graveyard product like Cobol.
Not much less. The cheaper ones all have significant drawbacks.
Used phones might be cheaper, but they still rely on someone else shelling out money.
My problem is not my personal financial situation, it's societal. We throw out tons of resources (natural, but also human) out of the window for products that have zero benefit. It's extremely wasteful.
I need a smartphone for my job (authenticator), bank, social life, etc.
Buying a new phone in the range of 500€ and having to replace that every 4-5 years, comes down to about 10€ per month.
Of course I could buy a cheaper phone, but those usually get barely any software updates, which I find rather frightening, and often enough break for other reasons (battery dead, ports worn out, cracked display). So it's not really cheaper.
One of our customers does that. It happened multiple times already that one dev fixed an issue in production, and the next regular deployment overwrote everything.
But fortunately, it's just critical infrastructure and nothing important.