Live data from Hacker News

Apple announces Foundation Models and Containerization frameworks, etc

apple.com

421–430 of 514 posts

Re: Apple announces Foundation Models and Containerization frameworks, etc

#421

Okay, the AI stuff is cool, but that "Containerization framework" mention is kinda huge, right? I mean, native Linux container support on Mac could be a game-changer for my whole workflow, maybe even making Docker less of a headache.

FWIW, here are the repos for the CLI tool [1] and backend [2]. Looks like it is indeed VM-based container support (as opposed to WSLv1-style syscall translation or whatever): Containerization provides APIs to: [...] - Create an optimized Linux kernel for fast boot times. - Spawn lightweight virtual machines. - Manage the runtime environment of virtual machines. [1] https://github.com/apple/container [2] https://githu…

I just noticed the addition of container cask when I ran b”brew update”.

I chased the package’s source and indeed it’s pointing to this repo.

You can install and use it now on the latest macOS (not 26). I just ran “container run nginx” and it worked alright it seems. Haven’t looked deeper yet.

Re: Apple announces Foundation Models and Containerization frameworks, etc

#422

Earlier quoted context omitted.

> Is there a VM technology that can make Linux aware that it's running in a VM, and be able to hand back the memory it uses to the host OS? Isn't this an issue of the hypervisor? The guest OS is just told it has X amount of memory available, whether this memory exists or not (hence why you can overallocate memory for VMs), whether the hypervisor will allocate the entire amount or just what the guest OS is actually us…

> 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.

Re: Apple announces Foundation Models and Containerization frameworks, etc

#423

Earlier quoted context omitted.

But the opposite of "flat" is not "transparent". This was posted in another HN thread about Liquid Glass: https://imgur.com/a/6ZTCStC . I'm sure Apple will tweak the opacity before it goes live, but this looks horribly insane to me.

Agreed, people have said perhaps its Apple's way of bringing VR vibes to the UI, showing layers of UI elements. But I'm not so sure if I want transparent.

I'll just want the option to turn it off because it will use extra CPU cycles just existing.

I remember the catastrophe of Windows Vista, and how you needed a capable GPU to handle the glass effect. Otherwise, one of your (Maybe two) CPU cores would have to process all that overhead.

Re: Apple announces Foundation Models and Containerization frameworks, etc

#424

Earlier quoted context omitted.

FWIW, here are the repos for the CLI tool [1] and backend [2]. Looks like it is indeed VM-based container support (as opposed to WSLv1-style syscall translation or whatever): Containerization provides APIs to: [...] - Create an optimized Linux kernel for fast boot times. - Spawn lightweight virtual machines. - Manage the runtime environment of virtual machines. [1] https://github.com/apple/container [2] https://githu…

I just noticed the addition of container cask when I ran b”brew update”. I chased the package’s source and indeed it’s pointing to this repo. You can install and use it now on the latest macOS (not 26). I just ran “container run nginx” and it worked alright it seems. Haven’t looked deeper yet.

There’s some problem with networking: if you try to run multiple containers, they won’t see each other. Could probably be solved by running a local VPN or something.

Re: Apple announces Foundation Models and Containerization frameworks, etc

#425

> New Design with Liquid Glass Looks like software UI design – just like fashion, film, architecture and many other fields I'm sure – has now officially entered the "nothing new under the sun" / "let's recycle ideas from xx years ago" stage. https://en.wikipedia.org/wiki/Aqua_%28user_interface%29 To be clear, this is just an observation, not a judgment of that change or the quality of the design by itself. I was gett…

I used to find these changes compelling but now I think they are mostly a pain in the ass or questionable. Proof of a well-designed UI is stability, not change. Reads to me strongly of an effort to give traditional media something shiny to put above the headline and keep the marketing engine running.

If you read the press release, you can see it's 100% about marketing and nothing else.

Apple will spend 10x the effort to tell you way a useless feature is necessary before they look at user feedback.

Re: Apple announces Foundation Models and Containerization frameworks, etc

#426

Earlier quoted context omitted.

I'm kinda ignorant about the current state of Linux VMs, but my biggest gripe with VMs is that OS kernels kind of assume they have access to all the RAM the hardware has - unlike the reserve/commit scheme processes use for memory. Is there a VM technology that can make Linux aware that it's running in a VM, and be able to hand back the memory it uses to the host OS? Or maybe could Apple patch the kernel to do exactly…

It’s one reason i don’t like WSL2. When you compile something which needs 30 GB RAM the only thing you can do is terminate the wsl2 vm to get that ram back.

Since late 2023, WSL2 has supported "autoMemoryReclaim", nominally still experimental, but works fine for me.

add:

[experimental] autoMemoryReclaim=gradual

to your .wslconfig

See: https://learn.microsoft.com/en-us/windows/wsl/wsl-config

Re: Apple announces Foundation Models and Containerization frameworks, etc

#427
post #69

Some 15 years ago, A friend of mine said to me "mark my words, Apple will eventually merge OSX with iOS on the iPad". And with every passing keynote since then, it seemed Apple's been inching towards that prophecy, and today, the iPad has become practically a MacBook Air with a touch screen. Unless you were a video editor, programmer who needs resources to compile or a 3D artist, I don't see how you'd need anything o…

The fact that they haven't done it in 15 years should be an indication that they don't intend to do it at all. Remember that in the same time period Apple rebuilt every Macbook from scratch from the chipset up. Neither the hardware nor software is a barrier to them merging the two platforms. It's that the ecosystems are fundamentally incompatible. A true "professional" device needs to offer the user full control, and…

They don’t want to overtake their desktop device market. If the UI fully converges, then all you have a iPad with a keyboard across all devices (laptops, desktop).

Re: Apple announces Foundation Models and Containerization frameworks, etc

#429
post #417

Earlier quoted context omitted.

I guess I'd say "mu", from a dev perspective, you shouldn't care about tokens ever - if your inference framework isn't abstracting that for you, your first task would be to patch it to do so. To parent, yes this is for local models, so insomuch worrying about token implies financial cost, yes

Ish - it always depends how deep in the weeds you need to get. Tokenisation impacts performance, both speed and results, so details can be important.

I maintain a llama.cpp wrapper, on everything from web to Android and cannot quite wrap my mind around if you'd have any more info by getting individual token IDs from the API, beyond what you'd get from wall clock time and checking their vocab.
Post reply on HN