Spotify releases native ARM client for Windows
source link: https://www.neowin.net/news/spotify-releases-native-arm-client-for-windows/
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
18 Comments - Add comment
Cool. Hopefully it auto updates to that version when it's available.
It has taken 10 years since Arm-only Windows RT released in 2012…
for Spotify to ship a native Arm64 client.
10 years.
It has taken 10 years since Arm-only Windows RT released in 2012…
for Spotify to ship a native Arm64 client.
10 years.
Much of Microsoft’s own software doesn’t run on ARM, so should we be surprised?
It has taken 10 years since Arm-only Windows RT released in 2012…
for Spotify to ship a native Arm64 client.
10 years.
Well, there are a lot of moving parts, tbh. Don't want to defend Spotify, but that's how we will need to deal in the Windows ecosystem. There's very little incentive for developers to port to ARM
Well, there are a lot of moving parts, tbh. Don't want to defend Spotify, but that's how we will need to deal in the Windows ecosystem. There's very little incentive for developers to port to ARM
Your last sentence is the reason. The first doesn't really matter.
It has taken 10 years since Arm-only Windows RT released in 2012…
for Spotify to ship a native Arm64 client.
10 years.
The world is still waiting for Spotify to release a bug free client, so this is a record for them! 
It has taken 10 years since Arm-only Windows RT released in 2012…
for Spotify to ship a native Arm64 client.
10 years.
Unless they developed a Metro App at the time (which few developers had any interest in) Windows RT was a no go back then. It had to be Jailbroken to run any apps recompiled for the ARM architecture, as Microsoft didn't want people doing this.
Much of Microsoft’s own software doesn’t run on ARM, so should we be surprised?
Curious which software you're referring to. Because from what I've seen the situation has gotten a LOT better of late. Office apps are all either native or hybrid apps, and that's been true pretty much from the beginning (even on RT). Teams has had a native app for awhile now. Visual Studio is even getting a native version in the near future. What am I forgetting?
Server apps I don't expect to run on a client OS, and games would depend on system requirements of the game. Minecraft runs, but Flight Simulator for example is to much for a Surface Pro 7/8 so an ARM version is pointless.
Curious which software you're referring to. Because from what I've seen the situation has gotten a LOT better of late. Office apps are all either native or hybrid apps, and that's been true pretty much from the beginning (even on RT). Teams has had a native app for awhile now. Visual Studio is even getting a native version in the near future. What am I forgetting?
Server apps I don't expect to run on a client OS, and games would depend on system requirements of the game. Minecraft runs, but Flight Simulator for example is to much for a Surface Pro 7/8 so an ARM version is pointless.
Lets see:
Visual Studio
Azure Storage Explorer
Teams only recently went to beta with ARM support within the last month
Azure Data Studio (last I checked)
I am sure I can find more if I feel like digging; this is just an example. Just because some of these run on WoA doesn't mean they are ported to ARM. Them not porting their games due to hardware requirements just removes any motiviation for OEMs to provide needed hardware specs, and then other developers are going to follow suit.
Lets see:
Visual Studio
Azure Storage Explorer
Teams only recently went to beta with ARM support within the last month
Azure Data Studio (last I checked)
I am sure I can find more if I feel like digging; this is just an example. Just because some of these run on WoA doesn't mean they are ported to ARM. Them not porting their games due to hardware requirements just removes any motiviation for OEMs to provide needed hardware specs, and then other developers are going to follow suit.
Sure, blame the new kids (Azure, Teams) rather than the streaming media platform that's been consumer-focused since their inception (Spotify).
Also, SSMS/ASE/ADS are ostensibly redundant products; they all interconnect with the same data sources. Breaking them apart is rather silly. (And yes, I know ASE refers to the object storage rather than the SSMS/ADS branching, but it's still data objects all of the same.)
Sure, blame the new kids (Azure, Teams) rather than the streaming media platform that's been consumer-focused since their inception (Spotify).
Also, SSMS/ASE/ADS are ostensibly redundant products; they all interconnect with the same data sources. Breaking them apart is rather silly. (And yes, I know ASE refers to the object storage rather than the SSMS/ADS branching, but it's still data objects all of the same.)
I am not blaming them, I am pointing out what was asked from me.
They are separate applications, it makes sense to break them out. On top of that, that they are "new kids" as you put it, ALL THE MORE REASON they should have been ARM all along.
Edit: Wait you are right, I forgot MS is a small indie developer and didn't have the resources to support ARM64 until now.
It has taken 10 years since Arm-only Windows RT released in 2012…
for Spotify to ship a native Arm64 client.
10 years.
Uh... that's just not true, unless you have some sort of insider knowledge.
Spotify didn't release in the US until 2011. I followed their service from day one so I believe it's rather far fetched to think they were somehow worried about releasing to an unproven platform, that Microsoft struggled to even release to.
Lets see:
Visual Studio
Azure Storage Explorer
Teams only recently went to beta with ARM support within the last month
Azure Data Studio (last I checked)
I am sure I can find more if I feel like digging; this is just an example. Just because some of these run on WoA doesn't mean they are ported to ARM. Them not porting their games due to hardware requirements just removes any motiviation for OEMs to provide needed hardware specs, and then other developers are going to follow suit.
As noted, Visual Studio is coming native soon (yes, it would have been nice earlier, but it is coming) and Teams? In the last month? Teams for Windows AARCH64 has existed since October 2020, almost two years ago
As noted, Visual Studio is coming native soon (yes, it would have been nice earlier, but it is coming) and Teams? In the last month? Teams for Windows AARCH64 has existed since October 2020, almost two years ago
Source?
Teams didn't come to Apple Silicon until last month and thats a fact.
Edit: I stand corrected, it was just AS wasn't available until last month.
I get the support is coming, but clearly so is other support from third parties. My point is, until MS invests in the architecture, its not going to go anywhere for Windows applications. Now that they are, others are following suit. Had it happened sooner, so would it with other applications. You won't get faith in a new architecture if the OS vendor doesn't invest in it.
Apple went all in and while the first couple of years were pretty rocky, the ecosystem is decently robust now. Of the numerous applications I have installed, only 2 or 3 are Intel, most of which are MS.
Source?
Teams didn't come to Apple Silicon until last month and thats a fact.
Edit: I stand corrected, it was just AS wasn't available until last month.
I get the support is coming, but clearly so is other support from third parties. My point is, until MS invests in the architecture, its not going to go anywhere for Windows applications. Now that they are, others are following suit. Had it happened sooner, so would it with other applications. You won't get faith in a new architecture if the OS vendor doesn't invest in it.
Apple went all in and while the first couple of years were pretty rocky, the ecosystem is decently robust now. Of the numerous applications I have installed, only 2 or 3 are Intel, most of which are MS.
Your last sentence basically sums up the difference between Apple's and Microsoft's approach. Microsoft can't exactly go all-in on ARM because ditching Intel and AMD would be suicided. So they have to take a different approach, which so far has been slow and steady. Also why Apple can ditch Rosetta after a few years whereas I doubt we'll see the x86/x64 emulation layer go away anytime soon.
I can't help but wonder if a native Visual Studio was even a real option before now, as there was no 64 bit (x64) version until VS 2022 either. Maybe they could have release a 32bit ARM version perhaps, but that may not have been worth the time or money when they already had a roadmap for finally releasing 64bit versions.
You have a point about the Azure utilities, but I'm not so sure about SSMS. I guess I'm not really a DBA, but the few SQL databases I've managed in the past I've just used SSMS via RDP on the server itself. I expect that would may via emulation, though without trying it I don't know how well it works.
Sweet! I use the current x86 version on my Surface Pro X, but the interface it always a bit sluggish. Once audio starts it's fine. I look forward to having a native version.
To be honest though, I'm not sure if I want to try the beta or not. I suppose I probably should just to help support the effort, and I don't think the one known issue would affect me. Spotify came pre-installed from the Microsoft Store, which appears to be a win32 app packed for the store, and from what I've ready it basically the same app.
Sweet! I use the current x86 version on my Surface Pro X, but the interface it always a bit sluggish. Once audio starts it's fine. I look forward to having a native version.
To be honest though, I'm not sure if I want to try the beta or not. I suppose I probably should just to help support the effort, and I don't think the one known issue would affect me. Spotify came pre-installed from the Microsoft Store, which appears to be a win32 app packed for the store, and from what I've ready it basically the same app.
I've replaced the normal version with the beta as so far the only issue I've had is touching the maximize button doesn't seem to work correctly, but clicking it does. The beta is incredibly snappy so I do suggest giving it a try
I've replaced the normal version with the beta as so far the only issue I've had is touching the maximize button doesn't seem to work correctly, but clicking it does. The beta is incredibly snappy so I do suggest giving it a try
Nice! I'll definitely give it a try then.
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK