> In Dark, making an API call is as simple as a function call. Our tools for building connectors to 3rd party services handle rate limiting, authentication, error handling, and retries, with great default behaviour. Visibility around costs and failures are built into the editor, as is support for secret keys and Personally Identifying Information.
The history of RPC is...checkered. It's possible that every attempt to make remote process calls as simple as local function calls has resulted in terrible abstractions that leak like a sieve.
My suggestion (for what it's worth) is to bake the notion of message passing into the language, and make it as simple as possible.
I'm talking about using 3rdparty APIs, like Twilio or Stripe or something, that we don't have control over and that we need to handle. So we want it to feel like calling functions, though in practice it needs to be able to handle all the stuff that goes wrong.
Can you link to something about message passing? I'm familiar with a concept with this name, but I don't quite see what you mean.
I don't think it's really similar to Eve at all, except that it's an outside the box look at how we code. We're extremely focused on the backend coding use case, and solving known problems. I think Eve was on the path of experimenting to come up with a new way of doing computing, while we basically know what we're aiming to build already (and mostly have for over a year now).
That said, it has a lot of similarities to LightTable, especially regarding coding with live values.
Great! That got us our first two customers, and it allowed us prioritize really effectively for what they actually needed. And it cost us almost nothing, like $15k total - a great investment :) Would you read a blog post on this?
Probably September, though no promises. We're still redoing some core metaphors. Codewise, you can expect it to look similar to Elm/OCaml - functional/imperative language with structured error handling and no null.
The history of RPC is...checkered. It's possible that every attempt to make remote process calls as simple as local function calls has resulted in terrible abstractions that leak like a sieve.
My suggestion (for what it's worth) is to bake the notion of message passing into the language, and make it as simple as possible.