Comment

Comment by _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.

parent _nalply 23 days ago

No comments yet

Be the first to share your thoughts.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton