Show HN: A better way to read blogs
2 by khet | 0 comments on Hacker News.
Wednesday, 6 September 2023
Tuesday, 5 September 2023
New Show Hacker News story: latest news
Show HN: Open source Postman alternative with type safety
3 by Volbohel | 0 comments on Hacker News.
Hello! This is Jeane and Samuel and we’re building RecipeUI. RecipeUI is an open source Postman alternative that uses TypeScript to statically type and autocomplete requests. We built this because current API tools don’t deal with the fact that some APIs are just painful to work with. For us, it’s usually error after error as we try to figure out how to properly form the first request. We recorded a demo to show you how TypeScript helps us autocomplete a request correctly. https://youtu.be/O_Mly_p-g5s How does our platform improve the developer experience? The analogy is similar to using a statically typed language vs dynamically typed. Most API tools are dynamically typed. You’re guessing the params and relying on the request to magically work at runtime, only for you to go back to stack overflow or the docs when it doesn’t. We take the approach of defining parameters and the schema first. When you add a new parameter, you need to mention upfront if it’s required and what type it is (integer, string, boolean). While this can be painful in the beginning, it will save you and anyone you share this with the hassle of understanding how this API works. Our app is cross-platform on web and desktop. Our desktop app is <20mb and built on top of Rust with Tauri, NextJS, and Supabase. We open source our code because we want to be transparent about how API requests and secrets are handled (all local IndexDB). I built the first version of this at Robinhood when my colleagues were sharing bash scripts and internal APIs on slack to test things. I wanted to make it easier for anyone to use an API quickly and made use of our OpenAPI specs to generate a nice autocomplete API tool. Soon after, the Options team, then the Crypto team, and then the whole eng org at Robinhood adopted this tool! Try it out at recipeui.com! Please star us on GitHub if you like the product https://github.com/RecipeUI/RecipeUI .
3 by Volbohel | 0 comments on Hacker News.
Hello! This is Jeane and Samuel and we’re building RecipeUI. RecipeUI is an open source Postman alternative that uses TypeScript to statically type and autocomplete requests. We built this because current API tools don’t deal with the fact that some APIs are just painful to work with. For us, it’s usually error after error as we try to figure out how to properly form the first request. We recorded a demo to show you how TypeScript helps us autocomplete a request correctly. https://youtu.be/O_Mly_p-g5s How does our platform improve the developer experience? The analogy is similar to using a statically typed language vs dynamically typed. Most API tools are dynamically typed. You’re guessing the params and relying on the request to magically work at runtime, only for you to go back to stack overflow or the docs when it doesn’t. We take the approach of defining parameters and the schema first. When you add a new parameter, you need to mention upfront if it’s required and what type it is (integer, string, boolean). While this can be painful in the beginning, it will save you and anyone you share this with the hassle of understanding how this API works. Our app is cross-platform on web and desktop. Our desktop app is <20mb and built on top of Rust with Tauri, NextJS, and Supabase. We open source our code because we want to be transparent about how API requests and secrets are handled (all local IndexDB). I built the first version of this at Robinhood when my colleagues were sharing bash scripts and internal APIs on slack to test things. I wanted to make it easier for anyone to use an API quickly and made use of our OpenAPI specs to generate a nice autocomplete API tool. Soon after, the Options team, then the Crypto team, and then the whole eng org at Robinhood adopted this tool! Try it out at recipeui.com! Please star us on GitHub if you like the product https://github.com/RecipeUI/RecipeUI .
New Show Hacker News story: latest news
Show HN: Subsidian – Visualize a Substack archive in Obsidian graph view
4 by ddanielgal | 0 comments on Hacker News.
4 by ddanielgal | 0 comments on Hacker News.
Monday, 4 September 2023
New Show Hacker News story: latest news
Show HN: Keep – GitHub Actions for your monitoring tools
11 by talboren | 0 comments on Hacker News.
Hi Hacker News! Shahar and Tal from Keep here. A few months ago, we introduced here at HN ( https://ift.tt/iS2PnQk ) Keep as an “open source alerting CLI” and got some interesting feedback - mainly around UI, automation, and supporting more tools. We were VERY early back then, and we understood that although the current DX around creating alerts is not great, it's not that critical and developers don’t need another tool just for that. But we did find something else. While talking to developers and devops, we found that a lot of companies use many tools that generate alerts - from Cloudwatch, Prometheus, Grafana, and Datadog to tools such as Zabbix or Nagios. We definitely agree consolidation in the observability space is a real thing, but while talking to those companies we feel that there are still real use cases for having more than one tool (and for example, according to Grafana’s 2023 observability survey, 52% of the companies uses more than 6 observability tools https://ift.tt/smN6T7C ). So we that in mind, we rebuilt Keep with a simple mindset: (1) Integrate with every tool that triggers alerts - it can be either pushing alerts to Keep via webhooks or routing policies or Keep to pull alerts via the tools API. (2) Create a simple abstraction layer to run workflows on top of these alerts. (3) Maintain a great developer experience - open source, API-first, workflows as code and generally having a developer mindset while building Keep. During the time we rebuilt Keep, Datadog released their workflow automation tool ( https://ift.tt/TBecqlj ) which led us to the understanding that's exactly what we solve - but for everyone who uses tools other than Datadog. A short demo of Keep with a simple use case: https://www.youtube.com/watch?v=FPMRCZM8ZYg You can try it yourself by signing into https://ift.tt/swPrCeJ Like always - we invite you to try Keep and we are eager to hear any feedback.
11 by talboren | 0 comments on Hacker News.
Hi Hacker News! Shahar and Tal from Keep here. A few months ago, we introduced here at HN ( https://ift.tt/iS2PnQk ) Keep as an “open source alerting CLI” and got some interesting feedback - mainly around UI, automation, and supporting more tools. We were VERY early back then, and we understood that although the current DX around creating alerts is not great, it's not that critical and developers don’t need another tool just for that. But we did find something else. While talking to developers and devops, we found that a lot of companies use many tools that generate alerts - from Cloudwatch, Prometheus, Grafana, and Datadog to tools such as Zabbix or Nagios. We definitely agree consolidation in the observability space is a real thing, but while talking to those companies we feel that there are still real use cases for having more than one tool (and for example, according to Grafana’s 2023 observability survey, 52% of the companies uses more than 6 observability tools https://ift.tt/smN6T7C ). So we that in mind, we rebuilt Keep with a simple mindset: (1) Integrate with every tool that triggers alerts - it can be either pushing alerts to Keep via webhooks or routing policies or Keep to pull alerts via the tools API. (2) Create a simple abstraction layer to run workflows on top of these alerts. (3) Maintain a great developer experience - open source, API-first, workflows as code and generally having a developer mindset while building Keep. During the time we rebuilt Keep, Datadog released their workflow automation tool ( https://ift.tt/TBecqlj ) which led us to the understanding that's exactly what we solve - but for everyone who uses tools other than Datadog. A short demo of Keep with a simple use case: https://www.youtube.com/watch?v=FPMRCZM8ZYg You can try it yourself by signing into https://ift.tt/swPrCeJ Like always - we invite you to try Keep and we are eager to hear any feedback.
New Show Hacker News story: latest news
Show HN: Recognize license plates using fine-tuned yolov8, OCR and IP camera
2 by TDiblik | 0 comments on Hacker News.
Hey, just a work related project I made, which could be open sourced :D If you're looking for an example on how to use/fine-tune yolov8, I feel like taking a look at this repo and reading the README could help you get up to speed (also linked some nice refs)! This is actually a full rewrite of a proprietary project I made (and documented on my site) like a year ago, will do some finishing touches (write blog post about it, mark the old version deprecated, record a tutorial on how to set it up on an Ubuntu server, etc, etc) in the following month, but felt like sharing it now, cuz I consider it done The only proprietary part is the client, which receives the images and does stuff with db (has to interact with internal APIs, so there's no reason to make it oss anyways). Also, the client contains only the business logic, all of the fun ai/web server stuff is fully open under AGPL-3.0 (and an example client without the business logic is available ... in rust btw xdd).
2 by TDiblik | 0 comments on Hacker News.
Hey, just a work related project I made, which could be open sourced :D If you're looking for an example on how to use/fine-tune yolov8, I feel like taking a look at this repo and reading the README could help you get up to speed (also linked some nice refs)! This is actually a full rewrite of a proprietary project I made (and documented on my site) like a year ago, will do some finishing touches (write blog post about it, mark the old version deprecated, record a tutorial on how to set it up on an Ubuntu server, etc, etc) in the following month, but felt like sharing it now, cuz I consider it done The only proprietary part is the client, which receives the images and does stuff with db (has to interact with internal APIs, so there's no reason to make it oss anyways). Also, the client contains only the business logic, all of the fun ai/web server stuff is fully open under AGPL-3.0 (and an example client without the business logic is available ... in rust btw xdd).
New Show Hacker News story: latest news
Show HN: TTop – System monitoring tool with historical data, triggers and TUI
5 by inv2004 | 0 comments on Hacker News.
It is not top/htop replacement because of historical snapshots which can help you to find problems back in time
5 by inv2004 | 0 comments on Hacker News.
It is not top/htop replacement because of historical snapshots which can help you to find problems back in time
Subscribe to:
Posts (Atom)