tempest
workerd
tempest | workerd | |
---|---|---|
2 | 37 | |
92 | 5,751 | |
- | 4.4% | |
8.6 | 9.9 | |
11 months ago | 2 days ago | |
Cap'n Proto | C++ | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
tempest
-
Cap'n Proto 1.0
Yes, he was the most active developer over the last few years, although it wasn't a huge amount of activity. And that activity had dropped off this year as Ian shifted his focus to Tempest, a mostly-from-scratch rewrite. https://github.com/zenhack/tempest
For my part I stopped pushing monthly Sandstorm updates this year as there hasn't really been anything to push. Unfortunately Sandstorm's biggest dependencies can't even be updated anymore because of breaking changes that would take significant effort to work around.
I agree a blog post is probably in order.
-
Sandstorm: Open-source platform for self-hosting web app
Tempest [0] looks very interesting. What is the current state of the project?
[0] https://github.com/zenhack/tempest
workerd
-
Cloudflare acquires PartyKit to allow developers to build real-time multi-user
Standards bodies only standardize things after they've been proven to work. You can't standardize a new idea before offering it to the market. It's hard enough to get just one vendor to experiment with an idea (it literally took me years to convince everyone inside Cloudflare that we should build Durable Objects). Getting N competing vendors to agree on it -- before anything has been proven in the market -- is simply not possible.
But the Durable Objects API is not complicated and there's nothing stopping competing platforms from building a compatible product if they want. Much of the implementation is open source, even. In fact, if you build an app on DO but decide you don't want to host it on Cloudflare, you can self-host it on workerd:
https://github.com/cloudflare/workerd
-
Python Cloudflare Workers
In any case, I welcome this initiative with my open hands and look forward all the cool apps that people will now build with this!
[1] https://pyodide.org/
[2] https://github.com/cloudflare/workerd/blob/main/docs/pyodide...
[3] https://github.com/cloudflare/workerd/pull/1875
-
LLRT: A low-latency JavaScript runtime from AWS
For ref:
- https://blog.cloudflare.com/workerd-open-source-workers-runt...
- https://github.com/cloudflare/workerd
-
A list of JavaScript engines, runtimes, interpreters
workerd
-
WinterJS
I think this is for people who want to run their own cloudflare workers (sort of) and since nobody wants to run full node for that, they want a small runtime that just executes js/wasm in an isolated way. But I wonder why they don't tell me how I can be sure that this is safe or how it's safe. Surely I can't just trust them and it explicitly mentions that it still has file IO so clearly there is still work I need to do customize the isolation further. But then they don't show any info on that core usecase. But then that's probably because they don't really want you to use this to run it on your own, they are selling you on running things on their edge platform called "Wasmer Edge". So that's probably why this is so light on information.. the motivation isn't to get you to use this yourself, just to use this their hosted edge platform. But then I wonder why I wouldn't just use https://github.com/cloudflare/workerd which is also open source. Surely that is fast enough? If not then it should show some benchmarks?
- Cloudflare workers is adopting Ada URL parser
-
Cap'n Proto 1.0
i love how the main reference for workerd can be just one capnp file.
https://github.com/cloudflare/workerd/blob/main/src/workerd/...
this changed my world how i think about computing on the web.
if there was just a good enough js library as for lua and you could directly send capnp messages to workerd instead of always going through files. I guess one day i have to relearn c++ and understand how the internals actually work.
-
Cloudflare Workers Introduces Connect() API to Create TCP Sockets
A significant chunk of it is open source: https://github.com/cloudflare/workerd/
-
JSON with multiline strings
Some of the configuration files for applications wind up being an entire language unto themselves, e.g., https://github.com/cloudflare/workerd/blob/1b5057f2bfcfedf146f6f79ff04e99903d55412b/src/workerd/io/compatibility-date.capnp
-
Am I out of touch for trying to limit my stack to containers?
Edge runtimes are very good alternatives to containers that shouldn't be dismissed for "not being containers". They're often faster, more scalable, and cheaper than containers. Them being so lightweight also enable a "nanoservice architecture" – being able to run every service on a single computer instead of running different services on different computers and having to deal with network latency and unreliability.
What are some alternatives?
ethibox - Open-source web apps hoster
cloudflare-docs - Cloudflare’s documentation
plugin - Javascript plugin for Capnproto
js-compute-runtime - JavaScript SDK and runtime for building Fastly Compute applications
exp-lazyproto - Experimental fast implementation of Protobufs in Go
lagon - Deploy Serverless Functions at the Edge. Current status: Alpha
CubiCAD - A fast and modern vulkan based rendering engine
fauna-schema-migrate - The Fauna Schema Migrate tool helps you set up Fauna resources as code and perform schema migrations.
runtipi - Runtipi is a homeserver for everyone! One command setup, one click installs for your favorites self-hosted apps. ✨
windmill - Open-source developer platform to turn scripts into workflows and UIs. Fastest workflow engine (5x vs Airflow). Open-source alternative to Airplane and Retool.
go-capnp - Cap'n Proto library and code generator for Go
go - The Go programming language