From https://512pixels.net/2013/07/power-mac-g4/: the ad was based on the fact that Apple was forbidden to export the G4 to many countries due to its “supercomputer” classification by the US government.
Yes, Apple will take down apps that are blatant redistribution without license of open-source software. Years ago I made a simple utility app and put the code on GitHub, someone took the code, changed the name, and uploaded it on the App Store with a 8$ price. It was taken down after I contacted Apple.
Because HandBrake uses some parts of the FFmpeg libraries, but HandBrake scope is much smaller than FFmpeg, and while it uses some parts, it's definitely not FFmpeg CLI GUI.
The "Messages in iCloud" sync is end to end, so you can enable it and disable iCloud backup, or manually backup on your computer: https://support.apple.com/en-us/102651
Right, Blender Cycles for example can run on Metal, but neither on OpenGL or Vulkan.
So while it's nice to have a working OpenGL, it depends if your workflow requires OpenGL apps.
It's been a gradual process, looks at the Music app, how it has continuously got worse and buggier over the year, even without Swift and SwiftUI.
You can't blame SwiftUI for that.
The issue has got nothing to do with programming languages or UI toolkits, it's just that before there were more people with more attention to details, or now the management is so broken that there is no QA and no time to fix things.
The content of almost every messaging app push notification is already encrypted. So I think it's mainly for knowing when someone receives a notification.
The object oriented part of Objective-C was never meant for high performance code. Apple documentation always recommended using C when performances are an issue, which can be easily done because Objective-C is in fact C plus a bunch of object oriented concepts.
However, in the end if you want every bit of performance you have to use SIMD intrinsics or write asm directly, so even C can be 8x times or more slower than a manually optimized code.
All filters are capable of high depth since 1.6. I would say that AAC encoder quality is not too bad now (on macOS it can use Apple's AAC encoder, so it's not an issue there).
Anyway, the main issue is the lack of man power, so many requested features that would be nice to have are stuck in features paradise. I guess that's the same as every Open Source project.
HandBrake requires a patched version of libavcodec/libavformat libraries. Some Linux distributions like to link it to their system libavcodec/libavformat versions, and this breaks many things, DVD subtitles too.
However, if you are using a version that's linked with the right libraries, it's probably a bug that should be reported.
HandBrake uses some parts of FFmpeg libraries: libavformat, libavcodec, and libavfilter. But even so, it's an entire different app, the decoders, some demuxers and some filters are the same, but the way they are connected together is entirely different than FFmpeg cli app.
That was mainly marketing. 10.6 had so many new features and extensive under the hood changes, for example it introduce Grand Central Dispatch, QuickTime X, OpenCL, completely rewritten Finder (Finder was a Carbon app, it was rewritten in Cocoa), 64bit kernel, App Store, app sandbox, etc…
SVT-AV1 has still a lot of visual quality issues. PSNR, SSIM, VMAF are useful metrics, but optimising for these won't get you the best encoder.
x264 didn't get its reputation for going after PSNR and SSIM.
We spent the last 15 years avoiding the menu bar in mobile devices, and in the end we reinvented it in the worst way. Hidden under either the hamburger button on Android, the "…" or whatever other button on iOS.
Swift string type has got many different views, like UTF-8, UTF-16, Unicode Scalar, etc… so if you want to count the bytes or cut over a specific byte you still can.