brooksmtownsend

31 ms·

1.
by brooksmtownsend 2y ago
Oh, and though WIT can be in-your-face in these tutorials (as we try to leave a good offramp for folks to customize beyond the quickstart) WIT shouldn’t be necessary for most common use-cases. There are standardized interfaces that language
2.
by brooksmtownsend 2y ago
To start with a bit of project history, we love Wasmtime and that’s our core runtime of choice! Before wasmCloud 1.0, e.g. from 2019-2023, we only used Wasm modules with our own custom ABI. Literally everyone was doing this at the time, to
3.
by brooksmtownsend 2y ago
First off, thank you for the thoughtful feedback here, it’s great to hear you’ve found the docs useful! I’ve read through your feedback and captured issues in our issue tracker for future improvements that will definitely go a long way towa
4.
by brooksmtownsend 2y ago
On the magic box concern, Wasm is pretty different from the other serverless approaches (isolates, BEAM, JVM-based, etc) that can be a bit more “magical”. A Wasm component can be inspected prior to compilation, the binary itself is a declar
5.
by brooksmtownsend 2y ago
Containers take seconds to start so a container must always be running. Wasm starts in microseconds and most Wasm platforms scale to zero by default because they do not suffer from cold starts. Wasm also offers incredible density characteri
6.
by brooksmtownsend 2y ago
We actually used to start with a Wasm-first perspective by focusing on explaining what Wasm is before focusing on our value props. This is good feedback though, we should call these out with more in-depth resources for learning. To name a f
7.
by brooksmtownsend 2y ago
That's what people do in enterprises because they have security controls and processes around k8s with too much investment. It's a no-go telling people to "just run this binary on this VM/baremetal machine", underst
8.
by brooksmtownsend 2y ago
It sounds obvious when you say it, and I appreciate the feedback! Marketing fluff is nice for messaging, but we'll take a look at getting comparison examples more front-and-center.
9.
by brooksmtownsend 2y ago
Wasm gives lots of benefits and as a project in a new-ish ecosystem we like to tout it and our goals as being a Wasm-native orchestrator. I think in general though nobody should care about running Wasm at all, just like you shouldn't r
10.
by brooksmtownsend 2y ago
Yep that's right, we do not require k8s. There's a ton of existing infrastructure into k8s so we try to make it apparent how you integrate there. The local CLI, wash, is an example of how we run locally, it's just a Windows&#
11.
by brooksmtownsend 2y ago
Hey! I’ve been a maintainer of wasmCloud since 2019, I’m glad it sparked some interest and I appreciate the time spent going through the docs and QuickStart. I’ll have to take another look and answer questions when I’m at the keyboard tomor
12.
Rust's Sneaky Deadlock With `if let` Blocks(brooksblog.bearblog.dev)
3 points by brooksmtownsend 2y ago|0 comments
13.
WASI 0.2.0 and Why It Matters(wasmcloud.com)
134 points by brooksmtownsend 3y ago|105 comments
14.
Better together: A Kubernetes and Wasm case study(cncf.io)
3 points by brooksmtownsend 4y ago|0 comments
15.
WebAssembly and the Road to Ubiquity(wasmcloud.com)
3 points by brooksmtownsend 4y ago|0 comments
16.
by brooksmtownsend 4y ago
I relate 100%. Everyone at my current job is sick of the soul-crushing work as a software developer that people just accept as part of the job. The side projects are so fun, we just want to do that for our real job. We call it "Write t
17.
Why WebAssembly Belongs Outside the Browser(wasm.builders)
16 points by brooksmtownsend 4y ago|0 comments
18.
Globally Distributed WebAssembly Applications with WasmCloud and NATS(wasmcloud.com)
9 points by brooksmtownsend 4y ago|2 comments
19.
WebAssembly Components and WasmCloud Actors: A Glimpse of the Future(wasmcloud.com)
3 points by brooksmtownsend 4y ago|0 comments