mootoday

10 ms·

31.
by mootoday 1y ago
Full disclaimer: I only scanned the article, but based on the title, SvelteKit does that with a single option "inline". https://svelte.dev/docs/kit/configuration#output
32.
by mootoday 1y ago
Tell me it's early days without telling me it's early days... hi (at) pipestack.dev should work
33.
by mootoday 1y ago
I'm heads down building a workflow pipeline builder that executes Wasm Components as part of individual nodes within the pipeline. Think Zapier or n8n, but you either use existing processing nodes or upload your own code, written of co
34.
by mootoday 1y ago
What I get is isolation, so I can run untrusted customer code as a Wasm component knowing it runs in a secure sandbox. Also, scaling across clouds, edge, on-prem with minimal effort. Another benefit I enjoy now is changing links between com
35.
by mootoday 1y ago
I hadn't really been interested in WebAssembly until I read about the component model and the fact that I can run Wasm components on the server. That led me to wasmCloud[1]. As the article says, Wasm on the server isn't a winner y
36.
by mootoday 1y ago
Wasm Components, deployed on wasmCloud. IMHO, that's the way to go. Instead of hundreds of megabytes or even gigabytes, we're talking kilobytes, sometimes megabytes for each unit of compute. Actually sandboxed environments per com
37.
by mootoday 1y ago
I use ts-rs [1] in my project to generate Typescript definitions. The files are copied to the web app automatically. [1] https://crates.io/crates/ts-rs
38.
by mootoday 1y ago
That was a great intro to clap, thanks for writing it up! I've been building clap CLIs for a while and started to put together a template: https://github.com/mootoday/cli-template . It also includes a crate I devel
39.
by mootoday 1y ago
Why containers when you can have Wasm components on wasmCloud :-)?! https://wasmcloud.com/
40.
by mootoday 1y ago
This is great, lots I learned by looking at your code and the dependencies you use! I started a similar thing, although not as feature-rich as yours. My goal was to follow CLI best practices and add all the boilerplate one needs to build a
41.
Ask HN: Pipelines with WASM Components
2 points by mootoday 1y ago|0 comments
42.
by mootoday 2y ago
Worth noting some are cloud-only whereas others like Jetify's Devbox work locally and in the cloud. I wrote about that years ago and the article is as valid today as it was back then, IMHO. https://mootoday.com/blog&#x2
43.
by mootoday 2y ago
I've used Devbox by Jetify for two years. Never looked back. https://github.com/jetify-com/devbox
44.
by mootoday 2y ago
Leaving this here as it's by the creator of Insomnia: https://yaak.app/
45.
by mootoday 2y ago
Sounds like you're looking for https://yaak.app/ .
46.
by mootoday 2y ago
Did anyone say debugging? I've followed https://debugbetter.com/ for a few weeks and the content has been great!
47.
Migrating a Node.js CLI to Rust(mootoday.com)
1 points by mootoday 2y ago|0 comments
48.
by mootoday 2y ago
No
49.
by mootoday 2y ago
Pretty sure you'd have a more lightweight experience with https://www.jetify.com/devbox . Happy to set it up and demo if you can share (or DM) a repo URL.
50.
My First Rust Crate(mootoday.com)
1 points by mootoday 2y ago|0 comments
51.
by mootoday 2y ago
I hear you, Nix has been nothing but a waste of time for me every time I tried to do anything with it. Devbox abstracts it and the only time I had to do a nix-specific thing was when I needed a flake to install a CLI from a GitHub release.
52.
by mootoday 2y ago
Thank you, TIL about ubi! My brain is now compiling a list of places where this will replace either a shell script or flake for my projects :). Tasks sounds similar process-compose which is bundled into Devbox. I'll have to read up mor
53.
by mootoday 2y ago
I've used Devbox for two years for my projects and any work I've done for my clients. I'm curious what some of the mise features are you like.
54.
by mootoday 2y ago
I read the project's Readme and all I'm left with is "why?". I use Devbox[1] and get access to the entire Nix ecosystem, done. [1] https://github.com/jetify-com/devbox
55.
by mootoday 2y ago
All I can say when I see Homebrew: "I replaced Homebrew with Devbox" [1] [1] https://mootoday.com/blog/i-replaced-homebrew-with-devbox
56.
by mootoday 2y ago
Meta also uses React and we know what mess that introduced to the world...
57.
by mootoday 2y ago
I've worked with remote dev environments for many years, including some time with one of the providers of such a service. It became clear to me that cloud-only is not the way to go, but instead a local-first, cloud-optional approach.
58.
by mootoday 2y ago
I had done the same before I learned about Devbox. It's very lightweight and gets very powerful combined with `git worktree` to work on multiple branches in parallel, each with its own database instance.
59.
by mootoday 2y ago
For me, the key push towards using it as a Homebrew replacement was the fact that I already used Devbox to create isolated dev environments for individual projects I work on. Now I have one tool to manage all dependencies. Other than that,
60.
by mootoday 2y ago
There's an interesting alternative to Homebrew: Devbox It abstracts Nix in a way you don't have to know or learn anything about the Nix language. I wrote a few words on how I use it instead of Homebrew [1]. [1] https://

More ›