Live data from Hacker News

Apple announces Foundation Models and Containerization frameworks, etc

apple.com

451–460 of 514 posts

Re: Apple announces Foundation Models and Containerization frameworks, etc

#451
post #444

I'm still a little dissapointed. It seems those models are only available for iPhone series 16 and iPhone 15 pro. According to mixpanel that's only 25% of all iOS devices and even less if taking into account iPadOS. You will still have to use some other online model if you want to cover all iOS 26 users because I doubt apple will approve your app if it will only work on those Apple Intelligence devices. Why should I…

Uptake of iPhone 16+ devices will be much more than 25% by the time someone develops the next killer app using these tools, which will no doubt spur sales anyway.

Re: Apple announces Foundation Models and Containerization frameworks, etc

#452
post #137

I hoped for a moment that "Containerization Framework" meant that macOS itself would be getting containers. Running Linux containers and VMs on macOS via virtualization is already pretty easy and has many good options. If you're willing to use proprietary applications to do this, OrbStack is the slickest, but Lima/Colima is fine, and Podman Desktop and Rancher Desktop work well, too. The thing macOS really painfully…

Hard same. I wonder if this does anything different to the existing projects that would mean one could use the WSL2 approach where containerd is running in the Linux micro-VM. A key component is the RPC framework - seems to be how orbstack's `macctl` command does it. I see mention of GRPC, sandboxes and containers in the binfmt_misc handling code, which is promising:

https://github.com/apple/containerization/blob/d1a8fae1aff6f...

Re: Apple announces Foundation Models and Containerization frameworks, etc

#453

Earlier quoted context omitted.

> or just what the guest OS is actually using should depend on the hypervisor itself. How can the hypervisor know which memory the guest OS is actually using? It might have used some memory in the past and now no longer needs it, but from the POV of the hypervisor it might as well be used. This is a communication problem between hypervisor and guest OS, because the hypervisor manages the physical memory but only the…

A generic vmm can not, but these are specific vmms so they can likely load dedicated kernel mode drivers into the well known guest to get the information back out.

The driver would still be part of the guest.

Re: Apple announces Foundation Models and Containerization frameworks, etc

#454
post #434
post #394

Earlier quoted context omitted.

I might we wrong but I guess this will only works on iphone 16 devices and iphone 15 pro - thus drastically limits your user base and you would still have to use online API for most apps. I was hoping they provide free ai api on their private cloud for other devices even if also running small models

If you start writing an app now, by the time it's polished enough to release it, the iPhone 16 will already be a year old phone, and there will be plenty potential customers. If your app is worthwhile, and gets popular in a few years, by that time iPhone 16 will be an old phone and a reasonable minimum target. Skate to where the puck is going...

Developers could be adding a feature utilizing LLMs to their existing app that already has a large user base. This could be a matter of a few weeks from an idea ti shipping the feature. While competitors use API calls to just "get things done", you are trying to figure out how to serve both iPhone 16 and older users, and potentially Android/web users if your product is also available elsewhere. I don't see how an iPhone 16 only feature helps anyone's product development, especially when the quality still remains to be seen.

Re: Apple announces Foundation Models and Containerization frameworks, etc

#455
post #444

I'm still a little dissapointed. It seems those models are only available for iPhone series 16 and iPhone 15 pro. According to mixpanel that's only 25% of all iOS devices and even less if taking into account iPadOS. You will still have to use some other online model if you want to cover all iOS 26 users because I doubt apple will approve your app if it will only work on those Apple Intelligence devices. Why should I…

Uptake of iPhone 16+ devices will be much more than 25% by the time someone develops the next killer app using these tools, which will no doubt spur sales anyway.

App development could be as quickly as a few weeks. If the only "killer apps" we have seen in the past three years are the ChatGPT kind, I'm not holding my breath for a brand new "killer app" that runs only on iPhone 16+.

Re: Apple announces Foundation Models and Containerization frameworks, etc

#456
post #41

iPad update is going to encourage a new series of folks trying to use iPads for general programming. I'm curious how it goes this time around. I'm cautiously optimistic

No vscode, no deal. I don't see that happening any time soon.

Re: Apple announces Foundation Models and Containerization frameworks, etc

#457
post #94
post #43

Earlier quoted context omitted.

Multi-user iPadOS when?

When they figure out how to make it not dent sales of individual devices. If you and your spouse could easily share one around the house for different purposes but still having each of your personal apps and settings, you might not buy two!

