sargun

This is massively different from DynamoDB.

I accidentally dropped something into an iron mountain bin years ago, and just pried it open with a screwdriver.

I accidentally took down our corporate network multiple times ~20 years ago, because I was setting up virtual networks with Linux machines acting as l2 bridges, and with proxy_arp to on. The DHCP server only checked for an arp reply, and I caused our server to run out of IPs. It had a cache and nobody knew how to clear it, so we just had to wait it out.

Eh, at least one of those -- the "crashing the node" with messages argument is weak-ish, you can setup:

  erlang:process_flag(message_queue_data, on_heap),
  erlang:set_process_info_limit(memory, 1024000).

Isn’t the highly connected nature of the model layers problematic to build into physical layer?

I find it a little funny how much the government spends on these dead end investigations. We never will know precisely how much is wasted.

What ethnicity are you? I went through an airport -- and nobody else got screened except me. What was special about me? I was the only non-white person in the airport. Upon complaining, this was the response:

> Random selection by our screening technology prevents terrorists from attempting to defeat the security system by learning how it operates. Leaving out any one group, such as senior citizens, persons with disabilities, or children, would remove the random element from the system and undermine security. We simply cannot assume that all terrorists will fit a particular profile.

Andy Pavlo absolutely seems like the kind of guy that I would want to get a drink with.

So, you’re essentially washing the soil in DMSO, and DDT is more soluble in DMSO? — curious, what does it take to wash all that soil?

I have wondered why the likes of McKinsey, KPMG, and PWC do not put up candidates (don't even sponsor them, just say you're electing _well known consultancy_).

The author (Cong Wang) is building all sorts of neat stuff. Recently, they built kernelscript: https://github.com/multikernel/kernelscript -- another DSL for BPF that's much more powerful than the C alternatives, without the complexity of C BPF. Previously, they were at Bytedance, so there's a lot of hope that they understand the complexities of "production".

What's the US Customs ruling in question? > This update was enabled by a recent U.S. Customs ruling.

I really like the manycores approach, but we haven’t seen it come to fruition — at least not on general purpose machines. I think a machine that exposes each subset of cores as a NUMA node and doesn’t try to flatten memory across the entire set of cores might be a much more workable approach. Otherwise the interconnect becomes the scaling limit quickly (all cores being able to access all memory at speed).

Erlang, at least the programming model, lends itself well to this, where each process has a local heap. If that can stay resident to a subsection of the CPU, that might lend itself better to a reasonably priced many core architecture.

I think the most interesting thing about this is the origin of the project - multikernel. It seems like someone is building Solaris zones for Linux.

Investment gap is what I'd say too. While Rust, Go, Python, etc... have had massive backers that have managed to invest a ton more into things like static analysis, type checking, and developer ergonomics, the Erlang ecosystem hasn't necessarily had the same love, and instead the major users have typically chosen to pivot, or build something outside of the BEAM.

What's the biggest barrier to creating a lot of antimatter?

No it wont. It's incredibly hard to build out a fully useful version of the Linux APIs, as shown to us by Cygwin, and WSL. Even if you built out a similar set of APIs, Linux itself offers a ridiculous set of interaction points where applications can tie together (for example, I can use inotifywatch to copy files out of my container as they're written). I feel like what you'll end up with is something like gvisor running on top of WASM. In which case, what did we gain from VMs at all?

Where does the capsaicin go? How much ends up in the bird's blood, egg, and muscles?

1. AWS and their account managers are relatively frugal compared to other enterprise sales teams. As far as I can tell, this is a good thing.

2. More

3. AWS has this idea of “customer obsession.” They will spend an absurd amount of time trying to understand your business and make sense of it.

What if I told you that a modern MBP has more IOPs (and faster individual cores) than servers that many large companies use?

Wasn't there a paper from Heidi Howard that stated you it's not actually f failures in 2f+1 nodes, but you can actually make the number of nodes that can fail a lot higher, if you have some nodes that have to take part in the quorum (or the prior proposal)? This feels roughly similar?

Is El Capitan entirely made of Oxide components?

I wish the article actually talked about the interesting nitro enclave specific features more. A lot of it just talks about the basic hardening of a Linux VM and writing secure applications.

Relyvrio was ALS drug.

I don't think any HIV vaccines have gotten to phase III yet.

I feel like Intel has embarked upon a bunch of good ideas like SDI (https://www.intel.com/content/www/us/en/manufacturing/softwa...), IoT / Edison (https://ark.intel.com/content/www/us/en/ark/products/84572/i...), Silicon Photonics (https://www.intel.com/content/www/us/en/products/details/net...), and SDN (https://www.intc.com/news-events/press-releases/detail/640/i...).

But, they manage to fail to capitalize on any of these. What's wrong with them?

I've found iPhones get real wonky <-5C. I think the safe storage temp is like -20C because it can damage the battery.

“You will never have less information than you do today”

I’ve loved the Buttplug project. I was hitting an issue with their Bluetooth library controlling a we-vibe, and someone offered to drive over from the other side of the bay to help debug it. Bluetooth sniffer, and all.

I wish that SSH would be disaggregated further. SSH has become the suite du jour for file transfer, remote access, and a handful of other things. Unfortunately, simultaneously, innovations have been made in transport protocols and elsewhere in the stack that we're unable to take advantage of.

SFTP is a great example of a protocol which has a discrete server (look! There's sftp-server on your computer. Nothing prevents it from running over TLS, or a web socket). I wish that this was the way the entire suite worked. I wish the multiplexing, and underlying shell implementation was transport agnostic (perhaps relying on SOCK_STREAM, or SOCK_SEQPACKET semantics), and the authentication, encryption, etc was its own thing.

With seccomp, you have syscall filtering. The bits that are left exposed are largely around mm, and depending on how the sandbox works, non-syscall APIs like io_uring. It essentially actuates kernel APIs to sandbox, and then redirects a number of APIs to use userspace reimplementations.