I had a very different reaction to this, because I just released a Rust library called ironbeam [0] without knowing anything about this. It was intended to be a pun on Apache Beam and the fact that iron can rust... I guess I'll have to live with it for now because it's way too high-effort to rename it after a stable release.
Readit Newsnhubbard commented on IDF to receive 'Iron Beam' laser interceptors at the end of the month timesofisrael.com/idf-to-... · Posted by u/mhb
nhubbard commented on Bending Spoons acquires Vimeo for $1.38B investors.vimeo.com/news-... · Posted by u/nixy
Oh no, this is undoubtedly going to be terrible for the companies that built their OTT platforms on Vimeo. E.g. Dropout.tv.
nhubbard commented on Lewis and Clark marked their trail with laxatives offbeatoregon.com/2501d10... · Posted by u/toomuchtodo
Of course, Tom Scott and the Citation Needed crew made an amazing episode about this: https://www.youtube.com/watch?v=KrO_ZMQ8aFc
nhubbard commented on My first verified imperative program markushimmel.de/blog/my-f... · Posted by u/TwoFx
Which languages do support TCO at this point? From my recollection we have
* Scheme
* Haskell
* Elixir
* Erlang
* OCaml
* F#
* Scala
* (not Clojure)
* the JVM could remove tail-recursive calls, but IIRC this still hasn't been added for security reasons
* Racket
* Zig
* Lua
* Common Lisp, under certain compilers/interpreters
* Rust? (depends)
* Swift? (sometimes)
Kotlin as well, through the ‘tailrec’ marker on a function.
Archived post: https://archive.is/J2oZn
nhubbard commented on Nvidia's RTX Pro 6000 has 96GB of VRAM and 600W of power theverge.com/news/631868/... · Posted by u/mfiguiere
Apple uses LPDDR4 which comes in densities of up to 16Gb AFAICT. So they can have ~5X as much memory using the same bus width.
Apple uses LPDDR5X, not LPDDR4, iirc
I can read that as applying personal phones hooked up to employer services. I think it's pretty common to force employees to consent allowing their employers to manage their device to get access to work email on it. I'd always assume that just mean they could remote wipe it, but maybe it's even worse than that.
Reading the post makes it sound like this only happens on managed devices; whether that means "owned and provided by work", "within the confines of the work profile on a BYOD devices", or both, I'm not 100% sure.