I came in on an H1B as an IC3 at Meta. Now, with the skills I gained during my career, I maintain core infrastructure that has a massive benefit to the industry and is critical to tech companies of all sizes (I learned last week that a major auto manufacturer uses my infrastructure as well). Immigration's benefit to society is tail-distributed, which is why it's important to have broad-based immigration (you can't predict who will be at the tails).
This fallacy gets pointed to constantly, but it's not actually part of most arguments. I.e. it's a strawman. Bad immigration policy can and does negatively affect opportunities and salaries. Immigration in general does not necessarily do so, and an argument to that effect would be an example of the Lump of Labor fallacy, but that is not the argument being made.
My complaint is directed at the Rust Foundation, not the authors, to be clear. Yes, it's free labor, but the Foundation ought to have standards.
I showed Bryan the post while in a meeting room with him, left the room, and a few minutes later heard a very loud, very exasperated primal scream coming from the room!
Well, one example is that patterns in code now can make you recall bugs you've seen in the past. I had this realization where I used an LLM to do a big refactor, and it fixed a bug along the way that I should have realized was much more urgent than the refactor, having seen an identical bug in the past (it was related to prefix-checking in a set that wasn't constructed to do that kind of prefix-checking). Had I done the refactor by hand I'd likely have realized it much quicker.
This whole week I've been dealing with incidental complexity created by shortcuts taken and edge cases not handled in code written in the before times, both in mine and in others'. I realized at some point yesterday that these kinds of shortcuts would no longer be accepted with competent LLM use.
Right, when used incompetently. When used competently they can carefully reason through every edge case and flag things no human would have picked up on.
One example: in some old code I wrote I had assumed that the Rust Hash impl for a type is stable over time. This is not the case in general, but writing a custom hasher for a complex type is incredibly annoying, so I took that shortcut. That was fine for years, but came back to bite me this week as I was trying to update a dependency.
How much incidental complexity is due to that kind of thing? An LLM code review would flag this instantly, and one would also write a stable hash function for you.
Are you aware of comparative advantage? What matters is opportunity cost, not raw output. (Also, unit labor cost is wage per hour divided by output per hour, so the number of hours worked is not really relevant. In other words, longer hours make workers richer and not their output cheaper.)
This was worked out by David Ricardo 200 years ago. You still benefit from trade even if (granting the argument) you are worse at producing everything.
This is only tangentially related, but libuv and mio's Windows implementations use the undocumented AFD readiness-based poll interface [1], since there isn't a documented readiness-based interface on Windows. The undocumented interface is now effectively stable since, among other reasons, Microsoft uses Tokio in some of its products.
libuv does all sorts of shenanigans, like using the undocumented fields in STARTUPINFOW the CRT uses to pass file descriptors to processes inheriting handles so that you can open whatever file descriptor you need in your children processes like in POSIX
But Microsoft kind of expects this crap and will support it until the end of time; Apple can't give a crap until and will readily break programs even when they use legal APIs
> Decoupling the User/Kernel boundary in Windows is a monumental task and highly non-trivial, however, we have been working hard to stabilize this boundary across all of Windows to provide our customers the flexibility to run down-level containers. Starting with Windows 11 and Windows Server 2022 we are enabling the ability to run process-isolated WS2022 containers on Windows 11 hosts.
reply