The best Hacker News stories from Show from the past day
Latest posts:
Show HN: I've been making JavaScript sandbox alone for 6 years
Hi HN!
Thanks for your attention to my post.<p>It was a big challenge to run most of Node.js packages in browser, fast moreover. Virtual File system, resolve import/export. I got cold many times, depressions, burned out, yet still alive and finished it.<p>Many guys helped me with an advice. Many users give a lot of positive feedback.
There are 200,000 monthly unique users.<p>I work full time now because of the freemium business model. To be honest - I am happy after many years of hard work.
Show HN: The Poetry Corner – A React Native app to read public domain poems
TLDR - scratched my own itch with an app, added a pro plan and got my first subscribers this week!<p>Last December I started digging into poetry, it was a topic I always thought I liked, but just hadn’t explored very much. I soon discovered that a lot of the poetry sites online had pretty annoying designs, e.g. ads right at the end of the poem, (muting any emotional impact).<p>I also wanted to be able to easily save a list of my favourites to come back to.<p>I decided to build and release a react native app which addressed these needs/issues. It took about 4 weeks during the winter break to release an MVP to the App Store. The backend is using Firebase, which has been superb in allowing me to bootstrap the app quickly.<p>I soon added a poem of the day feature, which forced me into curation (needing to find 365 poems for the year!). I’ve discovered so many amazing poems and poets as a result. One of the things I love about tech is that it can touch so many different domains and industries.<p>Anyway, fast forward six months of continuous development, adding features and refining the design, lots of late nights. I finally had enough of a feature set to demarcate some out to a paid plan with a free trial. And the first users have actually started subscribing!<p>I’ll soon be ramping up ads, currently just on the App Store Search, but soon with Google and Instagram. I’ll be seeing if I can spend x amount on ads to net a return in subscriptions. If so, I’ll be scaling it as fast as the budget will allow.<p>For the instagram ads, I’ll be marketing the poetry app with a mindfulness twist. Some people have already talked about this connection online, and I’ve personally experienced a deeper bond with nature and awareness of my own feelings as a result of reading so many poems.<p>So that’s where the app is now, and where I have in mind to take it. It’s been super fun working on it and any feedback is welcome!
BMList – A list of big pre-trained models (GPT-3, DALL-E2...)
Show HN: P2PCF – Low cost, low effort WebRTC signalling using Cloudflare workers
Show HN: P2PCF – Low cost, low effort WebRTC signalling using Cloudflare workers
Show HN: Distributed SQLite on FoundationDB
Hello HN! I'm building mvsqlite, a distributed variant of SQLite with MVCC transactions, that runs on FoundationDB. It is a drop-in replacement that just needs an `LD_PRELOAD` for existing applications using SQLite.<p>I made this because Blueboat (<a href="https://github.com/losfair/blueboat" rel="nofollow">https://github.com/losfair/blueboat</a>) needs a native SQL interface to persistent data. Apparently, just providing a transactional key-value store isn’t enough - it is more easy and efficient to build complex business logic on an SQL database, and it seems necessary to bring a self-hostable distributed SQL DB onto the platform. Since FoundationDB is Blueboat’s only stateful external dependency, I decided to build the SQL capabilities on top of it.<p>At its core, mvsqlite’s storage engine, mvstore, is a multi-version page store built on FoundationDB. It addresses the duration and size limits (5 secs, 10 MB) of FDB transactions, by handling multi-versioning itself. Pages are fully versioned, so they are always snapshot-readable in the future. An SQLite transaction fetches the read version during `BEGIN TRANSACTION`, and this version is used as the per-page range scan upper bound in future page read requests.<p>For writes, pages are first written to a content-addressed store keyed by the page's hash. At commit, hashes of each written page in the SQLite transaction is written to the page index in a single FDB transaction to preserve atomicity. With 8K pages and ~60B per key-value entry in the page index, each SQLite transaction can be as large as 1.3 GB (compared to FDB's native txn size limit of 10 MB).<p>mvsqlite is not yet "production-ready", since it hasn’t received enough testing, and I may still have a few changes to make to the on-disk format. But please ask here if you have any questions!
Show HN: Distributed SQLite on FoundationDB
Hello HN! I'm building mvsqlite, a distributed variant of SQLite with MVCC transactions, that runs on FoundationDB. It is a drop-in replacement that just needs an `LD_PRELOAD` for existing applications using SQLite.<p>I made this because Blueboat (<a href="https://github.com/losfair/blueboat" rel="nofollow">https://github.com/losfair/blueboat</a>) needs a native SQL interface to persistent data. Apparently, just providing a transactional key-value store isn’t enough - it is more easy and efficient to build complex business logic on an SQL database, and it seems necessary to bring a self-hostable distributed SQL DB onto the platform. Since FoundationDB is Blueboat’s only stateful external dependency, I decided to build the SQL capabilities on top of it.<p>At its core, mvsqlite’s storage engine, mvstore, is a multi-version page store built on FoundationDB. It addresses the duration and size limits (5 secs, 10 MB) of FDB transactions, by handling multi-versioning itself. Pages are fully versioned, so they are always snapshot-readable in the future. An SQLite transaction fetches the read version during `BEGIN TRANSACTION`, and this version is used as the per-page range scan upper bound in future page read requests.<p>For writes, pages are first written to a content-addressed store keyed by the page's hash. At commit, hashes of each written page in the SQLite transaction is written to the page index in a single FDB transaction to preserve atomicity. With 8K pages and ~60B per key-value entry in the page index, each SQLite transaction can be as large as 1.3 GB (compared to FDB's native txn size limit of 10 MB).<p>mvsqlite is not yet "production-ready", since it hasn’t received enough testing, and I may still have a few changes to make to the on-disk format. But please ask here if you have any questions!
Show HN: Distributed SQLite on FoundationDB
Hello HN! I'm building mvsqlite, a distributed variant of SQLite with MVCC transactions, that runs on FoundationDB. It is a drop-in replacement that just needs an `LD_PRELOAD` for existing applications using SQLite.<p>I made this because Blueboat (<a href="https://github.com/losfair/blueboat" rel="nofollow">https://github.com/losfair/blueboat</a>) needs a native SQL interface to persistent data. Apparently, just providing a transactional key-value store isn’t enough - it is more easy and efficient to build complex business logic on an SQL database, and it seems necessary to bring a self-hostable distributed SQL DB onto the platform. Since FoundationDB is Blueboat’s only stateful external dependency, I decided to build the SQL capabilities on top of it.<p>At its core, mvsqlite’s storage engine, mvstore, is a multi-version page store built on FoundationDB. It addresses the duration and size limits (5 secs, 10 MB) of FDB transactions, by handling multi-versioning itself. Pages are fully versioned, so they are always snapshot-readable in the future. An SQLite transaction fetches the read version during `BEGIN TRANSACTION`, and this version is used as the per-page range scan upper bound in future page read requests.<p>For writes, pages are first written to a content-addressed store keyed by the page's hash. At commit, hashes of each written page in the SQLite transaction is written to the page index in a single FDB transaction to preserve atomicity. With 8K pages and ~60B per key-value entry in the page index, each SQLite transaction can be as large as 1.3 GB (compared to FDB's native txn size limit of 10 MB).<p>mvsqlite is not yet "production-ready", since it hasn’t received enough testing, and I may still have a few changes to make to the on-disk format. But please ask here if you have any questions!
Show HN: SDWM – Simple Dynamic Window Manager for Windows
Show HN: A simple, pretty alternative to strace written in Rust
Show HN: Truss – Serve any ML model without boilerplate code
Show HN: Truss – Serve any ML model without boilerplate code
Show HN: Chunk – Code sandbox for back-end devs
Chunk co-founder here. We spent the last 2 weeks building this to scratch our own itch:<p>As developers, we often have problems that could be solved just by running a few lines of code.
Sometimes, running this code on your local machine is fine.
But other time, the code need to run automatically reacting to external events or to run continuously, which means, it needs to run on a server somewhere.<p>So now, you have to find a cloud provider, to package or build the code and finally to deploy it. All of that for what could be literally be 4 lines of code.<p>We couldn’t find an easier way to do this, so we built it.<p>Chunk is an all in one web editor (think of the codesandbox experience) that allows you to write, deploy and run a piece of code in the cloud from a variety of triggers: HTTP, WebHook, manual or scheduled (cron).<p>No setup, no build, no deploy. Chunk makes you go from idea to code running in the cloud in seconds.<p>Let me know what you guys think!
Show HN: Chunk – Code sandbox for back-end devs
Chunk co-founder here. We spent the last 2 weeks building this to scratch our own itch:<p>As developers, we often have problems that could be solved just by running a few lines of code.
Sometimes, running this code on your local machine is fine.
But other time, the code need to run automatically reacting to external events or to run continuously, which means, it needs to run on a server somewhere.<p>So now, you have to find a cloud provider, to package or build the code and finally to deploy it. All of that for what could be literally be 4 lines of code.<p>We couldn’t find an easier way to do this, so we built it.<p>Chunk is an all in one web editor (think of the codesandbox experience) that allows you to write, deploy and run a piece of code in the cloud from a variety of triggers: HTTP, WebHook, manual or scheduled (cron).<p>No setup, no build, no deploy. Chunk makes you go from idea to code running in the cloud in seconds.<p>Let me know what you guys think!
Show HN: Chunk – Code sandbox for back-end devs
Chunk co-founder here. We spent the last 2 weeks building this to scratch our own itch:<p>As developers, we often have problems that could be solved just by running a few lines of code.
Sometimes, running this code on your local machine is fine.
But other time, the code need to run automatically reacting to external events or to run continuously, which means, it needs to run on a server somewhere.<p>So now, you have to find a cloud provider, to package or build the code and finally to deploy it. All of that for what could be literally be 4 lines of code.<p>We couldn’t find an easier way to do this, so we built it.<p>Chunk is an all in one web editor (think of the codesandbox experience) that allows you to write, deploy and run a piece of code in the cloud from a variety of triggers: HTTP, WebHook, manual or scheduled (cron).<p>No setup, no build, no deploy. Chunk makes you go from idea to code running in the cloud in seconds.<p>Let me know what you guys think!
Show HN: Chunk – Code sandbox for back-end devs
Chunk co-founder here. We spent the last 2 weeks building this to scratch our own itch:<p>As developers, we often have problems that could be solved just by running a few lines of code.
Sometimes, running this code on your local machine is fine.
But other time, the code need to run automatically reacting to external events or to run continuously, which means, it needs to run on a server somewhere.<p>So now, you have to find a cloud provider, to package or build the code and finally to deploy it. All of that for what could be literally be 4 lines of code.<p>We couldn’t find an easier way to do this, so we built it.<p>Chunk is an all in one web editor (think of the codesandbox experience) that allows you to write, deploy and run a piece of code in the cloud from a variety of triggers: HTTP, WebHook, manual or scheduled (cron).<p>No setup, no build, no deploy. Chunk makes you go from idea to code running in the cloud in seconds.<p>Let me know what you guys think!
Show HN: Doxx Me – See how doxxable your phone number is
I built this tool that checks publicly available data against your phone number. I was surprised how one my numbers (which I text and sign up for services with) has a lot of information attached to it including my full name, all previous addresses, relatives, emails, and more.
Show HN: Doxx Me – See how doxxable your phone number is
I built this tool that checks publicly available data against your phone number. I was surprised how one my numbers (which I text and sign up for services with) has a lot of information attached to it including my full name, all previous addresses, relatives, emails, and more.
Show HN: Doxx Me – See how doxxable your phone number is
I built this tool that checks publicly available data against your phone number. I was surprised how one my numbers (which I text and sign up for services with) has a lot of information attached to it including my full name, all previous addresses, relatives, emails, and more.
Show HN: Marple – Interactive time series visualization for engineers
Hi HN, excited to share the project I have been working on for the past two years.
Marple was created by engineers for engineers. Marple helps them organize and analyze their sensor data in a more user-friendly way.<p>We’ve all been there: measurement data from an experiment or test needs to be analyzed but the only thing you have is a few data files flying around. You do not have a clue how to open or read the data. So what you do next is open your Python/Matlab/Jupyter Notebook/… and start coding in order to make some sense of the data. We didn’t like that process, so we started Marple to solve this issue.<p>Engineers tend to log data at frequencies from 1Hz to 10kHz and usually log hundreds of sensors at the same time. Data sets usually contain millions of data points. In order to make our web-based data visualization responsive, we had some technical challenges to tackle. We developed our own visualization engine based on PostgreSQL that is able to visualize millions of data points pretty much instantly. This allows us to create an interactive visualization environment which is perfect for data exploration, even for large data sets!<p>This is the second time we show Marple to HackerNews, but since then we made some big steps. We made a pivot to a cloud product and now offer a free version of Marple. Feel free to head over to our website and give it a go. Let us know what you think of it!