Tens. Out of thousands.
That's always a very separate codebase running either Vulkan or that low-level NV API (NVN?).
Tens. Out of thousands.Lots of older games
That's always a very separate codebase running either Vulkan or that low-level NV API (NVN?).Nintendo becoming open to more hardcore type 3rd party games for Switch may pay dividends in the future for native games on WoA.
For now at least, but I certainly don't see MS being in a rush to tether themselves to Qualcomm the same way they have been to Intel all these years.
More likely they would wait until QC and software partners did the heavy lifting of making WoA viable in the long term, and then switch to ARM permanently with their own custom SoCs to further follow Apple's business model.
Surfaces are an odd job, they're not available in many markets are generally are overpriced for what they offer.I don't see it is the lack of Microsoft's of SoC that is standing between them and world domination. I think it is the management of the Surface division, and broadly the entire client part of Microsoft.
They can't sell Surface even while having the Microsoft license for free and wile having the Microsoft name on the sticker...
True.I don't see it is the lack of Microsoft's of SoC that is standing between them and world domination. I think it is the management of the Surface division, and broadly the entire client part of Microsoft.
They can't sell Surface even while having the Microsoft license for free and wile having the Microsoft name on the sticker...
WP disaster started before that, with WP7 having initially (I don't remember if it was added postfactum, pre-WP8) native 3rd party apps, only Silverlight garbage.The Nokia disaster
WP disaster started before that, with WP7 having initially (I don't remember if it was added postfactum, pre-WP8) native 3rd party apps, only Silverlight garbage.
Then WP8 itself forced existing WP7 phones into legacy mode.
MS basically pressed the reboot button on their mobile efforts twice in span of two years, thus alienating any developer base it could've had.
Mostly just sad that they effectively killed my favourite phone maker 😒WP disaster started before that, with WP7 having initially (I don't remember if it was added postfactum, pre-WP8) native 3rd party apps, only Silverlight garbage.
Then WP8 itself forced existing WP7 phones into legacy mode.
MS basically pressed the reboot button on their mobile efforts twice in span of two years, thus alienating any developer base it could've had.
Oh yeah, gigabrain move from MS it was.WP7 never got non-Silverlight APIs. Native APIs came with WP8, along with the switch to NT.
Nokia became suicidal and meandered in the dark way before their commitment to Windows Phone.Mostly just sad that they effectively killed my favourite phone maker 😒
Microsoft can’t even sell consoles. Forget their computers.I don't see it is the lack of Microsoft's of SoC that is standing between them and world domination. I think it is the management of the Surface division, and broadly the entire client part of Microsoft.
They can't sell Surface even while having the Microsoft license for free and wile having the Microsoft name on the sticker...
Yep, NVN and soon to be NVN2 when Switch 2 comes out.Vulkan or that low-level NV API (NVN?).
Having video games to show really is a boon in this day and age.Nintendo had a great direct today, gonna plug that in somehow lol
Consoles are a different issue, Spencer is too hands off with studio management.Microsoft can’t even sell consoles. Forget their computers.
WP disaster started before that, with WP7 having initially (I don't remember if it was added postfactum, pre-WP8) native 3rd party apps, only Silverlight garbage.
Then WP8 itself forced existing WP7 phones into legacy mode.
MS basically pressed the reboot button on their mobile efforts twice in span of two years, thus alienating any developer base it could've had.
It never had any, iOS and Android both were reaching critical mass by early 2013.without giving it a chance to catch on.
Freedom from Wintel. Or at least that was the idea.What does WoA / WARM bring to the table?
Yeah, bad timing on QC side of things.But between Lunar Lake and Strix Point, this whole WoA is just redundant.
Microsoft can’t even sell consoles. Forget their computers.
It never had any, iOS and Android both were reaching critical mass by early 2013.
Pressuring the reboot button twice in the span of two years was a BAD idea. plain and simple.
All they had to do was to make WP7 NT-based from the get-go with native SDK and continuing the multi-vendor push strategy from the WP7 launch window instead of effectively committing to single source (Nokia).
Freedom from Wintel. Or at least that was the idea.
Yeah, bad timing on QC side of things.
But WoA efforts, persistent as they are, so far always been like that.
It's either mid parts or just stuff sitting in the wrong market segment.
Stuffing pre-8cx g3 parts into Very Expensive Devices instead of $600 !netbooks was the biggest, dumbest market misread one could ever pull off.
Wasn't a battle, it was dead before it was ever alive.It was an uphill battle, that's for sure.
WoA devices shipped 2017.Which Microsoft could have partially achieved if it had given AMD a chance, instead of shooting AMD in the foot.
yes they want to make WoA real for strictly "we hate Intel" reasons.It seems MSFT is still playing games, pushing Arm ahead of x86. Giving 0% market share Arm "exclusive features", and apparently Window license discounts / rebates.
Wasn't a battle, it was dead before it was ever alive.
WoA devices shipped 2017.
in 2017, AMD had RAVEN which is lmao.
yes they want to make WoA real for strictly "we hate Intel" reasons.
sunk cost etc, plus still, freedom from Wintel is worth a lot.By that, I meant recently. Instead of putting so much behind the most recent incarnation of WoA, Microsoft could have achieved more independence from Intel by giving more of a chance to AMD on the client side.
Well, MS is betting on other vendors than Qualcomm now so kinda?It seems like some sort of extreme marriage dysfunction, where instead of a divorce / break up, one party goes even deeper into bed with the dysfunctional partner, and when things get worse, comes out as gay.
It wasn't a year before but 5 months before M1 launch. But yeah they did release a dev kit at wwdc june 2020 and M1 came out nov 2020.
3. Qualcomm made claims it must have known would fall flat on it's face extremely quickly (see: every time they tried to compare their iGPU to Intel/AMD when in reality it's not even close to being competitive)
I'm also trying to use the standard Whisper AI python library, which is not maintained by Qualcomm. But that isn't working on this hardware. It gives a Numpy error because apparently Whisper requries Numpy, a popular Python library, that's less than version 2. But Numpy less than version 2 won't install on Arm64 hardware, at least as far as I can tell.
I'm still working on these problems, but the level of difficulty and awful documentation suggests that it may not be possible to build working AI apps in Python for Snapdragon. Qualcomm's AI hub is full of proofs of concepts of hundreds of models, from those that to image generation to pose estimation to transcription and yet, instead of showing users how to actually use these models in applications, it offers demos with its own pre-chosen audio, images, etc. Intel actually has useful libraries and documentation, however poorly written, for its OpenVINO libraries. Qualcomm, not so much. I'm very frustrated.
Wait for Nvidia SOC for that.X Elite is not even good for AI?