INTERACT FORUM
More => Old Versions => JRiver Media Center 31 for Windows => Topic started by: antenna on September 12, 2023, 02:19:00 am
-
I am not sure where to ask this question. Please move it to the appropriate place if this place is not correct.
Here's what I see..
I went to the LInux sub-forum to see what the current version for Linux is. It was: JRiver Media Center 31.0.53 for Debian BULLSEYE (amd64) https://yabb.jriver.com/interact/index.php/topic,136963.0.html
So then I go back to the main forum and see that the current version for Windows is: JRiver Media Center 31.0.52 for Windows
Is the development for Linux of MC now moving forward more quickly than the Windows development?
Note that I do not necessarily view that as a bad thing, it is just something new for me. And odd to see the Linux version number out in front of the Windows version number.
I don't ever remembering seeing that for MC previously. Usually there is a lag.
Has something changed? Or is this instance some manner of an infrequent quirk?
-
Those builds are usually built at whatever build number they're currently at, but keep in mind there are Windows beta builds (for the beta tester team) that are tested first. Publicly posted Windows builds usually lag behind.
Basically, it's normal. And I wouldn't put much stock in the Mac/Linux versions being a higher build number, it's really not and it doesn't actually matter that the Mac/Linux build numbers are, at the moment, higher. Look at the changelogs, they should largely be the same.
-
@antenna
You may or may not be aware of JRiver's development model for these different platforms. The vast majority of the code for all platforms (Windows, Linux, Mac) are THE SAME. They have abstracted most of the platform specific stuff (window drawing, audio handling, etc) so that the same code can be used on all platforms.
There are still some things that are different about each platform, but as I understand it, it's not all that much. So, new builds come out for each platform whenever the person that compiles that version decides to compile it.
The key point here is that none of the non-windows platforms are "separate". Nor are they "ports" of the windows code. The code is (largely) exactly the same. Therefore they are actually developing all the platforms simultaneously through a single code base.
For me this is EXTREMELY impressive. Applause for the JRiver development team!!
Brian.
-
> For me this is EXTREMELY impressive. Applause for the JRiver development team!!
I agree. I've mentioned my admiration for the developers in a few prior comments. thx for the explanation.
(thx also to Awesome Donkey for the reply.)