4,349 karma · joined August 4, 2023
I thought we were railing against Big Hospital/Big Insurance here? They'd love a cheap diagnostic.
Send an email to this head-and-neck oncologist's lab. I saw a talk he gave at a Chicago-area national lab on open-source models for identifying malignancies in scanned pathology slides, and was smitten.
PS – I am looking through the NuBus cards that I have... did you work for SuperMac or RasterOps?
Well, in domains like SWE where Anthropic's putting in the effort. I don't they'll make the claims that OpenAI makes about how their models are pushing the life sciences forward, for example.
Even without considering the Census data products alone, Census demographic data underlies virtually all extrapolation from other survey research. Everything from national opinion surveys based on tens of thousands of respondents, to small community surveys. A Census product with the most diverse participation pays off almost infinitely for America. It benefits everyone from national newspapers to rural counties.
If the smallest communities lose what little trust remains in the privacy of the Census, they have the most to lose in all of these ways.
Did the old 11" MacBook Air not teach the Wintel brands anything?
I might be missing something here, but wouldn't any UI toolkit that doesn't live within a WebView work?
For a comprehensive answer, a good vintage introductory digital design textbook is Ward and Halstead's 1989 Computation Structures, from the "peak CISC" era! [1]
There, the second (vertical) type is often used for highly complex instructions/fancy addressing modes, that you might want to implement with some sort of procedure abstraction, loops, working memory, etc. A "luxury" vertical microcode engine would have facilities like "microprocedure calls", a micro-stack and workspace RAM, a micro-ALU, dispatch table micro-instructions. The authors use the suggestive term "interpretive microcode".
String instructions come to mind as a complex example; non-register machine architectures (stack machines); tagged data architectures that have instruction-level polymorphism (e.g. Lisp machines).
The culminating project of Ward and Halstead is an elaborate two-level microcode system (vertical on horizontal/second on first). I think the first Motorola 68k had this architecture -- here is the patent. [2]
It's genuinely a fun read. The "write an micro-interpreter for your CISC ISA" approach is hopelessly out of date now that we need pervasive microarchitectural parallelism, and have HDLs.
[1] https://www.amazon.com/Computation-Structures-Optical-Electr...
[2] https://patents.google.com/patent/EP0011412A1/en?inventor=Ha...
Apple II forever!
Bringing the rainbow to you!
(Join us.)
Well, no wonder people don't have faith in the people selling AI.
> Before leaving, I asked him whether he even knew what was inside the package.
> He answered very casually that he had no idea and that he did not need to know.
> I then asked whether he at least knew which company had entrusted him with the delivery. He replied that it was simply "a friend" who had asked him to temporarily keep the box until someone came to collect it.
> I switched it on briefly, and that was actually the moment when the hardware shop owner himself suddenly became excited[...] Seeing the Apple logo appear on the screen, he immediately smiled and said something along the lines of, "Ah… a MacBook is a MacBook. Apple is still Apple."
Recent MAHA-era large-scale funding opportunities have embraced this as "gold-standard science", and explicitly require separate reproducibility teams.
Link to source: https://github.com/EVV1E/waylandcraft
Absolutely. I think TFA is hooking into the actual code emitter used by SBCL's evaluator-compiler, since it's not actually primitive, but implemented in Lisp and loaded into the image itself.
My guess at context: from the earliest days of Lisp, I think there was an expectation that Lisp systems would expose as much of their internals as possible... including their internal JIT, which is being plugged into here. I think the name for it was the "LISP Assembly Program" (LAP).
> Of [the 32], 14 no longer work for, or with, us, some of whom stopped as long as five years ago. Six are ex-armed forces veterans whose public sector experience involved serving and protecting their country.
> Not only do we entirely reject claims of an alleged ‘revolving door’ strategy, but we also believe it is inappropriate to include veterans in a report alleging such a strategy. Aside from the immense value of their experience, there is rightly an undertaking by government and society to ensure they are afforded the opportunity to build a career outside the armed forces when the time is right for them.