in the download section we can find “stable” releases named as
And in nightly builds these are:
And there is no explanation to which is which can be found.
Traditionally, public download folders in nix world contain some kind of description text file, what’s where, and how is it named. But for some reason not in paraview download area.
So, talking about extension, it speaks for itself. Any notion about exe would be useful, though; is it sfx or installer, or an adware.
Next we come to MPI. It is googlable, and HPC cluster users are familiar with it. But there are other simple people in science, who nave no education in IT.
Well, and just 2% of PC users understand Qt, generally from Linux world.
Linux’s Qt5-MPI-Linux-64bit.tar.gz and plain MPI-Linux-64bit.tar.xz difference is not clear, but I guess the latter is a console render-server without GUI. (can you confirm?)
Two things I totally do not understand, is why there are three (!3!) kinds of Windows binaries, for MPI, or standalone machines!?
msvc2015 is probably a compiler bundled with specific msvc.
But how do developers choose this or that compiler, how are those characterized, pros and cons?
I thought, in MSVC the important is not the compiler itself, but compilation options, impacting compiled software weight, performance, and compatibility.
Then, what is
MSVC2008? Well, I made a research, it is gcc. But it is not clear, will it always be gcc 4.x, or something else, llvm?
Therefore the final question:
What is the “stable” ParaView-5.5.2-Qt5-Windows-64bit.exe
There is totally no notion. With hard work against the wall I found, that it is MSVC2013. The error log record told me it, because “stable” paraview is not working well in Windows (ver 5.5.)
Why MSVC2013, not others? Will others crash the same way? What version do developers use, when confirming or not confirming your bug-reports?
Too much is unclear about builds, I think, before you try them all one by one.
There are also installation instructions, another old tradition, absent.