jchrisa
Joined 18 years ago
Karma
4,321
Submissions
1,249
Member since
Dec 10
Recent submissions
Comment · 11 months ago
Damn I just deleted another 29k loc https://github.com/VibesDIY/vibes.diy/pull/635
Code slows you down, always worth cleaning up. Yes, the business case is aligned with both the past bloat, and the current cleanup.
Comment · 11 months ago
I just had a majorly fun time addressing tech debt, deleting about 15k lines-of-code from a codebase that now has ~45k lines of implementation, and 50k lines of tests. This was made possible by moving from a homegrown auth system to Clerk, as well as consolidating some Cloudflare workers, and other basic stuff. Not as fun as creating the tech debt in the first place, but much more satisfying. Open source repo if you like to read this sort of thing: https://github.com/VibesDIY/vibes.diy/pull/582
Comment · 1 year ago
I just vibed up a quick and dirty catalog browser for FedFlix -- thanks IA for making the API so easy to use!
https://unknown-ptarmigan-3137.vibecode.garden
Click the remix button in the bottom right and you can make it your own.
Comment · 1 year ago
The generation is running while you login, so this appreciable decreases wait time from idea to app, because by the time you click through the login, your app is ready. (Vibes DIY CEO here.)
If login takes 30 seconds, and app gen 90, we think this is better for users (but clearly not everyone agrees.) Thanks for the feedback!
Comment · 1 year ago
I haven't posted it here yet b/c it's not show ready, but we have been building this vision -- I like to think of it as an e-bike for the mind.
We had a lot of fun last night with Vibecode Karaoke, where you code an app at the same time as you sing a song.
Comment · 1 year ago
This is very much like Erlang's actor model. The same compute can be run in parallel, or managed via queues. With Erlang's strong support for FFI and process control, I wonder if it's being used as a dispatcher for these sorts of workloads.
Comment · 1 year ago
if there is an ideological bent, or other driving reason -- write it up! make treatise / requirements document for someone else to implement.
Comment · 1 year ago
Some discussion on the repo README: https://news.ycombinator.com/item?id=42383592
Comment · 1 year ago
I'm curious what your environment looks like. We have a bunch of open source options, but standing up a new one is always getting easier.
Comment · 1 year ago
I didn't say enough about the ledger-like aspects above. Some databases have collections, some have tables, Fireproof has ledgers. These are the unit of sharing and access control, and also the unit of provable history.
Comment · 1 year ago
The best starter is the React Tutorial in our docs: https://use-fireproof.com/docs/react-tutorial/
We are updating this example to the latest right now, it shows how team chat can be implemented with database sharing. https://github.com/fireproof-storage/firehouse-chat
This drum machine is pretty forkable as well: https://github.com/fireproof-storage/bloopernet
You can also get started by clicking the "Edit in CodePen" button on our home page, which is just a JavaScript and HTML app.
Comment · 1 year ago
Thanks -- we got hello world with Socket, but there's some interesting open source work we'll need to do to support peers acting as servers and take full advantage of the network.
https://github.com/fireproof-storage/hello-socket-fireproof
If anyone wants to join the effort, the semantics we are talking about are also aligned with WebRTC delivery, so you'd enable a bunch of p2p topologies with your contribution.
Comment · 1 year ago
Here are some apps people have built, for inspiration:
* Bloopernet Drum Machine: https://news.ycombinator.com/item?id=42177005
* Slack style team chat https://firehouse-chat.jchris.partykit.dev/
* PartKit Cloudflare https://blog.partykit.io/posts/fireproof-database-connector
jchris at fireproof.storage