For example, we just saw an article rise to the top of HN in the last couple days about the pathetic state of Apple's developer documentation. Their focus seems to be less providing integrations into their hardware, and more providing integrations into their services. Meanwhile, developers increasingly distrust Apple because of bad policies and press around App Store review. It's a mess.
I agree that Apple could and should help app developers use this cool new hardware. I'm sure there are good people at Apple who're trying. But the company as a whole seems to be chasing other squirrels.
Over the past couple of years, coremltools [1], which is used to convert models from Tensorflow and other frameworks to run on Apple hardware (including the neural engine when available), has gone from a total joke to being quite good.
I had to get a Keras model running on iOS a few months ago, and I was expecting to spend days tracking down obscure errors and writing lots of custom code to get the conversion to work -- but instead it was literally 3 lines of code, and it worked on the first try.
There's probably lots of novel applications of AI/ML that remain to be built because of this limitation. Probably also good fodder for backing your way into a startup idea as a technologist.
On-device detection (“edge ai”) is gaining steam. Apple recently purchased a company called xnor.ai which specialized in optimizing models for low power conditions.
That’s a result of Apple putting effort into hardware + software to make that happen.
If I remember correctly, that's what happened with flux.
Was it on macOS App Store at one point and then kicked off?
That said, it would be silly of them not to in some of these most obvious cases: a flux/redshift comparable feature is now built into most OS’s as we’ve become attached to our devices, and Sherlock was argued by critics of the term to be a natural progression of iterating in their file indexing capabilities.
[1]: https://en.wikipedia.org/wiki/Sherlock_(software)#Sherlocked...
What the fuck guys? Do you just not care about astronomers? Why is it that no one has properly implemented all of f.luxs features?
This doesn't give ARM chips an advantage over Intel CPUs at executing Javascript for obvious reasons, once you know why they added it.
I believe the point is that it's one example (of hundreds, maybe thousands?) of performance paper-cuts addressed by Apple hardware that result in significant performance-per-watt advantages over devices not using Intel CPUs.
Apple's performance boosts will reward those companies who never valued performance. Why would they change their approach now?
Based on the front page of HN, "better" is not a word I'd choose
Apple sees App Store apps, and web apps as having different advantages, and it is in their interest to have the best platform for both.
It’s not just me saying this, they keep saying it too, and proving it by investing in making web apps run better.
Believe whatever you like.
But this means you are also choosing to ignore absolutely enormous investments at every level of the stack that they have made to increase web performance, adopt standards and improve web user experience.
Disclosure: I work at Google on JS libraries, and at one point was in the Chrome org, but my opinions are my own.
You'll probably know better than me but Apple's work on Webkit was presumably worthwhile enough for Google to fork it into Blink (no problem with that but maybe worth acknowledging that fact).
Google forked Blink because for whatever reason they were unsatisfied with the state of Webkit -- nominally because they wanted to take a different approach to multi-process, but there may have been other technological and project direction/pace disagreements. Since then, a number of browsers have switched from Webkit to Blink/Chromium as their engine, and arguably Safari is falling behind on new features and overall quality (weird quirks that require web devs to work around).
If Apple's focus is on getting better power consumption and memory use (esp on mobile) then that's still investing and arguably that does as much if not more for users and the web than adding more features.
PS Let's not forget that Apple are still standing behind WebKit when Microsoft have given up on their own rendering engine so let's give them some credit for helping to avoid a Chrome only web.
It’s hardly obvious that this is best for users in the long run.
I point this out not to say it’s wrong for them to attempt this, but because it makes no sense to use Google’s strategic decisions as evidence of Apple’s intentions or investment.
The method to pin a webapp to the home screen is substantially worse than it used to be.
There was a period where javascript running in Safari ran significantly faster than javascript running in a webapp opened from the home screen, or in any other app opening a web view. Is that still the case, or did they decide to share that function?
Think we can't ignore that the iOS install base has been larger than the MacOS install base. Start looking at it that way and the iOS way of doing things is the norm in the eyes of Apple and MacOS is the odd one out.
Could be, but as far as the new cross platform frameworks are shaping up right now it looks like their strategy is slightly different. Apple is seemingly creating a developer ecosystem to loosley describe interfaces and share them between platforms while they ultimately decide how your UI is rendered. Maybe you're right and one day that means flicking a switch and everything is unified. I also look at something like iPadOS for instance which started as extremely similar to iOS and has now diverged and become it's own thing, different to both the Mac and iPhone.
There should be limits on this. It's sad to be the baby outside the window, drenched in bathwater.
What you are describing is taking this even further in the direction of an information appliance.
I am unconvinced that there is any benefit that your model provides that Apple does not already.
You can already just buy a Mac with AppleCare and install MS office from the App Store.
People may want their choices to be simplified, but they are also going to need to be able to use whatever important new thing comes along. E.g. Zoom or Slack.
I know people who upgrade their Mac every time there is a speed bump and just sell the old one. They would presumably be candidates for this.
I wouldn’t be surprised to see this.
I just don’t see any reason Apple would tie the leased hardware to a limited software bundle.
Yes. For one, there seems to be no Unified API for GPU Computing in the PC Market. And Microsoft doesn't seems to be interested in doing a Direct X version of it.
And for NPU, which is increasingly important for things such as Speech Recognition, ( For many parts of the word where Languages aren't easily typed into, they are the default way of input on their Phone ), Photo Face Recognition without using the Cloud. Increasing use in Graphics, Video, Audio productivity apps. There aren't even any specific Hardware on PC market. ( That is why Intel is desperate to move the XE as a co-processor ). And it will be years if not a whole decade before a PC parts comes up and reach a large enough market volume.
And it sort of makes you wonder 3-4 years down the road when the M1 ( excluding Memory ) becomes a $20 SoC, will we see a variant of Mac cheap enough that will hit back at the 1.5B Windows PC Market. Where Apple current has roughly 110M Mac.
Of course set against that they've lost the ability to run x86 Windows in a VM for legacy business apps (but not sure many were doing that anyway!).
https://github.com/webmachinelearning/webnn/blob/master/expl...
I think Ben is missing something here: that the speed and specialist hardware (e.g. neural engine) on the new SoCs again give developers of native apps the ability to differentiate themselves (and the Mac) by offering apps that the competition (both web apps and PCs) can't. It's not just about running web apps more quickly.