workerd
webusb
Our great sponsors
workerd | webusb | |
---|---|---|
37 | 10 | |
5,655 | 1,285 | |
5.2% | 0.9% | |
9.9 | 6.5 | |
7 days ago | 5 months ago | |
C++ | Bikeshed | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
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.
webusb
-
Why are websites requesting access to motion sensors on my desktop?
> WebUSB is actually a W3C open standard.
This is misleading at best. Here’s what the actual spec says <https://wicg.github.io/webusb/>:
> This specification was published by the Web Platform Incubator Community Group. It is not a W3C Standard nor is it on the W3C Standards Track.
It’s an experimental spec by Google (observe the affiliation of the three editors: all Google); Mozilla has adopted a negative position on it <https://mozilla.github.io/standards-positions/#webusb>; WebKit has not remarked upon it.
- How to do dfu from mobile application over usb
- Mozilla and Quad9 both believe in a non-censored, free and open internet. If Sony Music wins a lawsuit against Quad9, this could end up with mass censorship across ALL DNS providers.
- You should probably disable WebUSB and WebBluetooth in Chrome
- Show HN: Postgres WASM
-
The baseline for web development in 2022
This is such a lame argument. You want it to be true but have no evidence that it actually is true.
A lot of the Chrome team's "standards" have problems with accessibility, workability on mobile, security[0], privacy[1], or just battery life. Some are neat experiments that are or only will be used in the wild by advertisers to track and identify users.
Because the Safari/WebKit team doesn't have to chase users for revenue like Mozilla does they can afford to be more conservative with what Google "standards" they support. Being able to offer a tighter privacy posture or efficiency is part of the iOS/macOS sales pitch.
[0] https://github.com/WICG/webusb/issues/50
[1] https://www.theverge.com/2021/4/16/22387492/google-floc-ad-t...
-
Porting USB applications to the web. Part 1: libusb
Limiting it to installed apps still has the problem of users blindly agreeing to something that is fundamentally super dangerous. I don’t believe installing PWAs currently exposes any new security surface, so this would be a significant change, and worse still a persistent hazard with probably no indication of what’s going on when it’s in use. I think there’s still potential in the general concept, but it’d take work and is certainly not ready yet in any browser.
Yes, certain classes are restricted from access via WebUSB for security, https://wicg.github.io/webusb/#protected-interface-classes. But as the note says, it’s about balance: that list is necessary for security, but not sufficient.
- Ledger Won't Connect to Anything in Any Browser
- WebUSB API
- Nano Ledger S & MyHBARWallet connection issue.
What are some alternatives?
cloudflare-docs - Cloudflare’s documentation
evilgophish - evilginx3 + gophish
js-compute-runtime - JavaScript SDK and runtime for building Fastly Compute applications
file-system-access - Expose the file system on the user’s device, so Web apps can interoperate with the user’s native applications.
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.
postgres-wasm - A PostgresQL server in your browser
fauna-schema-migrate - The Fauna Schema Migrate tool helps you set up Fauna resources as code and perform schema migrations.
standards-positions
lagon - Deploy Serverless Functions at the Edge. Current status: Alpha
actually-serverless - Dynamic HTTP Endpoints in your Browser
go - The Go programming language
byoda - Data breach resistant application: Bring Your Own Database