The best Hacker News stories from Show from the past day
Latest posts:
Show HN: Hydra (YC W22) – Serverless Analytics on Postgres
Hi HN, Hydra cofounders (Joe and JD) here (<a href="https://www.hydra.so/">https://www.hydra.so/</a>)! We enable realtime analytics on Postgres without requiring an external analytics database.<p>Traditionally, this was unfeasible: Postgres is a rowstore database that’s 1000X slower at analytical processing than a columnstore database.<p>(A quick refresher for anyone interested: A rowstore means table rows are stored sequentially, making it efficient at inserting / updating a record, but inefficient at filtering and aggregating data. At most businesses, analytical reporting scans large volumes of events, traces, time-series data. As the volume grows, the inefficiency of the rowstore compounds: i.e. it's not scalable for analytics. In contrast, a columnstore stores all the values of each column in sequence.)<p>For decades, it was a requirement for businesses to manage these differences between the row and columnstore’s relative strengths, by maintaining two separate systems. This led to large gaps in both functionality and syntax, and background knowledge of engineers. For example, here are the gaps between Redshift (a popular columnstore) and Postgres (rowstore) features: (<a href="https://docs.aws.amazon.com/redshift/latest/dg/c_unsupported-postgresql-features.html" rel="nofollow">https://docs.aws.amazon.com/redshift/latest/dg/c_unsupported...</a>).<p>We think there’s a better, simpler way: unify the rowstore and columnstore – keep the data in one place, stop the costs and hassle of managing an external analytics database. With Hydra, events, traces, time-series data, user sessions, clickstream, IOT telemetry, etc. are now accessible as a columnstore right alongside my standard rowstore tables.<p>Our solution: Hydra separates compute from storage to bring the analytics columnstore with serverless processing and automatic caching to your postgres database.<p>The term "serverless" can be a bit confusing, because a server always exists, but it means compute is ephemeral and spun up and down automatically. The database automatically provisions and isolates dedicated compute resources for each query process. Serverless is different from managed compute, where the user explicitly chooses to allocate and scale CPU and memory continuously, and potentially overpay during idle time.<p>How is serverless useful? It's important that every analytics query has its own resources per process. The major hurdles with running analytics on Postgres is 1) Rowstore performance 2) Resource contention. #2 is very often overlooked - but in practice, when analytics queries are run they tend to hog resources (RAM and CPU) from Postgres transactional work. So, a slightly expensive analytics query has the ability to slow down the entire database: that's why serverless is important: it guarantees the expensive queries are isolated and run on dedicated database resources per process.<p>why is hydra so fast at analytics? (<a href="https://tinyurl.com/hydraDBMS" rel="nofollow">https://tinyurl.com/hydraDBMS</a>) 1) columnstore by default 2) metadata for efficient file-skipping and retrieval 3) parallel, vectorized execution 4) automatic caching<p>what’s the killer feature? hydra can quickly join columnstore tables with standard row tables within postgres with direct sql.<p>example: “segment events as a table.” Instead of dumping segment event data into a s3 bucket or external analytics database, use hydra to store and join events (clicks, signups, purchases) with user profile data within postgres. know your users in realtime: “what events predict churn?” or “which user will likely convert?” is immediately actionable.<p>Thanks for reading! We would love to hear your feedback and if you'd like to try Hydra now, we offer a $300 credit and 14-days free per account. We're excited to see how bringing the columnstore and rowstore side-by-side can help your project.
Show HN: Hydra (YC W22) – Serverless Analytics on Postgres
Hi HN, Hydra cofounders (Joe and JD) here (<a href="https://www.hydra.so/">https://www.hydra.so/</a>)! We enable realtime analytics on Postgres without requiring an external analytics database.<p>Traditionally, this was unfeasible: Postgres is a rowstore database that’s 1000X slower at analytical processing than a columnstore database.<p>(A quick refresher for anyone interested: A rowstore means table rows are stored sequentially, making it efficient at inserting / updating a record, but inefficient at filtering and aggregating data. At most businesses, analytical reporting scans large volumes of events, traces, time-series data. As the volume grows, the inefficiency of the rowstore compounds: i.e. it's not scalable for analytics. In contrast, a columnstore stores all the values of each column in sequence.)<p>For decades, it was a requirement for businesses to manage these differences between the row and columnstore’s relative strengths, by maintaining two separate systems. This led to large gaps in both functionality and syntax, and background knowledge of engineers. For example, here are the gaps between Redshift (a popular columnstore) and Postgres (rowstore) features: (<a href="https://docs.aws.amazon.com/redshift/latest/dg/c_unsupported-postgresql-features.html" rel="nofollow">https://docs.aws.amazon.com/redshift/latest/dg/c_unsupported...</a>).<p>We think there’s a better, simpler way: unify the rowstore and columnstore – keep the data in one place, stop the costs and hassle of managing an external analytics database. With Hydra, events, traces, time-series data, user sessions, clickstream, IOT telemetry, etc. are now accessible as a columnstore right alongside my standard rowstore tables.<p>Our solution: Hydra separates compute from storage to bring the analytics columnstore with serverless processing and automatic caching to your postgres database.<p>The term "serverless" can be a bit confusing, because a server always exists, but it means compute is ephemeral and spun up and down automatically. The database automatically provisions and isolates dedicated compute resources for each query process. Serverless is different from managed compute, where the user explicitly chooses to allocate and scale CPU and memory continuously, and potentially overpay during idle time.<p>How is serverless useful? It's important that every analytics query has its own resources per process. The major hurdles with running analytics on Postgres is 1) Rowstore performance 2) Resource contention. #2 is very often overlooked - but in practice, when analytics queries are run they tend to hog resources (RAM and CPU) from Postgres transactional work. So, a slightly expensive analytics query has the ability to slow down the entire database: that's why serverless is important: it guarantees the expensive queries are isolated and run on dedicated database resources per process.<p>why is hydra so fast at analytics? (<a href="https://tinyurl.com/hydraDBMS" rel="nofollow">https://tinyurl.com/hydraDBMS</a>) 1) columnstore by default 2) metadata for efficient file-skipping and retrieval 3) parallel, vectorized execution 4) automatic caching<p>what’s the killer feature? hydra can quickly join columnstore tables with standard row tables within postgres with direct sql.<p>example: “segment events as a table.” Instead of dumping segment event data into a s3 bucket or external analytics database, use hydra to store and join events (clicks, signups, purchases) with user profile data within postgres. know your users in realtime: “what events predict churn?” or “which user will likely convert?” is immediately actionable.<p>Thanks for reading! We would love to hear your feedback and if you'd like to try Hydra now, we offer a $300 credit and 14-days free per account. We're excited to see how bringing the columnstore and rowstore side-by-side can help your project.
Show HN: A backend agnostic Ruby framework for building reactive desktop apps
For a year or two I've been building a UI library with the aim of making desktop applications fun and easy to write.<p>It is currently written in C/Ruby and uses a custom tree sitter grammar to describe templates.<p>Features include: composable UI components, template directives, event and prop handling, slots, styles and automation capabilities baked in.<p>One of the goals of the project is privileging easy to write custom components via a drawing API over providing a fixed set of components.<p>At the time of this writing it should install on Windows, Mac, and Linux, but sometimes it is hard to test the install on all platforms.<p>I'd love to hear any feedback or suggestions on the project. It is still in an early stage, but it would be great to hear thoughts.<p>Docs are here: <a href="https://hokusai.skinnyjames.net/" rel="nofollow">https://hokusai.skinnyjames.net/</a>
Repo is here: <a href="https://codeberg.org/skinnyjames/hokusai" rel="nofollow">https://codeberg.org/skinnyjames/hokusai</a><p>Licensed under the PPL
Show HN: A backend agnostic Ruby framework for building reactive desktop apps
For a year or two I've been building a UI library with the aim of making desktop applications fun and easy to write.<p>It is currently written in C/Ruby and uses a custom tree sitter grammar to describe templates.<p>Features include: composable UI components, template directives, event and prop handling, slots, styles and automation capabilities baked in.<p>One of the goals of the project is privileging easy to write custom components via a drawing API over providing a fixed set of components.<p>At the time of this writing it should install on Windows, Mac, and Linux, but sometimes it is hard to test the install on all platforms.<p>I'd love to hear any feedback or suggestions on the project. It is still in an early stage, but it would be great to hear thoughts.<p>Docs are here: <a href="https://hokusai.skinnyjames.net/" rel="nofollow">https://hokusai.skinnyjames.net/</a>
Repo is here: <a href="https://codeberg.org/skinnyjames/hokusai" rel="nofollow">https://codeberg.org/skinnyjames/hokusai</a><p>Licensed under the PPL
Show HN: A backend agnostic Ruby framework for building reactive desktop apps
For a year or two I've been building a UI library with the aim of making desktop applications fun and easy to write.<p>It is currently written in C/Ruby and uses a custom tree sitter grammar to describe templates.<p>Features include: composable UI components, template directives, event and prop handling, slots, styles and automation capabilities baked in.<p>One of the goals of the project is privileging easy to write custom components via a drawing API over providing a fixed set of components.<p>At the time of this writing it should install on Windows, Mac, and Linux, but sometimes it is hard to test the install on all platforms.<p>I'd love to hear any feedback or suggestions on the project. It is still in an early stage, but it would be great to hear thoughts.<p>Docs are here: <a href="https://hokusai.skinnyjames.net/" rel="nofollow">https://hokusai.skinnyjames.net/</a>
Repo is here: <a href="https://codeberg.org/skinnyjames/hokusai" rel="nofollow">https://codeberg.org/skinnyjames/hokusai</a><p>Licensed under the PPL
Show HN: Oliphaunt – A native Mastodon client for macOS
I’ve been building Oliphaunt, a native Mastodon client for macOS, as a solo project — designed to be fast, lightweight and feel right at home on the Mac. It’s not built with Catalyst or Electron framework.<p>Key features:<p>• Native macOS UI using AppKit with some SwiftUI integration (not a web wrapper)<p>• Core Data for local caching<p>• Responsive, keyboard-friendly interface<p>• UX tailored for desktop-class Mac computers<p>• Supports multiple accounts, cross-instance timelines and search<p>You can try it via TestFlight (macOS 14+ Sonoma):
<a href="https://testflight.apple.com/join/Epq1P3Cw" rel="nofollow">https://testflight.apple.com/join/Epq1P3Cw</a><p>Feedback is welcome here, on GitHub, or via TestFlight:
<a href="https://github.com/anosidium/Oliphaunt-Feedback-And-Support">https://github.com/anosidium/Oliphaunt-Feedback-And-Support</a>
Show HN: Oliphaunt – A native Mastodon client for macOS
I’ve been building Oliphaunt, a native Mastodon client for macOS, as a solo project — designed to be fast, lightweight and feel right at home on the Mac. It’s not built with Catalyst or Electron framework.<p>Key features:<p>• Native macOS UI using AppKit with some SwiftUI integration (not a web wrapper)<p>• Core Data for local caching<p>• Responsive, keyboard-friendly interface<p>• UX tailored for desktop-class Mac computers<p>• Supports multiple accounts, cross-instance timelines and search<p>You can try it via TestFlight (macOS 14+ Sonoma):
<a href="https://testflight.apple.com/join/Epq1P3Cw" rel="nofollow">https://testflight.apple.com/join/Epq1P3Cw</a><p>Feedback is welcome here, on GitHub, or via TestFlight:
<a href="https://github.com/anosidium/Oliphaunt-Feedback-And-Support">https://github.com/anosidium/Oliphaunt-Feedback-And-Support</a>
Show HN: Oliphaunt – A native Mastodon client for macOS
I’ve been building Oliphaunt, a native Mastodon client for macOS, as a solo project — designed to be fast, lightweight and feel right at home on the Mac. It’s not built with Catalyst or Electron framework.<p>Key features:<p>• Native macOS UI using AppKit with some SwiftUI integration (not a web wrapper)<p>• Core Data for local caching<p>• Responsive, keyboard-friendly interface<p>• UX tailored for desktop-class Mac computers<p>• Supports multiple accounts, cross-instance timelines and search<p>You can try it via TestFlight (macOS 14+ Sonoma):
<a href="https://testflight.apple.com/join/Epq1P3Cw" rel="nofollow">https://testflight.apple.com/join/Epq1P3Cw</a><p>Feedback is welcome here, on GitHub, or via TestFlight:
<a href="https://github.com/anosidium/Oliphaunt-Feedback-And-Support">https://github.com/anosidium/Oliphaunt-Feedback-And-Support</a>
Show HN: Oliphaunt – A native Mastodon client for macOS
I’ve been building Oliphaunt, a native Mastodon client for macOS, as a solo project — designed to be fast, lightweight and feel right at home on the Mac. It’s not built with Catalyst or Electron framework.<p>Key features:<p>• Native macOS UI using AppKit with some SwiftUI integration (not a web wrapper)<p>• Core Data for local caching<p>• Responsive, keyboard-friendly interface<p>• UX tailored for desktop-class Mac computers<p>• Supports multiple accounts, cross-instance timelines and search<p>You can try it via TestFlight (macOS 14+ Sonoma):
<a href="https://testflight.apple.com/join/Epq1P3Cw" rel="nofollow">https://testflight.apple.com/join/Epq1P3Cw</a><p>Feedback is welcome here, on GitHub, or via TestFlight:
<a href="https://github.com/anosidium/Oliphaunt-Feedback-And-Support">https://github.com/anosidium/Oliphaunt-Feedback-And-Support</a>
Show HN: Hyper – Standards-first React alternative
Author here. This is an attempt to simplify frontend development:<p>1. Standards first: User interfaces should be assembled with HTML, styled with CSS, and enhanced with JavaScript.<p>2. Less abstractions: UI composition should be easy and require as few idioms and abstractions as possible, both on client and server.<p>3. Design Systems: Design should be a separate subsystem, easily accessible for developers who care about and understand design.<p>4. Scalability: Complex UIs should retain simplicity as the application grows.<p>Eager to hear your thoughts!
Show HN: Hyper – Standards-first React alternative
Author here. This is an attempt to simplify frontend development:<p>1. Standards first: User interfaces should be assembled with HTML, styled with CSS, and enhanced with JavaScript.<p>2. Less abstractions: UI composition should be easy and require as few idioms and abstractions as possible, both on client and server.<p>3. Design Systems: Design should be a separate subsystem, easily accessible for developers who care about and understand design.<p>4. Scalability: Complex UIs should retain simplicity as the application grows.<p>Eager to hear your thoughts!
Show HN: Hyper – Standards-first React alternative
Author here. This is an attempt to simplify frontend development:<p>1. Standards first: User interfaces should be assembled with HTML, styled with CSS, and enhanced with JavaScript.<p>2. Less abstractions: UI composition should be easy and require as few idioms and abstractions as possible, both on client and server.<p>3. Design Systems: Design should be a separate subsystem, easily accessible for developers who care about and understand design.<p>4. Scalability: Complex UIs should retain simplicity as the application grows.<p>Eager to hear your thoughts!
Show HN: Aberdeen – An elegant approach to reactive UIs
Yes, another reactive UI framework for JavaScript. Bear with me, please... :-)<p>I 'invented' the concept for this back in 2011, and it was used (as a proprietary lib) in various startups. Even though <i>many</i> similar open source libs have been released since, and boy have I tried a lot of them, none have been able to capture the elegance and DX of what we had back then. I might be biased though. :-)<p>So I started creating a cleaned-up, modern, TypeScript, open source implementation for the concept about five years ago. After many iterations, working on the project on and off, I'm finally happy with its API and the developer experience it offers. I'm calling it 1.0!<p>The concept: It uses many small, anonymous functions for emitting DOM elements, and automatically reruns them when their underlying proxied data changes. This proxied data can be anything from simple values to complex, typed, and deeply nested data structures.<p>As I'm currently free to spend my time on labors of love like this, I'm planning to expand the ecosystem around this to include synchronizing data with a remote server/database, and to make CRUD apps very rapid and perhaps even pleasurable to implement.<p>I've celebrated 1.0 by creating a tutorial with editable interactive examples! <a href="https://aberdeenjs.org/Tutorial/" rel="nofollow">https://aberdeenjs.org/Tutorial/</a><p>I would love to hear your feedback. The first few people to actually give Aberdeen a shot can expect fanatical support from me! :-)
Show HN: Aberdeen – An elegant approach to reactive UIs
Yes, another reactive UI framework for JavaScript. Bear with me, please... :-)<p>I 'invented' the concept for this back in 2011, and it was used (as a proprietary lib) in various startups. Even though <i>many</i> similar open source libs have been released since, and boy have I tried a lot of them, none have been able to capture the elegance and DX of what we had back then. I might be biased though. :-)<p>So I started creating a cleaned-up, modern, TypeScript, open source implementation for the concept about five years ago. After many iterations, working on the project on and off, I'm finally happy with its API and the developer experience it offers. I'm calling it 1.0!<p>The concept: It uses many small, anonymous functions for emitting DOM elements, and automatically reruns them when their underlying proxied data changes. This proxied data can be anything from simple values to complex, typed, and deeply nested data structures.<p>As I'm currently free to spend my time on labors of love like this, I'm planning to expand the ecosystem around this to include synchronizing data with a remote server/database, and to make CRUD apps very rapid and perhaps even pleasurable to implement.<p>I've celebrated 1.0 by creating a tutorial with editable interactive examples! <a href="https://aberdeenjs.org/Tutorial/" rel="nofollow">https://aberdeenjs.org/Tutorial/</a><p>I would love to hear your feedback. The first few people to actually give Aberdeen a shot can expect fanatical support from me! :-)
Show HN: Hyvector – A fast and modern SVG editor
I have been working on Hyvector for the last five years and finally decided to present the result of my work.<p>Hyvector is an SVG editor that runs in all modern browsers. It is stable, very fast, and capable of handling complex SVG images.<p>Big new features like art strokes, vector tracing, colorizing are in the making, but for now the focus is on pushing a polished first release out of the door.<p>I would love to hear any feedback on what you like, missing features, or any bugs you encounter via our issue tracker: <a href="https://github.com/hyvectorapp/hyvector-issues">https://github.com/hyvectorapp/hyvector-issues</a><p>Note that while Hyvector should work on a phone, it is much more usable on a desktop computer or tablet.
Show HN: Hyvector – A fast and modern SVG editor
I have been working on Hyvector for the last five years and finally decided to present the result of my work.<p>Hyvector is an SVG editor that runs in all modern browsers. It is stable, very fast, and capable of handling complex SVG images.<p>Big new features like art strokes, vector tracing, colorizing are in the making, but for now the focus is on pushing a polished first release out of the door.<p>I would love to hear any feedback on what you like, missing features, or any bugs you encounter via our issue tracker: <a href="https://github.com/hyvectorapp/hyvector-issues">https://github.com/hyvectorapp/hyvector-issues</a><p>Note that while Hyvector should work on a phone, it is much more usable on a desktop computer or tablet.
Show HN: Hyvector – A fast and modern SVG editor
I have been working on Hyvector for the last five years and finally decided to present the result of my work.<p>Hyvector is an SVG editor that runs in all modern browsers. It is stable, very fast, and capable of handling complex SVG images.<p>Big new features like art strokes, vector tracing, colorizing are in the making, but for now the focus is on pushing a polished first release out of the door.<p>I would love to hear any feedback on what you like, missing features, or any bugs you encounter via our issue tracker: <a href="https://github.com/hyvectorapp/hyvector-issues">https://github.com/hyvectorapp/hyvector-issues</a><p>Note that while Hyvector should work on a phone, it is much more usable on a desktop computer or tablet.
Show HN: Extension for full-text browser history search
Hey. I’ve been working on Rearview, a browser extension that makes browsing history more useful. It’s available for Chrome, Edge, and Firefox.<p>What it does:<p>- Full-text Search: Search page content, not just URLs or titles.<p>- More Filter: Organize history by date, time, or visits.<p>- AI Assistant: Get insights from your history. (Optional, with your own api key.)<p>Everything stays local in IndexedDB.<p>Feedback & Feature request welcome.<p>BTW, since Firefox does not provide a favicon URLs implementation (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1315616" rel="nofollow">https://bugzilla.mozilla.org/show_bug.cgi?id=1315616</a>),I am currently requesting icons in Firefox via <a href="https://icon.horse/" rel="nofollow">https://icon.horse/</a>, the performance seems not ideal.
Is there a more recommended solution?
Show HN: US Routing – Python library for fast local routing in the US
Show HN: US Routing – Python library for fast local routing in the US