I don't suppose you have (or would be interested in writing) a blog post about how you set that up? Or maybe a list of links/resources/prompts you used to learn how to get there?
I recently tried to figure out what their offerings currently are. I'm hoping for `efficent but performant AI compute-chips` by Apple ever since they kicked out Nvidia in 2015 (for the ML Models / Exploration parts bellow). It will be interesting to see how good their products will feel in this fast-paced environment and how much legroom (RAM + Compute) will be left non-platform offerings.
To my understanding, they market their ML stack as four layers [1]:
- Platform Intelligence: ready-made OS features (e.g., Writing Tools, Genmoji, Image Playground) that apps can adopt with minimal customization.
- ML-powered APIs: higher-level frameworks for common tasks—on-device Foundation Models (LLM), plus Vision, Natural Language, Translation, Sound Analysis, and Speech; with optional customization via Create ML.
- ML Models (Core ML): ship your own models on-device in Core ML format; convert/optimize from PyTorch/TF via coremltools, and run efficiently across CPU/GPU/Neural Engine (optionally paired with Metal/Accelerate for more control).
- Exploration/Training: Metal-backed PyTorch/JAX for experimentation, plus Apple’s MLX for training/fine-tuning on Apple Silicon using unified memory, with multi-language bindings and models commonly sourced from Hugging Face.
This isn't necessarily a counterargument. Apple's always been conservative with their specs but their tight link between software and hardware has meant they've been able to do more with less. Batteries are a good example of that. Apple has always had a much smaller battery than flagship competitors but has had similar or better battery life than, say, Samsung
It showed up very quickly on my desktop rig.
Linux, Firefox, with a CPU that's over a decade old, a GPU of about half that age, and the cheapest Internet that Spectrum will sell me.
Just a second or three of a weird luminescent throbber, and then "Click here to start". No inexplicable lags at all -- it was all very smooth.
> That is why people are so pissed, there is absolutely zero control over what the large browser manufacturers decide on a whim. It's one thing if banks or Facebook or other truly large entities get to do work... but personal blogs and the likes?
Yep. There are plenty of things on the Internet for which TLS provides zero value. It is absolutely nonsensical to try to force them into using it, but the browser community is hell bent on making that bad decision. It is what it is.
The stereotype, which is sometimes true, is that people do that kind of degree because they want to understand and solve their own issues. Those who are are interested in people as such, can be more drawn to anthropology.
No, the calculation is straightforward and I'm not making the fallacious assumption you say there at the end about a magical lottery ticket number.
My basic point is the probability of collision is lower than the birthday bound, there's no need for this, and as comments in this thread make clear people are not understanding this limitation even exists with the specification.
I was about to say that I never encounter TLS errors while browsing, but that's not strictly true. There is one such website, and it's only because the webmaster had a stroke and can't maintain it currently. But apart from that rather sad story I can't relate to your issues at all.
Yeah, I have to wonder what lead them to these color choices. Not sure why they wouldn't include a white option or any other good neutral colors that actually go with silver and gold. And I think the number of people willing to wear a matte black ring is quite low, especially among women.
Getting yourself an IP address certificate still seems like an idea that's too crazy to work. I'm actually looking forward to seeing all the things breaking by becoming more secure.
I think it has its place, say, summarizing a large legal document under discussion. That said, if part of what someone says involves citing AI, I’d rather they acknowledge AI as their source.
I think making it a “rule” just encourages people to use AI and not acknowledge its use.
The article says it's better than Times New Roman because it's easier to read for those with disabilities - so of course the government needs to make things worse for them. Wonder if someone could sue over these kinds of changes that are being deliberately made to be less accessible.
This is all I can think of and it depresses me how exciting the video is about turning more materials into emissions. I get I have no power over these people building this, but I just wish they didn't make it. I don't want the world to keep building more amazing ways to burn things I or my neighbors will eventually have to breathe in.
"high quality specifications" have _always_ been a thing that matters.
In my mind, it's somewhat orthogonal to code quality.
Waterfall has always been about "high quality specifications" written by people who never see any code, much less write it. Agile make specs and code quality somewhat related, but in at least some ways probably drives lower quality code in the pursuit of meeting sprint deadlines and producing testable artefacts at the expense of thoroughness/correctness/quality.
A good explanation for their maintained prices is the high level of support they still receive from Apple.
Apple gets excoriated here for its backward compatibility, when the company takes very good care of its devices' backward compatibility. In Fall 2025 was the first time that any iPod lost support when macOS lost its Firewire drivers. Any USB iPod still completely works with the current version of macOS.
