live-interface VS exhibitor

If you've got some nodejs, Ruby or Python projects and you want to keep them around for posterity then I recommend thinking how you can package them up so they can be safely archived. You could use docker or a virtual machine image.

In my editor project ( screncast https://github.com/samsquire/live-interface/blob/master/scre... )

In components written in Nodejs, Ruby and Python and they're all in disrepair because I failed to pin dependencies.

Also recommend taking lots of screenshots.

I created a text editor that was meant to be programmable like a spreadsheet but interactive like a IPython notebook.

There's screenshots here:

https://github.com/samsquire/liveinterface

The code is Angular 1 legacy codebase.

https://github.com/samsquire/live-interface

There's a screencast here https://github.com/samsquire/live-interface/blob/master/scre...

It's not buildable at this time due to dependencies...

At one point I tried creating what is Notion/Obsidian style system in 2013. I called it "living documents".

here's one of the last surviving screenshots of living documents version 1.

https://github.com/samsquire/interface-experiments/blob/mast...

The system accepted RDF N3 triples and it queried Jena Fuseki database to render graphs with d3. You could introduce facts into the system with the three boxes at the top. if you changed them, they would autocomplete and change the graph view. You could insert references or links into the document by typing them.

I have the code trapped in a JSBIN SQLite file. It's somewhere in here https://github.com/samsquire/jsbin It uses KnockoutJS.

Living documents v2 has a screen cast of it here https://github.com/samsquire/live-interface/blob/master/scre...

TL;DR: A React front-end component workshop, a simple version of Storybook.

So around 5 months ago, I needed a tool to preview front-end (React) components whilst I create them for a personal project of mine. There were two options: Storybook or Ladle.

Storybook is the tool everybody knows. I've used it before quite a lot. It's very big, full-fat, supports loads of use-cases, etc.

Ladle comes out of Uber. It's very small, lean, and doesn't support that much. After trying it out for a while, it just gives me a feeling like it's a 20% project to learn some new tech.

So I realised that I wanted something kind of in the middle. Something that's a bit more customizable than Ladle, but something much simpler and less intrusive than Storybook.

This led me to create Exhibitor (https://github.com/samhuk/exhibitor) (https://demo.exhibitor.dev).

I worked on it on-and-off for a couple months, and it ended up being something that I'm quite proud of. It's not perfect, and supports only a fraction of what Storybook does, however for a tool made by 1 engineer vs the 20+ for Storybook, I'm quite happy about it!

Exhibitor, a snappy & delightful React component workshop, is GA. My aim is for Exhibitor to be an extremely fast, easy to use, and delightful tool for creating front-end component libraries.

It's been around 2 months since my last mention and quite a tonne has changed.

Wiki: https://github.com/samhuk/exhibitor/wiki

Looks interesting. Coincidentally, I've just completed the bulk of work on a distributed Websocket network system to synchronize certain bits of state between multiple clients for my own kind of Storybook tool [0]. How interesting!

This kind of tool is exactly what I would have needed, instead of the approach I've taken which is a bit kludgy, grass-roots, novice-like, etc.

Good work :)

[0] https://github.com/samhuk/exhibitor/pull/22

I was a bit deflated when my submission about https://github.com/samhuk/exhibitor fell through the HN floor-boards.

Think Storybook but simpler, faster, better Typescript support, and uses esbuild by default.

...Is the aim. I'm the sole lead dev working on it at the moment up against the ~10-20 strong team who built most of Storybook, so it's a long road ahead, but it's growing into something I'm quite proud of and happy about.