ndyg
Joined 12 years ago
Karma
52
Submissions
38
Member since
May 29
Recent submissions
Comment · 2 months ago
I'm a dual Australian / Canadian citizen. I'm disappointed Australia hasn't been more active in their support for Canada. Commonwealth countries should be sticking together.
Comment · 4 months ago
if you like bash web apps, you'll love https://github.com/cablehead/http-sh
Comment · 7 months ago
Something I find myself saying a lot, Nushell is a better `jq` than `jq`
Comment · 7 months ago
The original sin wasn't reactivity. It was putting state in the wrong place. Making the client state heavy. It's been downhill since then. Now you need to duplicate state handling between your frontend language and your backend language. Which leads to "isomorphic" backends seeming like a good idea.
Comment · 10 months ago
I'm using fjall v2 in the Rust event streaming store, cross.stream (`xs`) https://github.com/cablehead/xs
`xs` is for personal scale so fjall is fairly overkill performance-wise. marvin_j97's benchmark work and deep dives into different database systems is incredible though. Looking forward to updating to v3.
Comment · 10 months ago
Comment · 1 year ago
If you like lo-fi ways to attach cli commands to http end-points, you may also like:
- https://github.com/cablehead/http-nu or for POSIX - https://github.com/cablehead/http-sh
Comment · 1 year ago
astroturf campaign?
Comment · 1 year ago
My understanding is Turbo is more aligned with htmx. Common practice in Turbo are generally patterns of last resort in Datastar.
e.g. Datastar prescribes a single long lived SSE endpoint that owns the state for the currently connected user's view of the world / app, while common practice in Turbo is to have many small endpoints that return a fragment of html when requested by the client.
Comment · 1 year ago
The preferred pattern addresses your concern about scattered logic: a single long-lived SSE endpoint that "owns" the user's view of the app. That endpoint updates their field of view as appropriate - very much inspired by game dev's immediate mode rendering.
I've a tutorial that demonstrates this with Nushell as the backend: https://datastar-todomvc.cross.stream
An interesting characteristic of Datastar: it's very opinionated about the shape of your backend but extremely unopinionated about how you implement that shape.
Comment · 1 year ago
I'm curious, what do you think is missing from Caddy that has you looking for something new?
Comment · 1 year ago
I maintain a Rust-based CLI HTTP server that embeds Nushell. It’s a handy little Swiss-army knife that’s replaced Nginx and Caddy for my personal projects.
You can serve a folder of static assets like this:
http-nu :3021 '{|req| .static "www" $req.path}'
Comment · 1 year ago
The approach you describe requires host to have an open ssh port you can access. quic + nat hole punching works around this.
Comment · 1 year ago
The friction Dave describes where changing one param effects all the other params in an animation brought to mind this section of an old Bret Victor talk: https://www.youtube.com/watch?v=a-OyoVcbwWE&t=716s
I make: https://stacks.cross.stream
I'd like to garden: https://ndyg.co
Tinkering: https://github.com/cablehead
Fascinated by cosy communities and good faith communication as tools, aiming to explore life's intricacies and uplift everyone's journey.