exhibitor
ratarmount
exhibitor | ratarmount | |
---|---|---|
6 | 10 | |
8 | 637 | |
- | - | |
6.8 | 9.1 | |
about 1 year ago | 15 days ago | |
TypeScript | Python | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
exhibitor
-
Ask HN: Most interesting tech you built for just yourself?
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!
-
Show HN: Exhibitor – Snappy and delightful React component workshop
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
-
Show HN: DriftDB is an open source WebSocket back end for real-time apps
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
-
Ask HN: What have you created that deserves a second chance on HN?
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.
- Show HN: Exhibitor – Snappy, no-fuss, delightful React component workshop
ratarmount
- Ratarmount: Access large archives as a filesystem efficiently
- Show HN: Rapidgzip – Parallel Gzip Decompressing with 10 GB/S
- Ratarmount: Random Access Tar Mount
-
Ask HN: Most interesting tech you built for just yourself?
This is basically the same reason why I started with ratarmount (https://github.com/mxmlnkn/ratarmount) but the focus was more on runtime performance and random access and as the name suggests it started out with access to recursive tar archives. The current version should also work for your use case with recursive zips.
-
Looking for advice uploading data while at uni. I need to split the data i need to upload to carry it with me
As an added complication this would need to work under windows (i need onenote and that's win only :/ ) ; this alone makes the majority of solutions that i came up with impossible. One way could've been splitting the data onto various tar files and then mounting those with rartarmount but...linux only :( .
-
How Much Faster Is Making a Tar Archive Without Gzip?
Pragzip actually decompress in parallel and also access at random. I did a Show HN here: https://news.ycombinator.com/item?id=32366959
indexed_gzip https://github.com/pauldmccarthy/indexed_gzip can also do random access but is not parallel.
Both have to do a linear scan first though. The implementations however can do the linear scan on-demand, i.e., they scan only as far as needed.
bzip2 works very well with this approach. xz only works with this approach when compressed with multiple blocks. Similar is true for zstd.
For zstd, there also exists a seekable variant, which stores the block index at the end as metadata to avoid the linear scan. indexed_zstd offers random access to those files https://github.com/martinellimarco/indexed_zstd
I wrote pragzip and also combined all of the other random access compression backends in ratarmount to offer random access to TAR files that is magnitudes faster than archivemount: https://github.com/mxmlnkn/ratarmount
-
Ratarmount – Fast transparent access to archives through FUSE
Or via the experimental AppImage I created this week:
wget -O ratarmount 'https://github.com/mxmlnkn/ratarmount/releases/download/v0.10.0/ratarmount-manylinux2014_x86_64.AppImage'
-
Hop: 25x faster than unzip and 10x faster than tar at reading individual files
I've recently been looking into this same issue because I analyse a lot of data like sosreports or other tar/compressed data from customer systems. Currently I untar these onto my zfs filesystem which works out OK because it has zstd compression enabled but I end up decompressing and recompressing which is quite expensive as often the files are GBs or more compressed.
But I've started using a tool called "ratarmount" (https://github.com/mxmlnkn/ratarmount) which creates an index once (and something I could automate our upload system to generate in advance, but you can also just process it lcoally) and then lets you fuse mount the file. This works pretty great with the only exception that I can't create scratch files inside the directory layout which in the past I'd wanted to do.
I was surprised how hard a problem to solve it is to get a bundle file format that is indexable and compressed with a good and fast compression algorithm which mostly boils down to zstd at this point.
While it works quite well, especially with gzip and bzip2, sadly the zstd and xz (and some other compression formats) don't allow for decompressing only parts of a file by default, even though it's possible the default tools aren't doing it. The nitty gritty details are summarised here:
-
Is there a way to accelerate extracting .tar contents?
Well, you could try to skip extraction and access the tar archive using ratarmount, and stack overlayfs on top to allow writing, but that will have an impact on compilation time.
What are some alternatives?
epub2tts - Turn an epub or text file into an audiobook
tarindexer - python module for indexing tar files for fast access
MLVPN - Multi-link VPN (ADSL/SDSL/xDSL/Network aggregation / bonding)
asar - Simple extensive tar-like archive format with indexing
scheme-for-max - Max/MSP external for scripting and live coding Max with s7 Scheme Lisp
PyFilesystem2 - Python's Filesystem abstraction layer
mqtt-to-kafka-bridge - Move your messages from MQTT to Apache Kafka in real-time :rocket:
pixz - Parallel, indexed xz compressor
brethap
InstaPy - 📷 Instagram Bot - Tool for automated Instagram interactions
factorio-init - Factorio init script
icoextract - Extract icons from Windows PE files (.exe/.dll)