undefined | Better HN

0 pointslocknitpicker3mo ago0 comments

> Certainly that depends on the nature of the software. For instance, I don't expect some header-only library that does what it's supposed to do to ever need updating.

If it's a headers-only library in a language such as C++, if the project is not dead then the very least anyone would expect from it is being updated to support any of the modern C++ versions.

Also, if the project is actively maintained then there is always a multitude of low-priority issues and features to address.

Being FLOSS also means anyone in the whole world is able to contribute anything. If no one bothers to do so, that is aligned with the fact the project is indeed dead.

0 comments

SkiFire133mo ago

> If it's a headers-only library in a language such as C++, if the project is not dead then the very least anyone would expect from it is being updated to support any of the modern C++ versions.

Did I miss a new C++ version released <2 days ago perhaps?

locknitpickerOP3mo ago

> Did I miss a new C++ version released <2 days ago perhaps?

You certainly are missing something. C++26 was officially released 4 months ago, and support is slowly being rolled out to compilers and packages.

https://en.cppreference.com/w/cpp/compiler_support/26.html

If you somehow believe this kind of work is done in a couple of days, that's a good way to explain to the world how oblivious you are about the topic you are discussing.

lelanthran3mo ago

> If you somehow believe this kind of work is done in a couple of days, that's a good way to explain to the world how oblivious you are about the topic you are discussing.

And, in turn, you appear to be oblivious to the point - the release cadence of this best-case scenario still means like a decade between updates to the project.

C++26 was released 4months ago; pointless to update it until compilers and deps are updated. So, best case is maybe you'll have complete bug-tested support in the supported compilers in 2030.

If we're looking at 2035-ish for the next release, we're still only looking at 2040 before you update.

You still have to take into account that updating might not even be necessary. It's not like C++ < C++26 suddenly doesn't work.

1 more reply

SkiFire133mo ago

I think you lost the original context:

> If a project hasn't gotten a new commit in 2 days then the project is claimed dead.

You don't need a commit every day to support C++26, and surely not every day for 3 years until the next major version releases.

drnick13mo ago

> If it's a headers-only library in a language such as C++, if the project is not dead then the very least anyone would expect from it is being updated to support any of the modern C++ versions.

C++ versions are backward compatible. You don't need to modify code that works just to use recent languages features that you don't need.

j / k navigate · click thread line to collapse

0 pointslocknitpicker3mo ago0 comments

> Certainly that depends on the nature of the software. For instance, I don't expect some header-only library that does what it's supposed to do to ever need updating.

If it's a headers-only library in a language such as C++, if the project is not dead then the very least anyone would expect from it is being updated to support any of the modern C++ versions.

Also, if the project is actively maintained then there is always a multitude of low-priority issues and features to address.

Being FLOSS also means anyone in the whole world is able to contribute anything. If no one bothers to do so, that is aligned with the fact the project is indeed dead.

0 comments

SkiFire133mo ago

> If it's a headers-only library in a language such as C++, if the project is not dead then the very least anyone would expect from it is being updated to support any of the modern C++ versions.

Did I miss a new C++ version released <2 days ago perhaps?

locknitpickerOP3mo ago

> Did I miss a new C++ version released <2 days ago perhaps?

You certainly are missing something. C++26 was officially released 4 months ago, and support is slowly being rolled out to compilers and packages.

https://en.cppreference.com/w/cpp/compiler_support/26.html

If you somehow believe this kind of work is done in a couple of days, that's a good way to explain to the world how oblivious you are about the topic you are discussing.

lelanthran3mo ago

> If you somehow believe this kind of work is done in a couple of days, that's a good way to explain to the world how oblivious you are about the topic you are discussing.

And, in turn, you appear to be oblivious to the point - the release cadence of this best-case scenario still means like a decade between updates to the project.

C++26 was released 4months ago; pointless to update it until compilers and deps are updated. So, best case is maybe you'll have complete bug-tested support in the supported compilers in 2030.

If we're looking at 2035-ish for the next release, we're still only looking at 2040 before you update.

You still have to take into account that updating might not even be necessary. It's not like C++ < C++26 suddenly doesn't work.

1 more reply

SkiFire133mo ago

I think you lost the original context:

> If a project hasn't gotten a new commit in 2 days then the project is claimed dead.

You don't need a commit every day to support C++26, and surely not every day for 3 years until the next major version releases.

drnick13mo ago

> If it's a headers-only library in a language such as C++, if the project is not dead then the very least anyone would expect from it is being updated to support any of the modern C++ versions.

C++ versions are backward compatible. You don't need to modify code that works just to use recent languages features that you don't need.

j / k navigate · click thread line to collapse