←back to thread

The tragedy of running an old Node project

(abdisalan.com)
272 points abdisalan | 2 comments | 18 Nov 24 18:24 UTC | HN request time: 0.417s | source
Show context
Etheryte ◴[19 Nov 24 11:02 UTC] No.42182143[source]▶
Can't help but feel that this is a massive nothing-burger. You wouldn't generally expect your Java project to run if you use an incompatible version of the JVM, nor would you generally expect your C++ project to build if you swap one compiler for a different one. Etc, always specify what your project relies on, whether it's in the readme or in the dependency tree.
replies(2): >>42189184 #>>42189321 #
1. jcelerier ◴[19 Nov 24 23:47 UTC] No.42189321[source]▶
> nor would you generally expect your C++ project to build if you swap one compiler for a different one.

it's absolutely the expectation for C++ projects to support building on GCC, Clang and MSVC

replies(1): >>42189413 #
2. Etheryte ◴[20 Nov 24 00:01 UTC] No.42189413[source]▶
Maybe these days this is the case, last I used C++ about a decade ago though, this was most definitely not guaranteed to be so. This thread [0] is a good quick overview of the type of issues you used to run into, and often you didn't even need anything fancy to hit those edge cases. If life has improved in the meanwhile, that's good of course.

[0] https://stackoverflow.com/q/51866968/1470607