By the way (hello, adobe).
DNG compression compresses worse than 7zip, haha.
Too much for an open standard, too hard to add LZ4 as an option in the times of having 24 core setups :D
"Sony’s software for processing ARW RAW files is called Imaging Edge. Like most first-party software from camera manufacturers, it’s terrible and unintuitive to use — and should be saved for situations like a high-resolution multishot mode where it’s the only method to use a camera’s proprietary feature."
I think the primarily reason is that they have great hardware developers and terrible software developers. So, having ARWs it is maximum they could provide to photographer, so they could take the files and run away from sony as soon as possible (i.e. do the rest in the better software).
Pentax could save DNGs, there are zero reasons for other companies not to do the same.
It is always written into a memory buffer first, which could be like 256 megabytes... it tooks time to fill it up, once it is filled, memory card speed becomes a bottleneck. So, actually, writing only jpegs would trigger the slowdown later, so you could take more frames before the buffer fills up
Most popular dependency management systems literally linking to a git sha commit (tag), see locks file that npm/rebar/other tool gives you. Just in a recursive way.
They do way more than that. For example they won't allow you to have Foo-1 that depends on Qux-1 and Bar-1 that depends on Qux-2 where Qux-1 and Qux-2 are incompatible and can't be mixed within the same static library or assembly. But may allow it if mixing static-private Qux inside dynamic Foo and Bar and the dependency manager is aware of that.
A native submodule approach would fail at link time or runtime due to attempt to mix incompatible files in the same build run. Or, in some build systems, simply due to duplicate symbols.
That "just in a recursive way" addition hides a lot of important design decisions that separate having dependency manager vs. not having any.
They do way less then that. They just form a final list of locks and download that at the build time. Of course you have to also "recursively" go though all your dep tree and add submodules for each of subdependencies (recommend to add them in the main repo). Then you will have do waste infinite amount of time setting include dirs or something. If you have two libs that require a specific version of a shared lib, no dep manager would help you. Using submodules is questionable practice though. Useful for simple stuff, like 10 deps in total in the final project.
Natural language is pretty good for describing the technical requirements for the complex system, though. I.e. not the current code implementation, but why the current code implementation is selected vs other possible implementations. Not what code do, but what it is expected to do. Basically, most of the missing parts, that live in Jira-s, instead of your repo. It is also good, at allowing better refactoring capabilities, when all your system is described by outside rules, which could be enforced on the whole codebase. We just use programming languages, because it is easier to use in automated/computer context (and was the only way to use, to be honest, before all the LLM stuff). Though, while it gives us non-ambiguity on the local scale, it stops working on the global scale, the first moment person went and copy-pasted part of the code. Are you sure that part follows all the high-level restrictions we should to follow and is correct program? It is program that would run, when compile, but definition of run is pretty loose. In C++ program that corrupts all the memory is also runnable.
Apple has its own trackers and ad services. But it treats itself specially. While other apps need to ask. Maybe I don't want some apps from apple to have the same permissions, as other apps from apple. It is basically bundling. I agreed for one app from apple to share data, not for all apps from apple. Oh, and don't let me start about wording they use on these pop-ups... Like when I download some app from the internet, which is signed, notarized and so on, it still asks: oh, you downloaded this app from the internet (surprise!)... Instead of: "ok, you downloaded from internet, it has sign, notarification, developer is already delivering software for 10 years and have 20 million users, so looks safe to run...". Basically, fear inducing messages instead of actually useful from security sense.
Would not fly.
Developers would not go into the store. Because everyone knows, that 30% tax would be next (basically it is the current situation on the Mac, apple could pull the switch on gatekeeper any time). And, because a lot of modern apps are just electron wrappers, people would just move to the web versions for everything. Which means killing their own platform.
