Live data from Hacker News

Life is too short to depend on unstable software

blog.sidebits.tech

1–10 of 175 posts

Re: Life is too short to depend on unstable software

#3
Well the title mention unstable software but the article discussed about library or API.

Topic wise, backwards compatibility is indeed really important and useful. However to achieve stable API takes long time and effort.

You're either use the tooling now and risking changes albeit small (honestly almost everything programming related has breaking changes at one point), or roll your own API.

Re: Life is too short to depend on unstable software

#4
In theory we all mostly agree with this: stable, well understood software is to be preferred.

In practice, it's not true most businesses or teams want newer software just to be "on the bleeding edge". The bleeding edge is not a goal on its own. What usually happens is that you need a feature (for actual business reasons) that is not available in the older version of the software you are using; or there is a serious bug that is only fixed on the "bleeding edge" version and is nontrivial to backport.

So you often have two choices: make the change yourself in the stable version (risky, time consuming, and can it be considered "stable" anymore once you mess with it?) or move to an unstable version (risky, new bugs).

And that's assuming the software is open source; if it's proprietary you have even fewer choices...

Re: Life is too short to depend on unstable software

#5
post #4

In theory we all mostly agree with this: stable, well understood software is to be preferred. In practice , it's not true most businesses or teams want newer software just to be "on the bleeding edge". The bleeding edge is not a goal on its own. What usually happens is that you need a feature (for actual business reasons) that is not available in the older version of the software you are using; or there is a serious…

How badly do you really need that feature? Why did no one need it a couple of years ago?

Re: Life is too short to depend on unstable software

#6
post #4

In theory we all mostly agree with this: stable, well understood software is to be preferred. In practice , it's not true most businesses or teams want newer software just to be "on the bleeding edge". The bleeding edge is not a goal on its own. What usually happens is that you need a feature (for actual business reasons) that is not available in the older version of the software you are using; or there is a serious…

For personal use, here's the same thing again. Say a Linux user wants to play a game. The stable old version of their distro doesn't play well with the libs/drivers needed to play the game.

So the user must install a newer, less tested, distro. But the goal was not to be "on the bleeding edge" for its own sake; it's playing the game, and there's no other (easy) way.

Re: Life is too short to depend on unstable software

#10
Users of only "stable" FOSS releases almost never contribute, in code, or to its health or longevity. They are leeching it, sometimes over decades.

They don't contribute to testing either, since they just consume releases and ignore development, then wonder loudly why there are bugs.

Don't be that guy... if you want your dependencies to have a long life being maintained, find some time to contribute. Leeching is not contribution.

Post reply on HN