So if you donate at silver or gold tiers, you get in the credits of @spritely's videogames, but if you donate at *diamond* tier you ALSO get unique, signed, one-of-a-kind creature artwork by me which I sketch on index cards https://spritely.institute/donate
Here is one I sketched last night!
@cwebber @spritely I know you have posted recently on this, but personally, I have no real handle on what "Spritely" is? Goblins? Scheme? What? It's so strange and intangible. I'm sure it's important and will make me red in the face one day, but right now I just don't get it.
I feel that communicating what the "thing" actually *is*, is important... How do I use it? How does it affect the near future? Or not? What does it promise? Why should I pay attention?
hth.
@dbat @cwebber @spritely We're actively working on our elevator pitch and trying to find what resonates. I'll give it a shot.
Spritely's mission is to empower developers to easily create, maintain, and debug distributed applications that foster secure collaboration and healthy communities. Tech that empowers people.
How do we do this? Our assessment is that existing tools/platforms are insufficient; it's just too hard to make distributed apps right now. It's for subject matter experts only. Spritely is conducting research and building a set of tools that significantly lower the barrier to entry.
The "flagship" if you will is Goblins. it's our distributed programming library. For message sending, we use the Actor model. For security, we use object capability security. For networking, we use a protocol we're co-developing with other non-Spritely organizations called the Object Capability Network. The sum of these parts is a library that allows the developer to focus on business logic rather than low-level protocol details.
We're very close to making trying Goblins applications (our early demos) as easy as visiting a URL in your web browser. The state of our developer tools is in the early adopter phase, I'd say. Usable enough for enthusiasts that can pardon the rough edges and missing features... but we're not far from having the tools and onboarding documentation for a larger crowd. We're holding this supporter drive to raise the money to keep this development going.
For those that like to read whitepapers, we have the Heart of Spritely that goes into more detail about the foundational technology: https://spritely.institute/static/papers/spritely-core.html
We also have a tutorial that covers some basic concepts, though again it's more for early adopter enthusiasts at the moment: https://files.spritely.institute/docs/guile-goblins/0.14.0/A-simple-greeter.html
Hope this helps!
edit: typos
@dthompson @dbat @cwebber @spritely I still don't understand all this, but I picked up the part about the developer being able to focus on the business logic, and that sounds really good.
@dthompson @dbat @cwebber @spritely Would the business logic be written in your new system, or would it use an existing language, like JSON?
@dthompson @dbat @cwebber @spritely What level of feedback are you soliciting and what is the preferred mechanism for delivery of same?