_nalply

Some projects have their own jargon. Two terms I ran into recently are "surface" and "oracle." I'm a greybeard programmer who started in 1983, and both were new to me. I grasped them immediately once I asked my favorite florid model what they meant.

A surface is whatever the user interacts with: a GUI, a TUI, an API, or anything else. I once exposed some functions of a web app on the window object. Boom, a surface for working in DevTools.

An oracle is a simple, independent way to compute a result. It may be limited, but it's still useful for testing, because you can check the real implementation against it.

I understand that programmers like me may dismiss all this as hot air. But it's just jargon.

And "predictive surface"?

It's a surface that anticipates what you'll want next and shows it before you ask. For Spinal, this might be simple. Say you query for all functions whose names start with x, that take an int32_t argument, and that return void. The result list doesn't just give you names; it also shows, visually, how often each function was edited, how long it is, and how complex it is. In other words, it displays information eagerly.

Disclaimer: I'm not affiliated with Spinal. I'm only guessing from the demo on their site.

It's the typestate pattern. The compiler enforces valid state transitions and so you can't just pass to the same function. It's useful to ensure that only some transitions are allowed. To be honest, the connection state presented by GP is a bad example. But you shouldn't say "it defeats the point".

A better example is an HTTP writer. One state is `Headers` with the methods `add_header()` and `body()` which returns the response in state `Body`. This enforces that one can't add headers after `body()` has been called. But you can finish the response in the `Body` state. If you do something not in this order, you get a compile error.

I got a car whose cruise control state was never displayed (the mechanic used the wrong dashboard), but since it worked anyway, I accepted it. So that's a data point (me) that modal buttons do work.

But "should not depend in the GUI to keep up" is wrong, I think. It needs at least one LED per mode. Because sometimes it's a bit annoying. Rarely cruise control doesn't engage or turns off by itself or something caused the cruise control mode diverge from what I have in mind, and a quick glance would help to resync.

I think the possiblities that a minority can leave the group is an important escape valve for them. Now assume that in the future they are going to be not such a minority anymore like today, then what happens? Maybe some oscillation like for Lotka-Volterra situation, perhaps a bit different?

I found grandparent's post still useful because it caused something to click in my head. I then researched and found that threads and processes share a lot of functionality. In the kernel both processes and threads are represented by `task_struct` instances.

So, respectfully, you shouldn't dismiss grandparent with "This isn't really true".

Lipreading Deaf here.

I tried to lipread the Inauguration, and where it was successful I did read the same nonsense, but often it wasn't possible because they weren't looking at the camera or the microphone was in the way.

The Seagulls, however, the only thing I could read was amm-amm-ammmmm-am-am-aaaammm. Nothing else. Of course, the doll has very simple mouth mechanics.

I am Deaf. I lipread German, but rarely lipread English and was successful with lipreading people speaking English as not their native language, namely Greek, Estonian and Marathi but never from the Anglophone world. Turning older, my lipreading competence declines, and I prefer talking in my local Signed Language.

What this article is missing, I think, is that lipreading is not replacing auditory input with visual input because there are too many, let's just call them homophones. I find the word "visemes" a bit too cute. You need a lot of context. So I always struggle if someone asks me a very short question, because I don't know what it's about. Someone comes to me, says hello, and asks the question, and I don't have an idea what they want to know.

Re gameplays, the context is special, because you can assume that the football coach is not shouting "HAKUNA MATATA" over the field. This simplifies lipreading during gameplays. Essentially it devolves into something like a set of radio buttons.

How do you manage zone 5 cardio 4x a week without PEM?

I thought up to 3x a week and never consecutive days is the maximum.