826 karma · joined May 6, 2020
He basically invented triple cooked fries at the fat duck (precooked at 70° celsius then fried twice, with airing/freezing steps in between), and it's a pretty close approximation of them done much simpler.
In terms of recipes, some have mentioned it but it's barely practical, even if you like spending hours reproducing recipes from Michelin stars restaurant books. There are a few gems, like the truffle Arzak eggs done sous vide, but most of the time you don't find much. You'll have more fun with an El Bulli book if that's what you're looking for.
The at home version is a lot more practical but is also a bit dated at this point imo. The mac and cheese with sodium citrate is a good example of what to expect.
If we put aside Myhrvold (...), there's a lot of extremely talented chefs that worked on it (Chris Young worked at The Fat Duck during it's peak popularity). Some of them started a site called chefsteps a while back which tried to get a bit more practical yet still have some nice stuff. They do have a pretty useful chart (https://www.chefsteps.com/activities/a-map-of-sous-vide-cook...) that serves as a good reminder if you do sous vide regularly but never quite remember the temps. Their macaron course is also particularly on point.
The site has been bought by Breville (I think ?) and it's not super clear at this point how much they will still push content but it's still a cool ressource if you like that kind of cooking.
Basically Apple made a new "safe" API for screensavers (via .appex) but is only using it internally. 3rd party screensavers must still use the old unsafe API (that uses plugins, so unsafe code).
To bridge that gap, Apple made legacyScreenSaver, an .appex that loads the plugin code. It's a great concept in practice, but the implementation has been a mess since macOS 10.15 (Catalina...), breaking many things (multi monitor support was a big one, broken in many different ways over the years). Some Apple built in screensavers haven't been ported to the new API, so you may still have issues with legacyScreenSaver without that.
With macOS 14, Apple broke it again and indeed, legacyScreenSaver no longer tells the third party screensaver to quit! My rough guess is that this is linked to the way they implemented the transition with the new built in aerial videos they added that "slows" down on your desktop (on practice, it's not the screensaver that becomes the desktop, but 2 separate process/video players that gets synced up!).
Anyway, it's been a mess for third party developers for a while (I make one called Aerial). Our best workaround is to listen for a macOS event that tells us the screensaver will exit, and time our way to forcing an exit (literally, we call exit() which we shouldn't do, but that's the only workaround that works-ish). It works maybe 99% of the time. But sometimes legacyScreenSaver still craps out on its own.
Killing it manually will fix things (you will get a black screen + some CPU usage until you do, that can get bad depending on the screensaver) too.
I (and others) reported that bug multiple times but it's been 1 year+ and nothing. It's a mess.
The Académie tried to codify what was used at the time (which varied a lot) to try and create a standard, but that's why there's so many exceptions to the rules everywhere : they went with "tradition" when creating the system instead of logical rules or purer phonetical approach (which some proposed).
There's a bunch of info on the wikipedia link about it, and how each wave or "réforme" tries to make it simpler (while still keeping the old version around as correct).
Each one is always hotly debated/rejected by parents too when they see their kids learning the newly simplified rules.
Recently, the spelling of onion in french went from "Oignon" (old spelling with a silent I) to "Ognon" (simplifying it out), and event that one made me have a "hmm" moment ;)
Back to this precise one, there's no precise rule or pattern underneath, no rhyme or reason, it's just exceptions based on usage and even those can have their own exceptions. Like "idéals/idéaux", I (french) personally never even heard that "idéals" was a thing. Yet it is, somehow : https://www.larousse.fr/dictionnaires/francais/idéal/41391
Usually it's a new user who clones a few repositories to pass whatever mitigation they have.
Always get a "lots of reports, this may take a while" email first though. I don't think I ever not got that one.
I think there's something to be said about sending - by default - user generated content by email automatically if you've replied once to a thread. Lots of bad defaults here imho.
The railway system series is also great, you'll see the step by step construction of the system and later on its use in a GBC event.
I mean, under the hood, it's just windows that are stacked on top of each other at different Z-index.
The wallpaper itself is a window, it sits at the lowest z-index. There's another (transparent) window a few levels above, where your icons sit. Dock/menubar sit on top of those again a few levels above. You can yourself put a window there at pretty much any level.
The screen saver is its own window that's put "on top" of everything else. The XPC I mention starts the player in the desktop window below. Makes sense ?
> I did not realize until you mentioned it that you could have different screensavers on different screens. I guess logically it makes sense given that you can have different wallpaper, but I am kinda surprised they took it that far.
They had too with the way they implemented it, for each screen if you want the "continuity" effect you have to be able to set a different one as both saver/wallpaper.
> I thought all of the videos are available on Mac. I can't think of any that I have seen on my Apple TV that I am not currently seeing as part of this. I am looking in system preferences and I see 61 landscape, 30 cityscape, 21 underwater, and 22 earth
Are you running Sequoia ? I double checked and it now looks like they use the full collection indeed. I'm fairly sure it wasn't the case in Sonoma at the beginning. Maybe they added them in a point update at some point and I missed them. They always had the full manifest of videos, but only a subset was available when they launched the feature, that I'm sure. Some are fairly old and not very sharp, so it made sense to be selective, but Apple does create new versions of the same videos to clean them up fairly frequently.
Behind the scene there's a SQLite database that used to contain only which ones were shown in the UI, while the manifest of videos (which is similar to, but not the one used on tvOS, which has HDR versions encoded with Dolby Vision) is pulled online periodically.
Not really. It may have changed in Sequoia, but afaik in Sonoma this is how it worked :
- ScreenSaver plays the video
- You press a key/unlock your mac
- ScreenSaver does a XPC to the new Wallpaper system with the exact timing/position of where the screensaver was
- Wallpaper system starts a new video player and syncs it exactly
- Your mac wakes up, screensaver is hidden (it's complicated), and the second video player starts playing and slows down
- Eventually it gets replaced by a static screenshot of the last played frame seamlessly
- Screensaver exits (maybe, sometimes)
It's fairly complicated.
> what the performance hit during those few seconds of video playing when unlocking
Minimal, it's all hardware accelerated (videos are 4K/h265).
> is the video just "paused" or is it taking a frame and setting that as the background for better performance
It takes the last decoded frame eventually, but it's not instantaneous.
There are tons of other interesting tidbits about the system, I tried to untangle it because Apple introduced some really annoying bugs in the screensaver system as they changed the way screensavers exits because of the XPC handshake, and it threw a lot of issues in Aerial and other 3rd party screensavers.
Also if you use Spaces or multiple monitors, because you were able to have a different wallpaper on different Spaces/monitors, Apple now lets you set a different screensaver on each. That broke the ability to set a default screensaver which is a pain for 3rd parties.
Note that the "screensaver/wallpapers" videos are 4K/240FPS (likely interpolated frames for many) just to get that smooth slowdown effect. And they backported pretty much the entire catalog of existing Aerials to that format, even if only a few are available in macOS.
I do use these (the whole collection) in Aerial and for a few years I've also had a desktop version if you want to give it a try, it's in the installer. By default I use the 240FPS videos nowadays, and the desktop tool (Aerial Companion) will play those back at slow speed too by default (there are playback controls) : https://aerialscreensaver.github.io
It is, I tried to raise it up on Steam support forum, hopefully they'll address this. Especially since they showed the game a few times running on M1+ macs, I definitely was surprised.
> Performance on my M2 Max is pretty poor
On my M1 Ultra I found reducing to the "Low" preset worked great and lets me play at 60 FPS/5K resolution. It still looks fine. Just avoid Minimal which is visually jarring (no shaders and extreme contrasts/bad readability).
And it's definitely great! I just hope they get a universal build soon, as if you are on Apple Silicon (M1+), the game runs under Rosetta. There's a bit of a performance hit because of this, although you can still run really high resolution (5K) on low fairly effortlessly! And it looks absolutely beautiful.
Side note, I was a tiny bit confused about the "tutorial" when you get the two checkboxes, one of them saying something like "Don't destroy buildings".
I thought it meant you should reuse your structures and not destroy them, which after a few milestones is just not possible at all.
- In General > Language and region : Both Language to English US AND region to US - In Apple Intelligence : Set siri language to English US.
Then you need to reboot your mac. You'll have to apply to a waiting list, in Settings > Apple Intelligence. In my case it only took a few minutes.
Same procedure doesn't work for me on iPad where it says I'm region locked. Even with a VPN. As far as I remember, Apple introduced a pretty efficient daemon in iOS/iPadOS to detect region (for Europe's App Store easing of restrictions) and it's likely what's blocking there.
I'll refrain from too many early comments, but it seems fairly limited.
Asking a question about macOS (How to change DNS) will trigger a AI response that quotes the macOS user guide, while asking the same question about iOS will default to a basic Google Search. Haven't seen any fallback to ChatGPT, that may not be part of that beta.
Mail summarizing looks OK, but fails on some very long emails. When it works, the summary is fairly short (about 3 sentences max) which is probably pretty adequate.
Closest thing I noticed is that apps that have a "splash screen" of some sort (could be an update check, etc) will always fail to go where they are supposed to. This includes Discord and Xcode very reliably. Sometimes point releases make things worse.
Also, I think there's quite probably some firmware/hardware issues with screen detection on the M1. I do have a USB-C Studio Display which works mostly fine, but I also have a (I admit very odd and not quite new) Asus 4K display that uses Multistream Displayport. Connected via a USB-C to DP cable (protocol wise, it's supposed to be the best case scenario as VESA joined up to USB-C).
On my M1 Mac Studio (and something I can't reproduce with other hardware), that display will regularly not wake up from sleep and plugging/unplugging to another port will work maybe half the time.
Most puzzling also, if my Mac goes to sleep, periodically the Asus display will wake up for a few seconds (just going back to standby with backlight on), then go back to sleep. I never timed it but it's at least once an hour, and always does so.
I also had a few bug reports of people having issues with various USB-C docks where my screen saver (Aerial) just gets told the screen isn't there anymore and to go away, and people then see a blank screen on that one, and it never comes up again with the screen not on standby, but just displaying black with background on.
Considering it's been happening since I got the M1 and not on previous Macs (and most reports were on M1 I believe), I have a feeling there may be a few firmware/hardware USB-C issues laying around. Maybe it's been fixed since ?
At that point I can't quite remember if PPP Connect required MultiTOS/MinT/MagiC or not ? I think maybe only one of the stack did. I definitely remember CAB was the good/last browser option but it wasn't the first. Can't remember the name of the first one, or the email client though.
It was also my first Linux computer, somehow, which I installed on a iomega Zip (SCSI ?) drive. I think it took 15 minutes to launch X11 and at that point the whole thing was excruciatingly unusable.
Also first computer I overclocked, a french company called Centek had made a tiny board that reclocked the 68030 from 16 to 25 MHz. I looked it up and found their website here : http://centek.free.fr/atari/ct2/ct2_hist.htm
Looks like the version I have (probably Centurbo 1 rev2 ?) overclocked both the CPU an the bus (which may or may not impacted the RAM ? Hard to remember). They made a few iterations, going up to 50 MHz.
Many extremely fond memories of that machine in any case. But at that point the PC market was opening up and there was no going back.
Because of how the new system work, I wouldn't be surprised the bug is limited to those solid color backgrounds (which are handled quite differently for historic reasons, and it could very well be why you get the error).
The new wallpaper system is a bit of a mess, and solid colors have always been treated weirdly in their preferences.
Also, I hate to do this but if I'm allowed, tinniest plug, I do maintain a screensaver project for macOS that does video both screensaver and wallpaper integration with solar time adaptation : https://aerialscreensaver.github.io (the default download will give you the app that does the wallpaper integration).
I do find the contrast slightly low between active and inactive tabs on macOS in dark mode, using the "original" profile, but I'm sure this is easy to tweak.
For all its faults, Safari in compact mode/dark mode does get the active/inactive tabs contrast right, although it's obviously fairly subjective.
To give a bit of context, Bordier is considered very high-end/premium butter that you find mostly at cheesemongers (the large ones you see in the video, they get cut on demand) and Michelin star restaurants (the small cones for example). It's not particularly cheap, but unless you have a local small farm around (doing it the old way, which is probably not much of a thing), it's about as good as butter can get.
I stumbled upon that video a few days ago and was a bit surprised that even their "standardised" products (the "plaquettes", aka the rectangles you'll see around the end with striations on them) were still shaped manually.
Yet if it's a decent/good idea, my go to answer is "not yet" and not "no". If it's really a great idea, eventually I'll get to it. By keeping the issue around open, it's still peripherally in my vision and I may have a plan to take care of it that depends on something else. Extra information is never wasted and may inform your decisions on what you are working on now. Plus you know, it's kind of the polite thing to do.
I feel it's the same for the original Steve quote, Apple was/is pretty famous for saying "no" to a good idea and revisiting them later. I think "not yet" is closer to the originally meant intent.
With the various security changes in "recent" macOS, you can't modify your bundle and download files inside it, as it would change its signature and break the notarisation system.
As a developer the best you can usually do is put some instructions somewhere (website, somewhere in a menu in UI), or do a package install that puts an uninstaller somewhere (more of the Windows way, but it breaks many expectations from users like having your app be one icon in `Applications`, and not it's own folder with your app and maybe a "Uninstall" app there too). For Aerial I give uninstall instructions on the website, but there's not much of a standard on how to handle this (that I know of, at least).
- Feb 22, arm announced to Qualcomm that Nuvia's ALA/TLA licenses would be terminated in March 1st 22 (for the reasons from parent post)
- On April 1st, arm counsel acknowledged the termination of the licenses and that Nuvia was in compliance (aka destroyed the designs under the license they had obtained, which is in the ALA contract)
- On multiple occasions afterwards Qualcomm asked arm to validate "new core designs" to be used on upcoming products (!)
- Qualcomm PR/CEO kept talking about upcoming product based on Nuvia's work, while the license was effectively revoked, and was planning to sample such chips
It will be interesting to see Qualcomm's counterclaims, but arm's factual presentation seems pretty clear and doesn't paint Qualcomm under a very flattering light. Arm's complaint all in all looks pretty reasonable (again, we only have one side of the story, but there's some pretty obvious bad faith from Qualcomm here).
> Because Qualcomm attempted to transfer Nuvia licenses without Arm’s consent, which is a standard restriction under Arm’s license agreements, Nuvia’s licenses terminated in March 2022. Before and after that date, Arm made multiple good faith efforts to seek a resolution.
If I understand this correctly, arm's licences have an approval process in case of acquisitions for license transfer (which is pretty common), and Qualcomm thought that because they had their own (probably a lot broader) set of arm licenses, they didn't need to seek their approval (or more likely, didn't want to pay some extra transfer cost ?) ?
I can see Qualcomm's argument from a layman's point of view, arm claims that something designed by licensee A can't be transferred to licensee B without their approval, which seems a bit broad of a reach but contracts are weird I guess ? There's no doubt Nuvia's contracts was less favorable to whatever set of licenses Qualcomm operates with arm (relative company sizes and all).
Reuters article goes on about Qualcomm eventually ditching arm's Cortex designs and replacing them by Nuvia's being what this is about. That seems a bit of a stretch, and would be a large pivot in how arm used to operate with its licensees that would send a chilling effect if true.
So I'd be quite surprised if that was the case, considering arm is not under new management. I'm not saying there can't be tensions or bruised execs egos on both sides about this, but this seems a bit of a radical step to suspend Nuvia's license and ask that all their design IP be destroyed.
This is all about semi manufacturing, and the position that TSMC now has in the fab space, thanks to Apple (yes, really, that's what I went on about in the previous comment). No part of my comment referred to arm, architectures, anything of the sort, just that Apple's money, applied broadly at first in the semi manufacturing space, then in a very very targeted way, took TSMC from tier 2 manufaturer to the best in class.
If you look back a few years, only x86 chips were having volume at the bleeding edge of manufacturing process. Gpus, Smartphone, everything else was one node back at the very least. Apple threw money and orders with a massive volume (iPhone + iPad is pretty close in units to the x86 cpu market, above 300M roughly off the top of my heard) at TSMC and that early + continous investment helped them fast forward their processes while Intel is still stalled in 2015.
Apple is using TSMC today (the best bits), AMD is using TSMC today (the second best bits) for the performance part of their chiplets and so will Intel tomorrow for the exact same reason. This is the relevant bit that I was pointing at.
But in any case, there's plenty of things to be said about this article. About one year ago (random link with relevant quotes : https://www.pcgamer.com/intels-3d-chip-tech-is-perfect-so-it... ), Intel was mocking AMD for using a chiplet approach, before announcing today that it was - clickbaity title aside - going to change everything.
The sad truth is, both Intel and AMD are in the exact situation. AMD went chiplet in order to make their performance cores at TSMC, and their less critical cores ("IO") at GloFo.
And Intel will be doing the same thing tomorrow (again, random link on the topic: https://www.tomshardware.com/news/intel-ceo-visits-tsmc-agai... ) by producing their performance cores at TSMC and their less critical ones on their own processes.
In both cases, this is just a question of using a very limited resource (TSMC's best in class process) the more effectively that you can (by throwing extra engineering at making a chiplet design that works).
And it's supremely relevant to the discussion to talk about how Apple, by throwing capital at a company (TSMC) that was, for the couple of decades I used to cover this, at best 2 years behind the best in class, today where they are (far far in front).
We could definitely have a long discussion about the hubris that led 2015 Intel where they are today (completely stuck with a 7 year old "+ paint coatings" aging 14nm "performance" process), or how Gelsinger is trying to make the best out of the situation (I personally think he's immensely qualified and Intel's best hope, though that may not be enough to bring Intel back to where it was), but at the end of the day, Apple threw a wrench in what seemed like an unshakable performance lead from Intel by spewing a bit of money left and right (they didn't only bet on TSMC early on, they threw money at GF for example, and it wasn't that massive early on from my understanding), and the silicon world hasn't been the same since.
The complaint is about Apple not allowing 3rd party usage of their NFC chip for other wallets (or anything else for that matter. From my understanding, the access is very limited) :
Quoting :
As a result, users of Apple devices can only pay with the ‘tap and go' function using Apple Pay and not with other wallets. This is because competing wallet developpers need access to the NFC on Apple devices to reach Apple users.
Interestingly they also say that the Digital Market Acts will regulate this :
When it enters into the force, the Digital Markets Act will have a direct effect on digital payments. It will require companies designated as gatekeepers to ensure effective interoperability with hardware and software features they use themselves in their ecosystems. This includes access to NFC for mobile payments.
(IANAL but I find it interesting that they mention specific upcoming regulation tailored to curtail this, while still sending to Apple what they call a Statement of Objection)
My vague (and possibly completely wrong) understanding from the situation here in France is that banks have to individually sign up for this, but on the backend the payment processing is piggybacking on Mastercard/Visa payment network, as from day one, Apple Pay worked on everything (with some caveats) that accepted NFC payment (which most terminals did). Transactions show up on your receipt as (in my case) a "classic" Mastercard transaction.
This doesn't seem to be the way Apple Pay is implemented everywhere though (particularly in the US) ? This may be anecdotal but I had this discussion with a restaurant owner who mentioned that Apple Pay payments from some US customers didn't work (while in my case I've noticed eu/fr variant of Apple Pay worked pretty much everywhere). This could be some random other issue though.
It would be interesting to know if in other EU countries this is always the same, piggybacking on your bank/card network.
While I broadly understand the idea of opening up the NFC to 3rd party wallets, it's unclear to me how much of a practical idea that would be. As someone who uses Apple Pay daily, I don't see how having to open a 3rd party wallet app would be comparatively effective, it's all about the convenience of being able to triggering it instantly.
A better solution would be mandating/allowing those 3rd party wallets not only NFC integration but having their payment options showing up in Apple's Wallet so they can be triggered the same way (double tap on your iPhone/Apple Watch, which already lets you pick between various Apple Pay cards/QR codes you may have entered).
The renaming part btw was quite awful of them, they had a hard time acknowledging that they went back to Cortex based cores and I remember their press release trying to imply they didn't.
They were quite hammering the fact they had a custom arch pre v8, and the turnaround was difficult for them to admit.