I think this may be overestimating how often people buy tablets. My wife has an iPad Air 1 or 2, so it's close to 10 years old and mostly sits in a drawer. I had a VERY old iPad 2 that I held off on replacing because I wanted to wait for a multi-user iPad.

I finally gave up and bought a Mini6 a year or two ago, which gets.... also minimal use. And I'm sure not buying ANOTHER tablet we're not going to use.

If they were multi-user I actually think we'd both get more value out of it, and upgrade our one device more often.

Re: Apple announces Foundation Models and Containerization frameworks, etc

#458
post #238

There's a different thread if you want to wax about Fluid Glass etc [1], but there's some really interesting new improvements here for Apple Developers in Xcode 26. The new foundation frameworks around generative language model stuff looks very swift-y and nice for Apple developers. And it's local and on device. In the Platforms State of the Union they showed some really interesting sample apps using it to generate d…

The direction the software engineering is going in with this whole "vibe coding" thing is so depressing to me.

I went into this industry because I grew up fascinated by computers. When I learned how to code, it was about learning how to control these incredible machines. The joy of figuring something out by experimenting is quickly being replaced by just slamming it into some "generative" tool.

I have no idea where things go from here but hopefully there will still be a world where the craft of hand writing code is still valued. I for one will resist the "vibe coding" train for as long as I possibly can.

Re: Apple announces Foundation Models and Containerization frameworks, etc

#459
post #238

There's a different thread if you want to wax about Fluid Glass etc [1], but there's some really interesting new improvements here for Apple Developers in Xcode 26. The new foundation frameworks around generative language model stuff looks very swift-y and nice for Apple developers. And it's local and on device. In the Platforms State of the Union they showed some really interesting sample apps using it to generate d…

The direction the software engineering is going in with this whole "vibe coding" thing is so depressing to me. I went into this industry because I grew up fascinated by computers. When I learned how to code, it was about learning how to control these incredible machines. The joy of figuring something out by experimenting is quickly being replaced by just slamming it into some "generative" tool. I have no idea where t…

This sounds like a boomer trying to resist using Google in favor of encyclopedias.

Vibe coding can be whatever you want to make of it. If you want to be prescriptive about your instructions and use it as a glorified autocomplete, then do it. You can also go at it from a high-level point of view. Either way, you still need to code review the AI code as if it was a PR.

Re: Apple announces Foundation Models and Containerization frameworks, etc

#460
post #238

There's a different thread if you want to wax about Fluid Glass etc [1], but there's some really interesting new improvements here for Apple Developers in Xcode 26. The new foundation frameworks around generative language model stuff looks very swift-y and nice for Apple developers. And it's local and on device. In the Platforms State of the Union they showed some really interesting sample apps using it to generate d…

The direction the software engineering is going in with this whole "vibe coding" thing is so depressing to me. I went into this industry because I grew up fascinated by computers. When I learned how to code, it was about learning how to control these incredible machines. The joy of figuring something out by experimenting is quickly being replaced by just slamming it into some "generative" tool. I have no idea where t…

To be meta about it, I would argue that thinking "generatively" is a craft in and of itself. You are setting the conditions for work to grow rather than having top-down control over the entire problem space.

Where it gets interesting is being pushed into directions that you wouldn't have considered anyway rather than expediting the work you would have already done.

I can't speak for engineers, but that's how we've been positioning it in our org. It's worth noting that we're finding GenAI less practical in design-land for pushing code or prototyping, but insanely helpful helping with research and discovery work.

We've been experimenting with more esoteric prompts to really challenge the models and ourselves.

Here's a tangible example: Imagine you have an enormous dataset of user-research, both qual and quant, and you have a few ideas of how to synthesize the overall narrative, but are still hitting a wall.

You can use a prompt like this to really get the team thinking:

"What empty spaces or absences are crucial here? Amplify these voids until they become the primary focus, not the surrounding substance. Describe how centering nothingness might transform your understanding of everything else. What does the emptiness tell you?"

or

"Buildings reveal their true nature when sliced open. That perfect line that exposes all layers at once - from foundation to roof, from public to private, from structure to skin.

What stories hide between your floors? Cut through your challenge vertically, ruthlessly. Watch how each layer speaks to the others. Notice the hidden chambers, the unexpected connections, the places where different systems touch.

What would a clean slice through your problem expose?"

LLM's have completely changed our approach to research and, I would argue, reinvigorated an alternate craftsmanship to the ways in which we study our products and learn from our users.

Of course the onus is on us to pick apart the responses for any interesting directions that are contextually relevant to the problem we're attempting to solve, but we are still in control of the work.

Happy to write more about this if folks are interested.

Post reply on HN