dhash

it's worth noting that the price of these monitors got cut in half due to this news -- great for the linux users out there

something worth mentioning here is that iSCSI is quite unhappy on congested networks or packet loss caused by incast traffic.

to make this actually work well, consider modifying your switches QoS settings to carve out a priority VLAN for iSCSI traffic

ImHex is amazing! It’s actively maintained, sponsored by FUTO, and is very hackable (both without recompiling, as well as modifying the grammars for others to take advantage of)

Post Mendeley shutdown, zotero has been an awesome replacement (while not being controlled by Elsevier). Given the amount of PDF's that I see during researchy times in my life, it's been an absolute godsend. Highly reccommend!

these guys also have some really nice distributed systems explainer videos

I love this kind of research since it correctly identifies some issues with the way the public interacts with LLM’s. Thank you for the evening reading!

I’d love to see future work investigating - how does this compare to expert users (doctors/llm magicians using LLM’s to self diagnose)

- LLM’s often provide answers faster than doctors, and often with less hassle (what’s your insurance?), to what extent does latency impact healthcare outcomes

- do study participants exhibit similar follow on behavior (upcoding, seeking a second opinion, doctors) to others in the same professional discipline

I love the vibe of squishing formats together — like APE.

I’ve had this problem in the past (shudders in Bazel’s WORKSPACE file) and what eventually ended up saving my bacon was org-babel.

Yes, it does mean that emacs is a build-dependency, but honestly literate programming pretty excellent for untangling the complexities of a large build.

fantastic — I’m sure folks who have poked binaries or written patches have all had the desire for something like this. Glad to see that it exists!

I’m definitely going to use this for solving some problems that i’m currently facing.

For anyone curious about what hare-brained scheme that one could hatch with this, i’d like the ability to do something like a PGO’d shared library —- watch the process run and exit, tracing all dlopen’s to create a new shared library with only the right functions from all the referenced libraries.

Hopefully this works, and if not, i’ll at least fail at something interesting :)

Taking a further step back from LLM’s, this is called portfolio / ensemble techniques in the literature.

A common practice in more formal domains is to have a portfolio of solvers and race them, allowing for the first (provably correct) solver to “win”

In less formal domains, adding/removing nodes/trees in an online manner is part of the deployment process for random forests.

+1 to miscommunication, but host_volume is indeed what I’ve used to allow host files into the chroot. Not all drivers support it, and there are some nomad config implications, but it otherwise works great for storing db’s or configurations.

I loved this post, and patchelf is a real gem of a utility.

Congrats Udayan on the launch!

It’s really neat to see the open-face nature of this product as compared to others doing EWOD with a second immiscible phase / a glass top plate that the droplet is squished under — makes it much easier to do IO to the chip.

Are the chips disposable, to accomodate contamination constraints, or is there some on-site surface reconditioning that we can do to refurb the chips?

Interesting to note that this is down-scaled from some of your older prototypes. What design tradeoffs made you go fron large open faced arrays to a set of smaller arrays?