I asked Gemini to format some URLs into an XML format. It got halfway through and gave up. I asked if it truncated the output, and it said yes and then told _me_ to write a python script to do it.
I've spent several years optimizing a specialized IPC mechanism for a work project. I've spent time reviewing the Linux Kernel's unix socket source code to understand obscure edge cases. There isn't really much to optimize - it's just copying bytes between buffers. Most of the complexity of the code has to do with permissions and implementing the ability to send file descriptors. All my benchmarks have unambiguously showed unix sockets to be more performant than loopback TCP for my particular use case.
There's definitely differences, whether or not it matters for most usages. I've worked on several IPC mechanisms that specifically benefited from one vs. the other.
A former coworker texted me out of the blue yesterday, saying he missed working on a "<my name> codebase". He specifically appreciated that "doing something simple things were kept simple." Made my day!
The folk that made Crash Bandicoot were pretty clever. They figured out that the PlayStation could render untextured, shaded triangles a lot faster than textured triangles, so they "textured" the main character with pixel-scale geometry. This in turn saved them enough memory to use a higher resolution frame buffer mode.
Crowded? No. Littered? Perhaps, depending on the altitude. The article you linked says the bulk of the existing debris is from a few isolated incidents.
These satellites are generally low enough tha their orbits decay after a couple years if they don't boost themselves, and then they burn up in the atmosphere.
I've gotten CEC to work in Linux on my desktop computer. The funny thing is that most GPU HDMI ports don't implement CEC, but do implement CEC over DisplayPort. You simply need to find a DisplayPort to HDMI adapter that supports CEC.
A more obscure use would be for loading multiple instances of a singleton library. This is especially helpful in something like a unit test suite, where you want each test case to start in a cleanly initialized state. If the code under test has a bunch of globally initialized variables, reloading the library at runtime is one of only a few possible ways of doing it.
In my experience, a culture of radical employee-driven compensation transparency can lead to toxicity. A subset of folk have a tendency to become obsessed, and increasingly more resentful about their particular notion of fairness. Then from that, folk start to play the victim, grasping for explanations that don't require introspection or admitting individual responsibility. In that environment, the company is forced to take a defensive position, which makes the culture even more toxic.
What I've seen work well is the company taking pro-active steps to be transparent about compensation in aggregate. For example, HR can put out a periodic report documenting compensation metrics by job title and experience. They can also slice the data along various social factors to quantitatively show whether there's any indicators of unintentional bias. From there, another good idea is for the company to regularly apply adjustments independent from performance, in order to keep the metrics healthy.
Is email not customary? It seems like it would be fine as long as they respond in a timely manner, and provide access instructions. Also, in this situation it seems like that's exactly what happened.
I suppose what might be non-compliant is if their website doesn't explicitly document the process to access the source, i.e. "send an email to this addressm to request the most up-to-date source code."
Given that it's shared memory based, it seems like there has to be some degree of trust that the participants are well behaved. What do you mean by a malformed message, though? If you're talking about the payload of the message, that seems like a matter of the message scheme you're using. If you're talking about correctness of the IPC protocol itself, integrity checking is unfortunately at odds with latency.