lgg

10 ms·

31.
by lgg 3y ago
Spectre, Meltdown and Rowhammer were all discovered in the same timeframe as the things you listed, and were decidedly more complex than dumb one liners. Yes, those are all have a hardware component (and thus the "fixes" are softw
32.
by lgg 4y ago
The situation on classic MacOS was a bit different. The issue in that case was the the 68000 with a 32 bit architecture with a micro-architectural limitation of 24 bit addresses. Nobody thought deeply about the implication of that in terms
33.
by lgg 4y ago
The post's fundamental premise is wrong. LLVM bitcode is not architecture agnostic and never has been. Apple also has used it once, to move from 32 bit to 64 bit on watchOS. That was possible, but only because the armv7k and arm64_32 A
34.
by lgg 4y ago
Agreed, but I don't understand the cost structure at all. Basic Starlink service in the US is $110 a month, and all these quotes are for service fees in Ukraine are on the order of $2500-$4500 a month. I totally get that deploying into
35.
by lgg 4y ago
I don’t dispute that there is a lot fear bound up in the idea of death, but I disagree that accepting that our existence is finite all has to be terrifying. I actually find the idea finality comforting: It gives meaning to my life, and a bo
36.
by lgg 4y ago
Perhaps your conflation was deliberate, but it actually feels like you may not be conflating exactly what you think you are. Let me try to be fairly precise about some things: By standard UNIX function I take it that you mean a function def
37.
by lgg 4y ago
macOS essentially has the same distinction internally (libsystem_kernel.dylib), but that is not directly linkable and is instead re-exported via the libSystem umbrella which also exports libsystem_c.dylib. While you cannot link directly to
38.
by lgg 4y ago
You are confusing API and syscall here. Apple tries incredibly hard to keep APIs (as implemented via libSystem) working, and actually has passed UNIX conformance, so generally speaking these work, are stable, and don't get broken. The
39.
by lgg 4y ago
The macOS syscall interface policy is the same as Windows. In practice it has had less churn then then NTDLL which may make it feel more practical, but it is only more "allowed" in the sense that it is technically feasible, not th
40.
by lgg 4y ago
Because you asked: https://developer.apple.com/library/archive/qa/qa1118/_index... "Apple does not support statically linked binaries on Mac OS X. A statically linked binary assumes binary compatibi
41.
by lgg 4y ago
I think you under estimate just what level expertise and pull modern web engine requires. Google funded a ton of the work to support clang building code for Windows explicitly so they could standardize on clang for Chromium on all platforms
42.
by lgg 4y ago
I am a fan of io_uring style interfaces and think fork() is completely busted, but I agree that intuitively the comparisons seem to obfuscate where a lot of the perf wins come from 1. posix_spawn() performance seems terrible on Linux. There
43.
by lgg 4y ago
Yeah, that is a problem, and it is totally fixable. Checkout `POSIX_SPAWN_CLOEXEC_DEFAULT` on macOS for an example. Again, just because there are API deficiencies doesn't mean that the idea is wrong.
44.
by lgg 4y ago
I think it goes without saying that since I stated fork() is terrible that I am not advocating for spawning new processes via any of the variants of exec() since they all depend on fork(). I directly stated posix_spawn() was the right techn
45.
by lgg 4y ago
fork() is terrible, but embryonic processes also have a lot of performance issues and prevent a number of valuable security mitigations. In general a spawn() style mechanism seems like a better approach (despite the deficiencies of specific
46.
by lgg 4y ago
13.0 is not just a marketing number. It is the number stamped in the binaries produced with the Ventura SDK. It is the number in Ventura SystemVersion.plist. It is number used in the availability markup in the headers provided by the Ventur
47.
by lgg 4y ago
800, but it only worked if you were at 100% health.
48.
by lgg 4y ago
Not sure if it worth the platform specific code, but for #2 macOS 10.15+ has `posix_spawn_file_actions_addfchdir_np()`. I think most of these are deficiencies in the available posix_spawn actions, not anything inherent. Of course getting al
49.
by lgg 4y ago
I did partner acrobatics (hobbyist level), and could do handstands in the middle of the room for ~20-40 seconds fairly consistently (and on a good day much more than that). Handstands are actually one of the safer things you can do, especia
50.
by lgg 5y ago
It does because calling that function adds a new control flow edge out of the block it is in, which means you can no longer prove certain cleanup code can safely be elided. Additionally the fact that C++ does not annotate whether a function
51.
by lgg 5y ago
Yes. They are all reasonable ideas, and we actually have experience with most (all?) of them: * Distributing IR applications: We do a form of this by supporting bitcode for App Store submissions on iOS, tvOS, and watchOS. For watchOS it was
52.
by lgg 5y ago
Every time I read one of these essays extolling the virtues of static linking it makes me pretty sad. Engineering is about trade offs, and sometimes it does make sense to statically link, but the fact that those trade offs are so lopsided o
53.
by lgg 5y ago
It is good article, but I wish it discussed the differences in dynamic symbol resolution, which is often a source of subtle compatibility issues when porting between POSIX OSes. Linux uses a flat namespace for linking, where each bind lists
54.
by lgg 6y ago
No. UPX won't work on iOS for various reasons, but it is also generally speaking a poor choice to use on macOS. There are several issues here: * It usually does not reduce the size of the file in transit, as most files are compressed f
55.
by lgg 6y ago
Right before the pandemic started I went to an allergist and was considering getting shots, but obviously the last year has put many things on hold. Avoiding weekly doctor's office visits (and all those shots) is appealing. Would I nee
56.
by lgg 6y ago
Personally I think not dying of a deadly disease is a pretty good carrot, as is the fact that we get to eventually stop wearing masks, but I accept those are sort of abstract rewards. Unfortunately the what you are suggesting just isn'
57.
by lgg 6y ago
You are correct, I am just making an assertion, but I don't have to prove it, I will be satisfied to wait and watch things play out. There is a lot of money and a many industry players working on RISC-V, so eventually the market should
58.
by lgg 6y ago
In my opinion those complaints are generally correct. I work on low level OS and toolchain components (static and dynamic linkers) and interact with CPU architects. When I looked at RISC V's addressing modes I was dumbstruck, they are
59.
by lgg 6y ago
I also had an MkLinux machine I used as semi-production machine from ~96-99. I was able to get a Cable Modem in early '96. Back then ISPs only supported single machines directly connected to the modem, so I found an old Power 6100&#x2F
60.
by lgg 6y ago
That is true, but I am pretty sure this is misattributed. At the time we had two major issues which slowed down loading these sorts of dylibs. One was attaching the code signatures (which gets attributed to the dynamic linker because it is

More ›