Every time I’ve tried to run a standard Linux distro like Ubuntu for more than a couple of years I inevitably end up breaking something in a way that I can’t recover.
Don't use custom repos, use container technologies (e.g. Flatpak, Docker etc) to install applications, update the system regularly (at least once a week).
Usually broken distro upgrades I see are because people run "curl randomdomain.ck/totallysafescript.sh | sudo bash -" to install things or use custom repos.
This is why I like Arch's Pacman a lot, and the reason why I avoid Debian derivatives.
That `totallysafescript.sh` could at least be inside of the package manager scope. Most of the times someone already did it, and published it to AUR.
IMO the reason why there are so many people running random scripts in Ubuntu/Debian is due to how more difficult/inconvenient it is to get a dpkg .deb when compared to a PKGBUILD file. Same for MacOS, in which you have to either rely on Homebrew wizardry or just running the script
> That `totallysafescript.sh` could at least be inside of the package manager scope. Most of the times someone already did it, and published it to AUR.
The AUR is still not as good as proper package management and shouldn't be considered a stable or reliable method of software distribution at scale.
I hate Flatpaks; they're bloated monstrosities and I only run them when I have no other choice. Outside of that, distribution package maintainers tend to do a good job and that is my preferred way of running programs.
container stuff breaks the MOST for me. The hooks into the subsystems invariably are not working correctly be it like xdg preferences or finding things that are global, its nice to package things into their own sandboxes but those sandboxes have not played well with my wider systems. I am still thankful for snap getting me recent copies of popular software on my aged debian installs however.
I have had the same experience. Don’t run random commands from the internet, don’t install anything that doesn’t come from the distro vendor (a few very notable exceptions can be made for things like Docker if you really must), don’t mess with configuration files, do upgrades their way. Generally speaking you will have zero problems. Sometimes they will do something like switch from one network manager to something like netplan but overall that stuff is trending towards ease of use, not complexity.
If you install the newest versions of whatever from random repos or compile stuff yourself you are very likely to mess things up. But nowadays there is very little reason to do that. And you can pick a distro that releases at a pace you are comfortable with, so you have choices.
It's not a good distro. I don't know why people insist on using it. Notice that the GP said Debian instead. (Probably Stable, because testing and unstable will break within 10 years.)
This experience has been unique to (k)ubuntu (more than 15 years ago) for me.
I've been running rolling release distros for a decade and never had any problems - you have to follow some software migrations when needed, but I managed to migrate to systemd on Arch without an issue while any dist upgrade on ubuntu was wrecking my system.
I'm not saying accept it. I am a vocal critic of the RTO policy at my work and have been for years.
But keeping context and perspective is important. Even in your example, it would do the security guard some good to take a moment and be grateful that he does have that minimum wage job and a place to stay.
It's not meant to encourage you to settle and get screwed over. It's meant to remind you of what you have and often those things should drive you to fight harder for other people and yourself.
While I see your point I don’t think it’s a very useful one. It’s more productive to aspire for the betterment of your own/group’s position/circumstances than to compare how other groups have it worse. The latter just brings complacency, stagnation and maybe even regression because there is always someone who has it worse and so on and so forth.
You may be right, but I think you can have those examinations and comparisons without necessarily falling into complacency. I think that only happens if the forces driving you are mostly external.
I mean, that occurs anytime these labor changes happen in general. Anytime they can appear to align themselves with workers while actually furthering their own ends, they will.
Doesn't mean that advocating for blue collar workers is wrong just because the "founders" are doing it too. Instead we should actually hold them f-ing accountable to what they claim to believe and support when this happens.
All you are arguing for is that Dropbox should never have hired these people in the first place. Why is that better? At least these people got some years of high pay, experience, networking relationships, etc. Obviously it's disruptive, and it could be a big net negative for people who maybe jumped ship from more stable jobs only to be quickly laid off, but that's not the broad experience.
I suppose it's largely a matter of perspective but I would argue that fewer more stable jobs would likely be better for both the companies and employees.
Also, you're missing another obvious argument. Most tech companies that are doing layoffs could afford to keep their employees. Dropbox hasn't done 3 rounds of layoffs because they're on the verge of bankruptcy but rather they're just following the trend and pleasing shareholders or whatever.
So I'm not arguing for less jobs but rather less corporate bullshit.
>I suppose it's largely a matter of perspective but I would argue that fewer more stable jobs would likely be better for both the companies and employees.
How do you expect this to work? Companies hire because they think the extra man-hours is going to give them a competitive advantage. Companies agreeing not to compete each other seems suspiciously like a cartel.
They can still hire people and compete with each other? I'm just saying they shouldn't hire in mass quantities if there's a high chance that all of those people will be let go later on. It seems unethical to me but again it's a matter of perspective.
>They can still hire people and compete with each other?
That's still cartel behavior. If Google and Apple formed a cartel to fix handset prices, they could still theoretically compete with each other on features or whatever, but that'd still be a cartel.
"It's no secret that tech companies have not been hiring for sustainability and that sucks."
Does it suck? It means that someone got a job where they didn't really have to do that much and got paid anyway.
An alternative is where that job was never offered. And then we're complaining that there's no jobs.
Also, no, the solution is not to "just hire the perfect amount". Sure if we could just do anything perfectly everything is great, but how is that a reasonable demand.
Unless you have heavy experience hosting and tuning prometheus, its not easy to be that cost efficient. It has a tendency to OOM crash on heavy queries if enough memory isnt provided, and provisioning huge memory for occasional queries becomes expensive quickly. Not to mention backups and replicas.
The actual mileage may vary here - we found this to be true for our early customers. Our pricing is simple, and transparent - https://oodle.ai/pricing. Based on our conversations, we consistently hear this is very cost-efficient. Pls let us know if you feel otherwise - but one can can easily input the #active time series / hour to get an estimate from Oodle.
Even with compound interest $100/mo is only going to yield retirement like savings over 40 years with >=10% interest rates and monthly compounding.
It also neglects the fact that the cost of retirement might be much higher when that time comes.
Your whole spend less argument ignores the whole point of the article. These disillusioned people aren’t going to spend less because they don’t think it’s going to pay off. They’re optimizing for happiness in the present moment and that might end up being the right choice.
Every time I’ve tried to run a standard Linux distro like Ubuntu for more than a couple of years I inevitably end up breaking something in a way that I can’t recover.
Are you taking snapshots to roll back to?
reply