Earlier quoted context omitted.
Sure, or if you prefer: the price of Debian Stable is that you only get security updates and bug fixes until the next Stable release. It's wonderful.
Except for chromium.
and Firefox.
Never update anything
161–170 of 288 posts
Re: Never update anything
#162Corollary: Do hard things more often, per Martin Fowler - https://martinfowler.com/bliki/FrequencyReducesDifficulty.ht... Upgrade everything all the time and it will never be hard. You'll have full context for breaking changes, and the diff from A to B is always smaller than from A to Q, and less likely to break in strange and confusing ways.
I'm in this camp. I ran into a recent situation where I could have used a drop-in security module if the project had updated the framework in the past decade. Instead we rolled our own, which is janky and took longer than it should have. Debts have a way of compounding. Tech debt is no exception. Tech debt begets tech debt begets tech debt, and it will hang on your velocity like a ball and chain.
Dedicate 20% of developers’ time on constant updates of all components for a decade just in case you might need one drop-in security module ten years after now (if the company ever lives to see that day)? Does not sound like a good illustrative argument to me, I am afraid.
Re: Never update anything
#163Earlier quoted context omitted.
Mac does it, which is why I also quit mac. Some GNU/Linux distributions do it, but not all of them. And I have way more control over it when it does happen. Apple was pretty solid until around Mountain Lion. Once I saw them messing with "Save As", I jumped. I've had good experiences with LXDE and Xfce so far on multiple distros. Anything Gnome are no longer in the running, however.
Looking at Google Trends for GNOME,KDE,LXDE,XFCE from 2004 to present is interesting. https://trends.google.com/trends/explore?date=all&geo=US&q=%... Back then GNOME and KDE stood head and shoulders over all alternatives, whereas these last twelve months, all the Linux desktop choices appear more or less in the same league. Open source sort of behaves the opposite way as markets where instead of shakeout we get shake…
Interestingly just removing the US location restriction it looks quite different, with KDE being far more frequently searched for than the others at the moment. Searches for Linux desktop environments look to have reduced a lot in total since 2004, on Google at least. https://trends.google.com/trends/explore?date=all&q=%2Fm%2F0...
Re: Never update anything
#164Earlier quoted context omitted.
whoa, do you have a link?
https://imgur.com/dCxh2Dd (sorry. Looks terrible on phones) https://forums.aws.amazon.com/ann.jspa?annID=8499 So obviously I was embellishing the language, but the sentiment remains the same. I found this because I checked the RDS admin panel, which I rarely do. I didn't get an email. It was very alarming to discover and makes me anxious about what other forced upgrades I'll miss. I appreciate the point of this, but…
The lesson here is to use proper hosting instead of AWS or some other fart cloud.
Re: Never update anything
#165Earlier quoted context omitted.
https://imgur.com/dCxh2Dd (sorry. Looks terrible on phones) https://forums.aws.amazon.com/ann.jspa?annID=8499 So obviously I was embellishing the language, but the sentiment remains the same. I found this because I checked the RDS admin panel, which I rarely do. I didn't get an email. It was very alarming to discover and makes me anxious about what other forced upgrades I'll miss. I appreciate the point of this, but…
Easy to blame AWS, but as the post you linked said, Postgres 9.6 is no longer going to be receiving updates from 11 November. What do you want AWS to do here? Keep running software that won't get security updates? That seems a bit wild to me. Communication could have been better, but there is no universe in which a managed database provider should be expected to continue to maintain instances with discontinued versio…
> What do you want AWS to do here? Keep running software that won't get security updates? That seems a bit wild to me.
PostgreSQL is open source, so they could keep patching the old version with security fixes.
Or... they could keep using just the community-supplied free-of-charge version and pocket all the money from not maintaining security patches themselves.
Re: Never update anything
#166Few interesting areas:
- JS dependencies are a problem because of the sheer number, which is really because of all the authors of the dependencies and how they update, backwards compat or not etc. if you had 10 big things by 10 authors they would coordinate better than 1500.
- The Lazarus example is interesting but “trusted components” also means walled gardens, who gets to choose? Is there competition? How is that decided in vs out? Logical conclusion to much of this ends up with a central community package manager like maven central..
Re: Never update anything
#167"When your company won't be the first to market, because about 20% of your total development capacity needs to spent on keeping up" In the world of JS and Typescript this ratio looks more like 80%. I swear that node hipsters at my last job spent four out of five of their working days wrangling with dependencies or their transpilers, linters, packagers, bundlers and whatever the hell else needs to happen to actually m…
> I swear that node hipsters at my last job spent four out of five of their working days wrangling with dependencies or their transpilers, linters, packagers, bundlers and whatever the hell else needs to happen to actually make a node program run.
Like they say - a cushy job if you can get it.
Re: Never update anything
#168Timely. I was recently force upgraded to Win11. Today in fact. Last week I force-downgraded after I got an exception because it is my busy time of year. That exception was not respected and I realized fighting it weekly would be the same time investment as fixing compatibility issues. "What compatibility issues? Win11 is fine, I have had no problems." My coworkers say. Well on Day 1, 2 pretty important pieces of soft…
Why not just get LTSC? You get zero feature updates (ie. the breaking kind) pushed on you, but you still get security updates for up to 10 years.
Ignoring the licensing issues, LTSC failed for me. Just literally wouldn't boot one day.
It's probably something hardware related, but the Pro version works great so far, even if it ignores update time and sticks my files into a black hole because it thinks it's a virus.
Hopefully the last version I'll use on bare metal as I move away from soldered processors and more centralized garbage.
Re: Never update anything
#169Timely. I was recently force upgraded to Win11. Today in fact. Last week I force-downgraded after I got an exception because it is my busy time of year. That exception was not respected and I realized fighting it weekly would be the same time investment as fixing compatibility issues. "What compatibility issues? Win11 is fine, I have had no problems." My coworkers say. Well on Day 1, 2 pretty important pieces of soft…
Might come in useful to others on Win11:
To get the snipping tool working, close the snipping tool, manually set the date to around the start of October. Reopen the snipping tool and it should be working. The date can now be set back.
Re: Never update anything
#170"When your company won't be the first to market, because about 20% of your total development capacity needs to spent on keeping up" In the world of JS and Typescript this ratio looks more like 80%. I swear that node hipsters at my last job spent four out of five of their working days wrangling with dependencies or their transpilers, linters, packagers, bundlers and whatever the hell else needs to happen to actually m…
Where I work, its quite the opposite, every microservice is built with js/ts and we have a big monolith built in java.
The java service releases every month or so, the microservice, on average, release every week, sometimes more.
You can build bad software with any tool, it all depends on how you use it.