The best Hacker News stories from Show from the past day
Latest posts:
Show HN: Open-source Firebase Alternative? It's here
Show HN: Open-source tool to deploy infrastructure in any cloud
We have been working on multy.dev, an open-source cloud agnostic API that makes it easy to deploy the same infrastructure to any cloud provider using native managed services.<p>The motivation was the realisation that, even when using Terraform, migrating infrastructure code requires an end-to-end re-write. Even though most core resources are the same in any major cloud, developers need to learn a new provider to deploy the same infrastructure when moving providers.<p>We are still in early days of development and currently support the core services from AWS and Azure:<p>- Networking (virtual_network, subnet, route_table, security_group, network_interface, public_ip)<p>- Compute (virtual_machine, managed kubernetes)<p>- Database (managed MySQL databases)<p>- Vault (managed secrets)<p>- Storage (managed storage)<p>- Abstraction of cloud differences (Azure VM public vs AWS EC2 private by default)<p>- Deployment through Terraform<p>We’re looking for feedback from other developers about our approach. Let us know your thoughts!<p>GitHub: <a href="https://github.com/multycloud/multy" rel="nofollow">https://github.com/multycloud/multy</a>
Show HN: Pxl.to – A serverless link shortener with no limits and no downtime
I built a service based on Amazon CloudFront's global edge network of points of presence. This distributed architecture affords the user:<p>- Protection against network and application layer attacks<p>- Robust and reliable links that will never go down<p>- Instant links with low latency no matter where your visitors are in the world<p>- Unlimited tracked clicks (no cap on clicks/month)<p>The service has support for teams and custom domains, and auto-generates an SSL cert for every custom domain added, for HTTPS-secure links.<p>It's largely free and can be found at https://www.pxl.to<p>I'd love any feedback... no matter how brutal :)
Show HN: Pxl.to – A serverless link shortener with no limits and no downtime
I built a service based on Amazon CloudFront's global edge network of points of presence. This distributed architecture affords the user:<p>- Protection against network and application layer attacks<p>- Robust and reliable links that will never go down<p>- Instant links with low latency no matter where your visitors are in the world<p>- Unlimited tracked clicks (no cap on clicks/month)<p>The service has support for teams and custom domains, and auto-generates an SSL cert for every custom domain added, for HTTPS-secure links.<p>It's largely free and can be found at https://www.pxl.to<p>I'd love any feedback... no matter how brutal :)
Show HN: Simple Wave Function Collapse
Show HN: Simple Wave Function Collapse
Show HN: AI generated Magic The Gathering cards
Show HN: AI generated Magic The Gathering cards
Show HN: AI generated Magic The Gathering cards
Show HN: Bike – macOS Native Outliner
Bike’s most original feature is the “fluid” text editing. Lots of text editors have animated some interactions (cursor movement, insert newline, etc), but I think Bike is the first designed from the ground up to support fluid editing.<p>Give it a try, it feels different. (movie on home page if you don't have Mac)<p>Other Features:<p>• In text mode Bike works like a normal text editor. In outline mode rows are constrained to outline hierarchy.<p>• .bike file format is HTML subset, so files are easy to parse and manipulate. Bike also supports .opml and .txt.<p>• Scriptable via AppleScript. Javascript plugin API also expected in future, though no timing on that.<p>• Architecture needed to support fluid editing also makes Bike faster/more scalable than most (all?) outliners and many text editors. I test performance using the Moby Dick Workout[^1].<p>Implementation Notes:<p>• View is built using CALayers[^2].<p>• Animations are performed by Core animation and Motion[^3] lib.<p>• View performance is determined by visible text, not document size.<p>Model representation is interesting in that it’s just a flat list of rows. Each row has a `level` property, outline structure is determined dynamically. View implementation requires that each row has a unique ID.<p>I’m using OrderedDictionary from Swift Collections[^4] to store rows. This is Bike’s performance bottleneck for large outlines. Eventually I may change to augmented b+tree and then should be able to work with gigabytes worth of outline. That will be fun, but not sure it’s actually needed. Already probably fast enough for 99% of use cases as is.<p>Hope you find Bike interesting. I’m happy to answer any questions.<p>[^1]: <a href="https://www.hogbaysoftware.com/posts/moby-dick-workout/" rel="nofollow">https://www.hogbaysoftware.com/posts/moby-dick-workout/</a><p>[^2]: <a href="https://developer.apple.com/documentation/quartzcore/calayer" rel="nofollow">https://developer.apple.com/documentation/quartzcore/calayer</a><p>[^3]: <a href="https://github.com/b3ll/Motion" rel="nofollow">https://github.com/b3ll/Motion</a><p>[^4]: <a href="https://github.com/apple/swift-collections" rel="nofollow">https://github.com/apple/swift-collections</a>
Show HN: Bike – macOS Native Outliner
Bike’s most original feature is the “fluid” text editing. Lots of text editors have animated some interactions (cursor movement, insert newline, etc), but I think Bike is the first designed from the ground up to support fluid editing.<p>Give it a try, it feels different. (movie on home page if you don't have Mac)<p>Other Features:<p>• In text mode Bike works like a normal text editor. In outline mode rows are constrained to outline hierarchy.<p>• .bike file format is HTML subset, so files are easy to parse and manipulate. Bike also supports .opml and .txt.<p>• Scriptable via AppleScript. Javascript plugin API also expected in future, though no timing on that.<p>• Architecture needed to support fluid editing also makes Bike faster/more scalable than most (all?) outliners and many text editors. I test performance using the Moby Dick Workout[^1].<p>Implementation Notes:<p>• View is built using CALayers[^2].<p>• Animations are performed by Core animation and Motion[^3] lib.<p>• View performance is determined by visible text, not document size.<p>Model representation is interesting in that it’s just a flat list of rows. Each row has a `level` property, outline structure is determined dynamically. View implementation requires that each row has a unique ID.<p>I’m using OrderedDictionary from Swift Collections[^4] to store rows. This is Bike’s performance bottleneck for large outlines. Eventually I may change to augmented b+tree and then should be able to work with gigabytes worth of outline. That will be fun, but not sure it’s actually needed. Already probably fast enough for 99% of use cases as is.<p>Hope you find Bike interesting. I’m happy to answer any questions.<p>[^1]: <a href="https://www.hogbaysoftware.com/posts/moby-dick-workout/" rel="nofollow">https://www.hogbaysoftware.com/posts/moby-dick-workout/</a><p>[^2]: <a href="https://developer.apple.com/documentation/quartzcore/calayer" rel="nofollow">https://developer.apple.com/documentation/quartzcore/calayer</a><p>[^3]: <a href="https://github.com/b3ll/Motion" rel="nofollow">https://github.com/b3ll/Motion</a><p>[^4]: <a href="https://github.com/apple/swift-collections" rel="nofollow">https://github.com/apple/swift-collections</a>
Show HN: Bike – macOS Native Outliner
Bike’s most original feature is the “fluid” text editing. Lots of text editors have animated some interactions (cursor movement, insert newline, etc), but I think Bike is the first designed from the ground up to support fluid editing.<p>Give it a try, it feels different. (movie on home page if you don't have Mac)<p>Other Features:<p>• In text mode Bike works like a normal text editor. In outline mode rows are constrained to outline hierarchy.<p>• .bike file format is HTML subset, so files are easy to parse and manipulate. Bike also supports .opml and .txt.<p>• Scriptable via AppleScript. Javascript plugin API also expected in future, though no timing on that.<p>• Architecture needed to support fluid editing also makes Bike faster/more scalable than most (all?) outliners and many text editors. I test performance using the Moby Dick Workout[^1].<p>Implementation Notes:<p>• View is built using CALayers[^2].<p>• Animations are performed by Core animation and Motion[^3] lib.<p>• View performance is determined by visible text, not document size.<p>Model representation is interesting in that it’s just a flat list of rows. Each row has a `level` property, outline structure is determined dynamically. View implementation requires that each row has a unique ID.<p>I’m using OrderedDictionary from Swift Collections[^4] to store rows. This is Bike’s performance bottleneck for large outlines. Eventually I may change to augmented b+tree and then should be able to work with gigabytes worth of outline. That will be fun, but not sure it’s actually needed. Already probably fast enough for 99% of use cases as is.<p>Hope you find Bike interesting. I’m happy to answer any questions.<p>[^1]: <a href="https://www.hogbaysoftware.com/posts/moby-dick-workout/" rel="nofollow">https://www.hogbaysoftware.com/posts/moby-dick-workout/</a><p>[^2]: <a href="https://developer.apple.com/documentation/quartzcore/calayer" rel="nofollow">https://developer.apple.com/documentation/quartzcore/calayer</a><p>[^3]: <a href="https://github.com/b3ll/Motion" rel="nofollow">https://github.com/b3ll/Motion</a><p>[^4]: <a href="https://github.com/apple/swift-collections" rel="nofollow">https://github.com/apple/swift-collections</a>
Show HN: Bike – macOS Native Outliner
Bike’s most original feature is the “fluid” text editing. Lots of text editors have animated some interactions (cursor movement, insert newline, etc), but I think Bike is the first designed from the ground up to support fluid editing.<p>Give it a try, it feels different. (movie on home page if you don't have Mac)<p>Other Features:<p>• In text mode Bike works like a normal text editor. In outline mode rows are constrained to outline hierarchy.<p>• .bike file format is HTML subset, so files are easy to parse and manipulate. Bike also supports .opml and .txt.<p>• Scriptable via AppleScript. Javascript plugin API also expected in future, though no timing on that.<p>• Architecture needed to support fluid editing also makes Bike faster/more scalable than most (all?) outliners and many text editors. I test performance using the Moby Dick Workout[^1].<p>Implementation Notes:<p>• View is built using CALayers[^2].<p>• Animations are performed by Core animation and Motion[^3] lib.<p>• View performance is determined by visible text, not document size.<p>Model representation is interesting in that it’s just a flat list of rows. Each row has a `level` property, outline structure is determined dynamically. View implementation requires that each row has a unique ID.<p>I’m using OrderedDictionary from Swift Collections[^4] to store rows. This is Bike’s performance bottleneck for large outlines. Eventually I may change to augmented b+tree and then should be able to work with gigabytes worth of outline. That will be fun, but not sure it’s actually needed. Already probably fast enough for 99% of use cases as is.<p>Hope you find Bike interesting. I’m happy to answer any questions.<p>[^1]: <a href="https://www.hogbaysoftware.com/posts/moby-dick-workout/" rel="nofollow">https://www.hogbaysoftware.com/posts/moby-dick-workout/</a><p>[^2]: <a href="https://developer.apple.com/documentation/quartzcore/calayer" rel="nofollow">https://developer.apple.com/documentation/quartzcore/calayer</a><p>[^3]: <a href="https://github.com/b3ll/Motion" rel="nofollow">https://github.com/b3ll/Motion</a><p>[^4]: <a href="https://github.com/apple/swift-collections" rel="nofollow">https://github.com/apple/swift-collections</a>
Show HN: Bike – macOS Native Outliner
Bike’s most original feature is the “fluid” text editing. Lots of text editors have animated some interactions (cursor movement, insert newline, etc), but I think Bike is the first designed from the ground up to support fluid editing.<p>Give it a try, it feels different. (movie on home page if you don't have Mac)<p>Other Features:<p>• In text mode Bike works like a normal text editor. In outline mode rows are constrained to outline hierarchy.<p>• .bike file format is HTML subset, so files are easy to parse and manipulate. Bike also supports .opml and .txt.<p>• Scriptable via AppleScript. Javascript plugin API also expected in future, though no timing on that.<p>• Architecture needed to support fluid editing also makes Bike faster/more scalable than most (all?) outliners and many text editors. I test performance using the Moby Dick Workout[^1].<p>Implementation Notes:<p>• View is built using CALayers[^2].<p>• Animations are performed by Core animation and Motion[^3] lib.<p>• View performance is determined by visible text, not document size.<p>Model representation is interesting in that it’s just a flat list of rows. Each row has a `level` property, outline structure is determined dynamically. View implementation requires that each row has a unique ID.<p>I’m using OrderedDictionary from Swift Collections[^4] to store rows. This is Bike’s performance bottleneck for large outlines. Eventually I may change to augmented b+tree and then should be able to work with gigabytes worth of outline. That will be fun, but not sure it’s actually needed. Already probably fast enough for 99% of use cases as is.<p>Hope you find Bike interesting. I’m happy to answer any questions.<p>[^1]: <a href="https://www.hogbaysoftware.com/posts/moby-dick-workout/" rel="nofollow">https://www.hogbaysoftware.com/posts/moby-dick-workout/</a><p>[^2]: <a href="https://developer.apple.com/documentation/quartzcore/calayer" rel="nofollow">https://developer.apple.com/documentation/quartzcore/calayer</a><p>[^3]: <a href="https://github.com/b3ll/Motion" rel="nofollow">https://github.com/b3ll/Motion</a><p>[^4]: <a href="https://github.com/apple/swift-collections" rel="nofollow">https://github.com/apple/swift-collections</a>
Show HN: Babeloop, a new music sight-reading webapp
Backstory: I have a kid learning to play the clarinet in a music conservatory, which involves compulsory sight reading classes. Teaching for sight reading is done on books. The idea for this app is to port the method online, so that it's easier to practice and follow one's progress. It should also be more fun, and, for those so inclined, competitive.<p>The learning method is based on landmarks: for each clef one first learns the position of 2-3 landmarks, and then each note is in relation to a landmark. So for example, if you know where the middle G is on the treble clef, then you can learn fast that 2 positions up (next line) is B, and two positions down is E. (Anecdotally, in an earlier iteration of the app, landmark notes were displayed using specific colors; but users learned colors instead of the note position on the staff, and when they moved to a level without colors (or an actual score) they were completely lost.)<p>The app doesn't try to teach keyboard playing, or fingering for any other instrument for that matter. It only helps associate the position of a note on the staff with a name, in a given clef. It doesn't deal with octaves: a C3 is a C4 is a C; or accidentals: a sharp G is a flat G is a G. It also doesn't wait for user input, as other apps do. Music doesn't work that way; but more importantly, the point is to learn to recognize intervals instantly, <i>not</i> count them.<p>No account is necessary to use the app, only to participate in the leaderboard, and save one's score in case of device reset (or to use more than one device). When an account is created, the data is stored on the server in SQLite; I'm curious to see how far it can go. (Without an account, no data leaves the device.)<p>It's still a little rough around the edges but should work ok in reasonably recent browsers. On the client side, it uses VexFlow to display notes, staff and clefs, but animations are done using CSS transitions (not JS), to be mobile friendly. Tone.js helps provide a more accurate timing than a simple setInterval. Icons are coded in SVG by hand; for simple shapes, this is surprisingly fun and straightforward to do.
Show HN: Organize your open Chrome Tabs like apps on a desktop
Show HN: IT-Security for Developers
Show HN: What dogs can eat? (Web App)
Show HN: I built a minimal website for Los Angeles
I built <a href="https://veryla.io" rel="nofollow">https://veryla.io</a> - a minimal website for Los Angeles.<p>After growing tired of the chaotic, fast paced, attention-economy focused state of the web, I decided to build something simple and quiet. A site with no "real" database (just a json file I update by hand), no email signups, no ads, no pop ups, no data collection (besides google analytics), and no comment section filled with highly polarized politics. A site updated only 1-2 times per week.<p>It's just unique information in a simple and accessible format. The goal is for people to <i>not</i> check veryLA every day. I don't want people hitting refresh for emotionally charged SEO packed news to react to. My goal is for people to check out veryLA 1-2 per week and then go into the real world and have fun with the information they found.<p>Hope you enjoy if you live in Los Angeles or are planning to visit!
Show HN: I built a minimal website for Los Angeles
I built <a href="https://veryla.io" rel="nofollow">https://veryla.io</a> - a minimal website for Los Angeles.<p>After growing tired of the chaotic, fast paced, attention-economy focused state of the web, I decided to build something simple and quiet. A site with no "real" database (just a json file I update by hand), no email signups, no ads, no pop ups, no data collection (besides google analytics), and no comment section filled with highly polarized politics. A site updated only 1-2 times per week.<p>It's just unique information in a simple and accessible format. The goal is for people to <i>not</i> check veryLA every day. I don't want people hitting refresh for emotionally charged SEO packed news to react to. My goal is for people to check out veryLA 1-2 per week and then go into the real world and have fun with the information they found.<p>Hope you enjoy if you live in Los Angeles or are planning to visit!