chelgrian

sflocal said:

I swear these "developers" have nothing to do but whine.  Go over to Android's wild-west OS if it's that important to you.

As a developer myself, I'm embarrassed that these children are in the same group.  It's Apple's proprietary product. Get over it.

These people and the CMA simply do not understand the security implications of allowing a 3rd party language runtime that can run 3rd party code that is to say a 3rd party JavaScript JIT on iOS.

I spend my working life trying to increase computer security then these people come along and demand to be shot in the foot it's extremely depressing.

canukstorm said:

wwinter86 said:

Unfortunately, I don't think Apple will use Qualcomm chips.

Apple will do their own implementation.  The next gen AirPods Pro are rumored to be coming later this year.  I wouldn't be surprised if this is when Apple introduced their own take on lossless BT.

Apple will do something that is actually lossless. Despite it's name aptX Lossless is not. It degrades back to lossy if either the Bluetooth data rate drops due to interference or the audio is not losslessly compressible to fit in the ~1Mbit channel.

There is music out there which is quite similar to line noise and simply doesn't compress.

waveparticle said:

OutdoorAppDeveloper said:

waveparticle said:

OutdoorAppDeveloper said:

Apple really needs to start building chip fabs all around the world. The situation brewing between Taiwan and China poses an existential threat to Apple and the entire tech industry. It would cost Apple a hundred billion dollars or more but the investment would pay off for decades to come.

Not true. If Chian reunite Taiwan, it will be swift. Everything will return to normal shortly. And Apple wasted billions of dollars on other nations that are incapable. 

I hope you are right but I expect it would be a huge mess. It will likely be far bigger mess than China's slow take over of Hong Kong with TMSC shut down indefinitely. There would be an immediate scramble to smuggle the experts out of the country. China would want grab experts and equipment itself for its own fabs. The world's tech industry would pretty much shut down as not only would it lose most of its capacity but it would also take time to retool alternate fabs for essential silicon. If you pull half the chips the world uses out of production, almost nothing will work. Thats because you will discover that while you may be able to get the CPU you need, the RAM, controller or SSD will suddenly become unavailable. China taking over Taiwan could be an extinction level event and we have not even discussed how the West will respond when a nation they have sworn to protect and depend upon gets attacked.

You don't know the high tech industry. Why would China shutdown TSM? What China did not Hong Kong has nothing to do with business. It is purely political. Hong Kong people life is the same as before. Further, TSM build chips for Apple, Nvidia, Qualcomm, AMD, etc. China build fabs to meet these demands? The global chip business is far bigger and complicated that can be changed easily. Biden is trying to change it. It will not work well. 

There is no source of cutting edge lithography machines or wafers in China and neither Applied Materials or ASML will sell to China. This would get worse not better in the event of an invasion of Taiwan.

Biden isn't trying to change anything he hardly knows what lithography is. What is happening is that a variety of US companies are taking federal money to improve the availability of cutting edge foundry services on American soil.

They simply do not understand what the iOS App Store does and why it can't work 'like macOS' or 'like Widows'.

mcdave said:

The issue isn’t purely technical. What Apple are asking for is that cross-platform product managers/owners rethink their product architecture, specifically the forking/segmentation and this is no minor decision.
The product pie can be sliced many ways; mobile vs desktop, ARM vs x86, Windows vs macOS. Apple are asking for a separate AppleOS fork which will take time to sink in, let alone implement.

Yes it is purely technical. There is no 'product architecture' to rethink and no 'fork'. For a well written Cocoa Mac app it's a case of ticking a box in Xcode and recompiling and that's it. Any product manager trying to treat x86 Mac and ARM Mac as separate things deserves for their product to fail.

For almost every thing which does not have a Native M1 port on the list in this article I can point to a technical reason why. For example:

MS Teams - It's based on an ancient out of support version of ElectronJS which doesn't have ARM macOS support. Practically the only thing they need to do is move from Electron 8 to Electron 11.
Skype - Same Electron issues as Teams.
Acrobat - This has an entire JavaScript JIT of adobe's own invention in side it so that needs porting which isn't trivial before the rest of it can be ported.
Spotify - Based on the 'Chrome Embedded Framework'. This only gained initial support for ARM macOS in late December 2020 and it's half baked so far as it can't produce universal binaries.
Various bits of creative cloud - Also using Chrome Embedded Framework thus needs proper support there before it can progress.

The list goes on but I'm bored now.