Differences

This shows you the differences between two versions of the page.

--- newsletters:2024-08 [2024/09/04 02:32] – [What we'll be up to in September] osnr
+++ newsletters:2024-08 [2024/09/04 02:36] (current) – [3D calibration] osnr
@@ Line 240: / Line 240: @@
 Omar: We merged 3D calibration! This is a huge advance that's been in the works for much of the last year -- we're being aggressive by merging, there are still things to fix and it's only roughly on par with the old 2D calibration (better in some cases, worse in others) -- but this is why we are pre-alpha and don't promise anything to users yet :-)
+(it also means that regions are now deprecated compared to quads)
+{{:newsletters:pasted:20240904-023549.png?400px}}
 (3D calibration is also quite important for the portable gadget system, since it has no fixed plane in front of it that we could 2D-calibrate.)
@@ Line 306: / Line 310: @@
 Erlang is weird because of all the [[https://www.erlang.org/docs/20/man/erl_nif#lengthy_work|hinting]] it requires. Erlang programmers aren't normally directly writing and calling C functions, so they treat it as an exception that you mark up if you expect unusual blocking.
+{{:newsletters:pasted:20240904-023519.png?400px}}
 Go actually seems very close to what we want. It's a work-stealing scheduler that can deal with arbitrary CPU blocks and I/O blocks in a goroutine. It has a little bit of hinting to know about long-running work in advance (it can detect syscalls, since they all go through the Go runtime), but it also has something called [[https://medium.com/@blanchon.vincent/go-sysmon-runtime-monitoring-cff9395060b5|'sysmon']] which is basically my hacky outside monitor process proposal, so it can adapt to arbitrary blocking like we want.