News for hackers. Stuff that matters.

aliezsid

Oh definitely, it's a straightforward implementation with a few additions to avoid sending too many emails (both to not irritate the user and to save me from email sending costs)
Thanks! I'm glad you like it :)
Not exactly a "product" but yes, recently added an uptime notifier service in the sea of 1000s of these services.

https://ping.tinytown.studio/

Trying to keep it simple and tiny for now, would like to know what others think

Re:Show HN: My personal website is a shell on Thursday April 08, 2021 @02:11AM (#26735619)
Adding to the feedback, click on the whole thing should just focus the current input, I mean, that's general behaviour.

Amazing website though, liked the idea

not sure if this is what you wanted but

https://commitlog-web.herokuapp.com

Yeah, it was aimed at developers, though the idea of creating a web frontend for it for public github repo doesn't seem like a bad one. Should probably add that in scope
Re:Show HN: Minimal music player, uses YouTube as source on Thursday July 09, 2020 @01:48AM (#23777290)
Yeah, there’s a simple server that pipes a play stream to the response which is attached to the audio tag
Re:Show HN: Minimal music player, uses YouTube as source on Wednesday July 08, 2020 @06:12AM (#23768502)
working on the sharing and saving part, currently focused on a dev tool of mine.
Re:Show HN: A file tree based API Router on Tuesday July 07, 2020 @03:24PM (#23763028)
Oh nice, good approach. I went with Native http for performance reasons
Re:Show HN: A file tree based API Router on Tuesday July 07, 2020 @09:44AM (#23759166)
I create a tree similar to the file structure that is used by the actual router when it handles requests to figure out which handler to pass the `req` and `res` objects. This is in the stable(`master`) branch.

The `canary` branch implements the same thing but instead of a object tree , it creates a flat object and uses regex's to find the registered handler which is faster but creates an overlap which I'm trying to fix.

In simple senses, it there's to make sure that the router only passes down the req,res to the valid handler and doesn't do any other processing other than maybe, query parsing and param parsing

I'd agree that it's easy to compose but the API of the properties the components expose are inconsistent in certain cases and if I can get a native build out of it, I shouldn't be complaining about a minor issue
Makes sense. Will give these a try
I want the app to cross platform but not at the expense of a Ram hungry app that I just throw out. And yeah, i wouldn’t mind writing the logic in a language like rust or C and then invoking it from the native bindings If there’s no other solution out there for me to achieve performance over the so called “Let’s bundle the whole browser with every app” working solution.
There’s 2 projects. One is my take on a code editor and the other is a minimal inventory management system and even though I can gt through with just building one for Mac and the other for just Windows. I’d still prefer going with. Cross platform approach
and why do you think so?

Older »