Template talk:Latest stable software release/Spotify
 | This template does not require a rating on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||
| |||||||||||
Codebase for Spotify desktop clients
[edit]Hey @LocalNet: Yes, the desktop clients do indeed share the same codebase, the core codebase is entirely written in C++, with minor platform adoptions added to the codebase, but yes, the Windows and macOS clients are updated at the same time via Spotify's updater mechanism. As per a quote from Quora from a Spotify employee (answer located here) (somewhat outdated, but most of it still applies except for the apps part):
Clients for desktop, mobiles and our embeddable library, libspotify, all share a common code base. Each client then builds on this core to provide user interfaces and other platform specific adoptions. The shared code base is written in C++ and the platform adoptions in the platform native languages, e.g. ObjC on iOS. Also, many views and apps in the desktop client are now implemented as web apps, using an embedded instance of Chromium.
Hopefully that explains everything in better detail. :) - Kamran Mackey (Talk to me) (My contributions) 10:43, 11 March 2017 (UTC)
- @KamranMackey: Thank you for the post! I fully understand that you are correct now that they do share the same codebase, but what worries me a little bit is how much readers on Wikipedia will understand about that. For example, based on that Quora post, all platforms, including mobile, share the same codebase, just with minor platform-specific changes, and that also means the Android and iOS apps are closely connected. While you definitely can argue that equal version numbers and same update date make Windows and macOS versions the same, I'm just not entirely sure there is a downside to providing both Windows and macOS versions. I'm thinking this: Are there any downsides to providing both Windows and macOS? And our Windows FileHippo source only lists compatibility with Windows, not with macOS, breaking the verifiability policy if we include both macOS and Windows. LocalNet (talk) 11:09, 11 March 2017 (UTC)
- @LocalNet: It just makes the template cluttered. Why have two separate version branches for desktop, when we can just use two sources for the single "Desktop" entry? Which is what I just did. I made an edit to the template to where we use both the Windows and macOS FileHippo sources, while keeping the single "Desktop" entry. - Kamran Mackey (Talk to me) (My contributions) 11:19, 11 March 2017 (UTC)
- @KamranMackey: OK, I just got to stop you for one moment now. As part of WP:BRD, we need to discuss and come to an agreement before further edits are made, otherwise it quickly turns into edit war. Other people on Wikipedia take WP:BRD extremely seriously and could become angry at you now, but I understand this is all in good faith, but I just want to inform you about that. I made one more adjustment by changing "desktop" to specifically state "Windows/macOS", as "desktop" is ambiguous in that it relates to a specific form of computer, and relates to hardware, not software. But now I think we're good. LocalNet (talk) 11:24, 11 March 2017 (UTC)
- @LocalNet: It just makes the template cluttered. Why have two separate version branches for desktop, when we can just use two sources for the single "Desktop" entry? Which is what I just did. I made an edit to the template to where we use both the Windows and macOS FileHippo sources, while keeping the single "Desktop" entry. - Kamran Mackey (Talk to me) (My contributions) 11:19, 11 March 2017 (UTC)