Technically you're right, they do. They don't really serve the US Consumer market (anymore) though. There's no (or comparatively very few) established sales channels with consumer retail vendors by SKHynix themselves in the USDM. It's all reseller stuff, often plucked from OEM devices (prebuilts, workstations, etc).
What you linked is OEM RAM. The enterprise market still uses lots of UDIMM's, even though it certainly favors RDIMMs. Yes, it's DDR UDIMM's that are compatible with consumer PC's. But it's not sold like Samsung or Crucial consumer-oriented memory is, at least in the US market. Check the availability of it compared to say Crucial or Samsung. It's virtually non-existant. Check the comments on that very site as well, note how many people are talking about getting them from pre-builts (aka OEM/SI). Note, SK selling UDIMMs to SI/OEM's for consumer products is not a "consumer transaction" to SK, that's a B2B enterprise sale to another company from SK's perspective.
So technically yes, but practically no, not in the US they don't. Elsewhere I'm unsure, but SK has been deprioritizing consumer DRAM sales for a while now, just like Micron.
This is a talk that was given Pr. Giulio Biroli in the Physics Department of a French University ("École d'Ingénieurs" technically) that talks about the use of generative AI in theoretical physics.
The love-hate relationship with LabVIEW is something I can not get closure about : great tool, abysmal ergonmics, revolutionnary piece of software, ubiquitous in some fields and still some LabVIEW ergonomics is just SO...bad : want to zoom on your diagram ? Out of luck !
Heard of death by a thousand cuts ? LabVIEW comes to mind.
That can be argued, but they're pretty esoteric. For example, what language are they written in? Fortran, assembly, etc.? Probably nothing the majority of developers or mathematicians can't understand. And creating bindings for them is non-trivial. I don't even know where to start from the website. And on the website, all the links to the routines are broken. https://www.netlib.org/blas/
The naming convention is a bit esoteric, but once you figure it out it's not too bad. I don't think writing bindings is too hard once you know what's going on. You most likely would want to write some kind of wrapper on top of that in order to make things a little more user-friend.
I will agree with you on the routines being broken. That happened within the past year. Not sure why it happened, but it's annoying. If you know the name of the routine you can usually find documentation on another site.
I was hoping to intercept and reverse-engineer the protocol of the Oura rings.
For some reason, I thought this kind of device would attract a lot of hackers given the platform capabilities but I could not f8nd any other documented attempt except the really thorough iFixit (destructive) teardown : https://www.ifixit.com/Teardown/Oura+Ring+2+Teardown/135207
For anyone interested, the main author (if I understood properly) did a presentation at RustNL on the UI aspect that was quite impressive performance wise : https://youtu.be/rC4FCS-oMpg
Technically, that talk is by the author of the UI system/IDE that uses the synthesizer as an extended hello world. The synthesizer itself is by a different guy ( https://thisisnotrocketscience.nl ) who's been calling his bassline synths somethingmetallicfish since almost forever.
