We've solved cloud.
Yes. You read that right.
Well, conceptually. More accurately, we're solving cloud right now. That's why you should join the rx beta and reserve your username today.
I'll spare you the cloud history lesson, but basically we (as an industry) went from mainframes deployed on-premises to whatever the heck you'd call what we have today:
Mainframes -> Servers -> Serverless -> to a mix of everything, deployed all over the place — on-premises, hosted, and multicloud.
Most people would say: Yeah, but it's still all servers, baby. And they would be right. But that's not my point here.
These all came with their own abstractions and ever-changing cloud paradigms and deployment patterns. It's like we have to completely change the way we write and ship applications every 2 freaking minutes.
You know which abstraction has remained constant during that time? The function.
Ah, the function. The simplest callable unit of code.
The idea of a callable unit was initially conceived by John Mauchly and Kathleen Antonelli during their work ... January 1947 ... Maurice Wilkes, David Wheeler, and Stanley Gill are generally credited with the formal invention of this concept, which they termed a closed sub-routine ... Alan Turing had discussed subroutines in a paper ... going so far as to invent the concept of a return address stack.
That's all for the free Wikipedia history lesson. Continue reading on Wikipedia.
To put it simply, we are short custom cloud abstractions, and long fundamental computing primitives, like the function.
Functions are all you need.™
rx removes a whole suite of tools from your software supply chain.
I haven't told you much about how we've "solved cloud" yet. I'll be revealing more about these concepts in the next post, coming to your browser soon (Monday April 29 2024).
If you enjoyed this post, consider signing up for the rx beta here:
We respect your inbox and your privacy.