superchris
Joined 14 years ago
Karma
37
Submissions
28
Member since
Jun 14
Recent submissions
Comment · 9 months ago
wow this article sure reads like AI slop
Comment · 10 months ago
This thing that can't be measured is up 76%. Eyeroll
Comment · 1 year ago
The only thing surprising about the result was that they found it surprising :)
Comment · 1 year ago
This is great, I think this is perfect use for web components and gives your customers trying to build a fully custom storefront a much better experience. I built something similar for stripe based sites a couple years ago but didn't get too much attention: https://elements.launchscout.com/
Comment · 1 year ago
Really like what I'm seeing so far. It looks a lot like Sprae: https://github.com/dy/sprae one of my favorite things that no one seems to be paying attention to :) I use it on live-templates, which uses Sprae to connect a template to stateful backend in Elixir over Phoenix Channels: https://github.com/launchscout/live-templates
Comment · 1 year ago
This sounds awesome. As a GA pilot and software developer, I can tell you that voice comms and the need to work with them will be around for a long time. Just look at all the feet dragging just to get ADSB adopted. I'd love to find out more and possibly get involved. Are you looking for help?
Comment · 2 years ago
We've definitely experienced chaos when building large React apps. I don't think it's necessarily React's fault (though I'm not particularly a fan), I think the complexity is inherent in managing stage in both a client app and a server app. We've since moved to building apps with Phoenix LiveView and been much more productive. I've also built some libraries to give you the same benefits (single source of state on the server) when serving the front end in Elixir isn't an option: https://github.com/launchscout/live_state.
Comment · 2 years ago
This sounds like a really excellent product, and I really love the description in this post of how you got there. Not working on anything just this minute that needs it, but I will definitely keep an eye out for opportunities.
Comment · 2 years ago
The promise of being able to use any library from any language is really quite compelling, and that's what the WASM component model is about for me. It's pretty sad to say this amount of hate TBH
Comment · 2 years ago
Once again, missing the point of unit testing. Unit testing is about improving the design of the software, and allowing the design to evolve through refactoring (which is effectively impossible without unit testing). E2E or integration tests are for catching bugs
Comment · 2 years ago
Eleventy is pretty great! Highly recommend.
Comment · 2 years ago
The live-template element provides a connected, or "live" template that connects to a stateful backend application provided by Livestate. After connecting to a LiveState channel, it will
- render the initial state - subscribe to state updates and re-render on changes - push events to a Livestate channel which may then compute a new state
If you squint really hard, you can think of it as HTMX meets Elixir ;)
Comment · 3 years ago
It is supported by chromium already and Mozilla has said they'll be working on it
Comment · 3 years ago
Since you mention that state management is an unsolved problem with Web Components, I thought I would share a project that aims to bring a solution: https://github.com/launchscout/live_state. The basic pattern and idea of LiveState is "dispatch events, subscribe to state". The events and state updates are sent over a websocket connection, and the front end and back end libraries are a thin layer over Phoenix Channels. Currently, event handler functions are written in Elixir, but work is underway to allow them to be written in any language that compiles to WebAssembly.