Recent submissions

Comment · 3 months ago
Run it in a Docker container and give readonly access to the .git folder.

This way the agent can read git logs (this is very useful) but cannot commit directly (I don't see any value in this).

Comment · 9 months ago
Considering what's happening with PC component prices, it's likely we won't have anything to run those public models on anyway. Everything might become permanently cloud-only at some point.
Comment · 4 years ago
Comment · 4 years ago
Iterating with async/await means you wait for every result before making another call. You basically execute the async calls one by one.

Promise.all runs them all simultaneously and waits until they are all complete. It returns an array of results in the same order as the calls, so it's usually pretty straightforward to use.

Both approaches have a purpose, so it's not like you "should" strictly use one. But you should be aware of both and be able to use the one that fits the need.

Comment · 6 years ago
Can you give an example?

Because if you're talking about ads, many people (even in this post) are saying that they just don't work for small projects.

Comment · 6 years ago
I see this advice a lot, but I never really understood what the alternative is. If your product has a specific niche, maybe there are some forums or subreddits dedicated to it, sure. But if it's a game? Some are designed for a niche audience, but most really aren't.

Another thing is that most of the forums/subreddits these days have strict rules against self-promotion.

And I'm not saying that you're wrong - I'm just wondering what do you think is the right way to do things.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton