Dispute of "block running on EOL Windows versions #31954" - Alternative Suggestion

[xCykrix]

Is your feature request related to a problem? Please describe.
Dispute of PR #31954

Describe the solution you'd like
Changing of "Windows 8.1+ Required" to a warning regarding the usage of EOL operating systems that may inexplicably lead to the software failing to function for any reason.
Continuing support of Windows 7 at its EOL, even in a minimal state, up until the point that it becomes a burden to the active scope of the project.
It is currently in a known working state at the last version before 14.0.0, and I believe it will continue to work for the near future given that no significant changes will be made to Windows 7... ever...

Describe alternatives you've considered
I cannot see any possible alternatives besides removing the commit in a local fork and compiling the binaries myself.
This could also be circumvented by using a Linux virtual machine, but that is a significant hassle and is the last resort for me.

My full schpeel
While I struggle to understand the reasoning behind this, I deeply disagree with #31954 restricting the ability to use Windows 7.

I feel this should be removed and/or at least optional in some form. This could be achieved with a warning at runtime instead of failing to enter runtime) to the risk of using an EOL operating system that may result in the software inexplicably not working. Even going as far as offering minimal support for EOL operating systems if you do not wish to support this operating system any further past compiling it with its known working state.

Windows 10 left a bitter taste in the mouth of many with poor quality control and update mechanics. Given that Windows 7 is quite stable at its End of Life, I believe it should be supported up until a point that it cannot be supported any longer due to limitations in the scope of the project that prevents it.

[xCykrix]

Reference Issue: #33000

[bnoordhuis]

Node.js has been doing that for some time. There are only so much resources to go around and we choose to spend them elsewhere. If you insist on using an unsupported, end-of-lifed operating system, your options are:

1. Use the last version of Node.js that supported Windows 7, or
2. Remove the check and build from source.

I'm closing this as a wontfix.

[addaleax]

Fwiw, I also disagree with the practice of exiting the process if the OS is unsupported. I get that people shouldn’t be using Windows 7 anymore, but if they want to and we tell them it’s unsupported, that’s not really our problem but theirs, right?

@xCykrix If you open a PR that removes the exit(ERROR_EXE_MACHINE_TYPE_MISMATCH); line from src/node_main.cc, I’d approve it. I guess there’s a good chance that other people would disagree, but fwiw, PRs tend to lead to results faster than discussions in issues.

[bnoordhuis]

The current practice came about after ample discussion. The reason I closed this so quickly is that trying to backtrack on it just wastes everyone's time, including the OP's. Please close this again.

[addaleax]

@bnoordhuis Do you have a reference to that discussion?

[bnoordhuis]

@addaleax #3804

[addaleax]

@bnoordhuis I see zero discussion on this particular topic in that thread. The most popular suggestion in it actually seems to be a warning.

I’ll be re-opening this and keeping it open.

[sam-github]

@addaleax I don't understand what is unique to this particular issue was not discussed previously. What I saw was:

• Drop Windows XP (and Vista) support in 6.0 #3804 (comment)
• ctc meeting referenced: https://github.com/rvagg/io.js/blob/3967cb591232e50d2eec3cff3327eaffa9c0081d/doc/ctc-meetings/2016-01-27.md#drop-windows-xp-and-vista-support-in-60-3804

"stop on startup" is specifically mentioned several times, final mention in CTC meeting notes above:

I can make the change to stop on startup