classichasclass

This ( https://learn.microsoft.com/en-us/windows/arm/arm64ec-abi ) feels a lot like a modern rethinking of Universal Procedure Pointers (i.e., between PowerPC and the 68K emulator on Power Macintosh).

> frankly no one will bother to build them for RISC-V.

Welcome to our pain in OpenPOWER world, though at least we have the weight of IBM to encourage some ports, and for the big Power chips emulation is still reasonably practical.

If nothing else, there are still legitimate medical risks to catching COVID for people who are immunocompromised (at minimum). A good mask lets them at least have less risk being out and about.

Plus, given how often it mutates, perhaps people just don't want to get sick again even if they don't have any long-term aftereffects.

(author) This one has actually been in my collection for around a decade and is not a recent acquisition. I've just started playing with it more and figured I needed to shore it up to keep it going.

(author)

> In other words, like a bytecode VM?

Kind of, but it's still Forth of the era, so it's still threaded execution. You're still jumping from execution address to execution address (either native 68000 code or another set of Forth words heralded by a JMP to the nesting subroutine); you just have a layer of indirection by having to look them up in the token table first.

My late father (small animal vet) got approached by VCA and Banfield multiple times to sell out, but he was pretty sure he wouldn't make the same amount and he liked having his own full scope practice. He was the minority even then.

Wow, I had no idea it was that iffy under the hood. I might do more messing with the flash if it gets goofier. Yes, the issues with VC++ got annoying in a hurry.

(author) Thank you! But this was actually not very difficult. The PE format is well-documented, so I just extracted the code segment addresses, then generated an ELF by emitting code like this with a hacky Perl script:

  .globl main
  main:
     trap
     .byte 0xfc
     .byte 0xff
     ...

etc. Assemble, run that in gdb, it traps immediately, and just disassemble from PC.

(author) Hey, thanks!

Maybe I'm old-fashioned, but to this day I don't take notes on the computer when I'm in the room with a patient. I might take a couple notes, but otherwise I do it between patients or after hours. It seems discourteous to me otherwise.

That said, I have a prolonged charting period after every clinic. It's not sustainable in daily practice (I don't see patients every day).

If you have to ask, you shouldn't install it. This is entirely in keeping with the philosophy of 9front.

The electronic health records bit totally resonated. I was involved in a selection committee for a new health record for the municipal public health clinics I worked for a number of moons ago as the physician champion. They went with the product that the billing, finance and statistics department wanted, ignoring the fact that the interface was poorer for the clinicians and that the beancounters worked with the data, not with the program itself (i.e., forgetting that "garbage in garbage out"). I made the strategic mistake of saying honestly that we could learn to work with anything but it was suboptimal; they heard the first part but not the second and went with it, then they got mad when I refused to endorse it and sell the other clinicians on it. In the end it was never implemented and they chose Epic a few years later that now everybody hates. A massive waste of time and money.

Currently our house in a modest corner of So Cal is at a ridiculous valuation. I happen to like our house and I think it's nice, but it's not that nice, and this feels like a bubble getting bigger. I know there's a lot of controversy over Proposition 13 and its budgetary effects, but we'd be getting a whopping bill this year if it weren't in effect, and this is a factor not within our control.

I went from an HP 95LX to a Palm m505. The 95LX could, in theory, do more, but I got more out of the m505 because of the tap interface (rather than typing commands) and the smaller slate form factor (more portable, less clumsy, not a clamshell). I still used the 95LX for certain specific tasks but the m505 was there when I needed it and didn't feel like a burden.

My main issue with these two (and don't get me wrong: I'm delighted people are trying) is that they hit the uncanny valley pretty hard. They get enough of it right that the small differences really stick out, particularly things like font and text positioning. It almost makes me wonder if a Aqua-esque window manager with window buttons on the left -- and stopping there -- would be more successful than trying to get all the quirks in.

Originally, but then Palm bought them.

I was always a Memorex connoisseur myself in the 5.25" era, with the classic brown ruled sleeves.

Well, of course it is. The information density is less in AI writing, and as more AI writers are trained on more AI writing, will approach random entropy. This is merely thermodynamics at work. /s

Definitely some similarities. The DG-1's main advance was the full LCD panel (looks like this one also was 80x16 similar to the Visual Commuter).

What did you work on? Any of the micro stuff or mostly on the mini side?

And this is where Perl 5 says hi. It's also widespread and easily available, can do anything awk can, and isn't similarly fractured (Raku now being its own spinoff world). The article's complaints about its syntax are a matter of taste, of course.

Another 160-in-1 alumnus. I wish I could say I learned a lot from it, but I was probably too young to really get into it. I did build some of the circuits and had some fun messing around, though, so it was hardly wasted (but the 30 in one I got as a gift later was smaller and no less fun to play with).

(author) I thought AS worked pretty well. The syntax is a little idiosyncratic but it "just worked" once I learned its pet peeves, and it seems to have specific support for the added 9995 instructions.

And thus demonstrated is the value of lots of different implementations of a spec. Already one hole found in the spec in just this article, and I'm sure there will be/were more.

(author) Both GEnie and AppleLink used the same backend, which GE called the Mark III network, so there were some operational similarities.

(author) Front end or back end? Anything interesting about its operation or the protocols?

> Or, they can go after the same original sources you have cited and write their own summarizing article (but not copy the blog post, and they also can't add any of their own conclusions).

That's my point: you've done the legwork, but you don't get credit for it, and as far as Wikipedia's policies are concerned, can't. They aren't supposed to cite your blog as a source, because it's self-published. I've seen many edits citing what I thought were well-researched entries get reverted because "it's a blog."

The part that never made sense to me is that the exact same content on Wikipedia is proscribed, but if you put it somewhere else and someone else links to it, it somehow becomes OK. From where I'm sitting, the content is either fine or it's not.

A variant of this: you do the research, cite your findings with presumably reliable sources and post it somewhere like a personal blog. Wikipedia doesn't like directly linking to it [0], but if an editor writes the same content and cites the same sources, that's also OK, even though I'd argue that's plagiarism.

0: https://en.wikipedia.org/wiki/Wikipedia:Verifiability#Self-p...

Would they? Wouldn't that be "original research"?

This is well done, though for some of these movies the camera moves are at least as important as the composition of any one frame. Kubrick is a good example, but hardly the only one.