Agree, all of them in same industry mostly have similar posters. My eyes keep ignoring them and focus on service quality of barbershop and restaurants.
Norbert Wiener defined cybernetics as control and communication in the animal and the machine. He forgot to include the part where the machine's primary function is burning GPU credit with open-loop control.
Better workflow may require contributors to establish the problem and receive agreement before producing large patches, regaardless of whether AI is involved.
Well, the "you" now is not the same "you" 10 minutes from now. The only thing the new "you" inherits is your code, but otherwise it could be a different person. So in a way we are code too.
Yes, this is fantastic! I'm trying it right now. I look forward to the day when LLM inferencing can be done in a sql query and take less than the age of the earth to do something. This works way better than I would have expected, since, well, it's sql all the way down.
I noticed the cedardb.com blogpost on the project is slashdotted at the moment, but the game itself plays just fine.
Off topic, but say you have a program that needs to calculate something but takes a long long time, how to counter hardware failure without needing to calculate everything from the start?
Typically you use redundant computations, which don't have to be done from the start. You could calculate intermediate values and check them before proceeding
They converted linear algebra expressions into relational algebra expressions, optimized them using equality saturation and converted back into linear algebra. With some noticeable speedups.
They used relational algebra for optimization because relational algebra has canonical form - there is only one most optimal expression.
And, equality saturation is most efficiently implemented using generic join algorithm.
Redaction should be a tested security operation, not a visual formatting step. If copy-and-paste, a PDF parser, or OCR can recover the content, the document was never redacted.
A GC latency SLO should include operating-system memory pressure. Otherwise, a page-fault problem will look like a collector problem and lead to the wrong fix.
Swap latency explodes when you get into a swap storm where tasks continuously touch different pages and fight to get things paged in and out, forming a queue waiting for swap IO.
The other thing causing multi-second pauses is approaching OOM and the system attempting some last-ditch efforts before unleashing the OOM reaper, but that's not strictly swapping, it'd also happen on a swapless system.
If it's only a single fault I'd expect it to be to be dominated by IO latency, which is pretty good on NVMe. As the article shows those 40ms were accumulated over hundreds of pagefaults. The problem there was that there was a stop-the-world pause stalled by all those pagefaults together.
A fully-concurrent and swap-friendly GC you could maybe define that it only increases the active working-set by x GB on top of what the application itself (and the rest of the system) is actively using and will only page-in y GB per second. And it'd do so on GC threads, not the application threads.
Whether that would be sufficient to not cause a swap storm would still depend on all the other stuff happening besides the GC.
Important adoption questions include corpus coverage, fuzzing duration, malformed-input limits, API compatibility, and comparison with other Rust decoders.
reply