The article is much fluff and few concrete facts, probably can be condensed to "Apple strategy is to be a funnel to AI sevices instead of building it's own SOTA model.
It has good reputation on privacy concerns, user apreciation for it's software products and integration, has a toll booth in the app store and it is working on Gemini integration."
No doubt Apple will surf the AI wave, and all of the above are powerfull advantages.
A compelling history to be the chosen way to access AI services will need to offer good sandboxing, secure gatekeeping of credentials, a modern adaptive firewall to control agents communications, skills to access OS services and core applications, and a core agent that can handle all of the previous concerns.
This will be a massive effort. The good news for Apple is that it will not have competition: these needs OS integration, and a comprehensive design.
The Itanium C and FORTRAN compilers eventually became very, very good. By then, the hardware was falling behind. Intel couldn't justify putting it on their latest process node or giving it the IPC advancements that were developed for x86.
If you wanted to do something similar right now, it's possible to succeed. Your approach has to be very different. Get a lot of advancements into LLVM ahead of time, perhaps. Change the default ideas around teaching programming ("use structured concurrency except where it is a bad idea" vs "use traditional programming except where structured concurrency makes sense", etc)
But no, throwing a new hardware paradigm out into the world with nothing but a bunch of hype is not going to work. That could only work in the software world.
A direct benefit of using `__all__` at module A is better intellisense while editing files that imports A, if A has a small intended public API and many internal usage symbols.
I just tried it and at least the autocomplete in IPython appears to ignore __all__ when suggesting possible imports. I haven't tried any other tools' autocompletes.
If module A has a small intended public API, you can structure it no matter how you want to achieve that. You can put those internal symbols behind their own object/class/module if you prefer.
Using `__all__` has one functional consequence, which is `from A import *`. Again, I would avoid * imports entirely, but if you want to try to curb possible downstream problems from users who do indeed use * imports, I would also prefer not defining `__all__` because it's extra boilerplate you have to maintain and can very easily be missed on future updates.
- More legible than HN, a combo of size and color
- Too much space below short entries ?
- Context menu (rclick) on links hijacked, no 'open in new tab'
The page linked to buy the product say 10 pieces in stock, and 'not recomended for new designs'.
Following the link in that page to manufacturer and then to 'microcontroller units' shows 14 products, all 'not recomended for new designs', except for the ones with zero stock.
No doubt Apple will surf the AI wave, and all of the above are powerfull advantages.
A compelling history to be the chosen way to access AI services will need to offer good sandboxing, secure gatekeeping of credentials, a modern adaptive firewall to control agents communications, skills to access OS services and core applications, and a core agent that can handle all of the previous concerns.
This will be a massive effort. The good news for Apple is that it will not have competition: these needs OS integration, and a comprehensive design.
reply