Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
destel
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
destel
3mo ago
Just be careful with model personalization. Gemini once learned that I'm an engineer and now "translates" all conversations into engineering language, even if we talk about some philosophical stuff
2.
▲
The "superpower" AI unblocked is ability to ask tons of stupid questions
(old.reddit.com)
3 points
by
destel
3mo ago
|
2 comments
3.
▲
Building what customers need, not just what they ask for
(linear.app)
2 points
by
destel
1y ago
|
1 comments
4.
▲
Developing an AI Agent
(dolthub.com)
1 points
by
destel
1y ago
|
0 comments
5.
▲
The official 2025 Go Developer Survey is live
(go.dev)
2 points
by
destel
1y ago
|
0 comments
6.
▲
by
destel
1y ago
I had similar bad results with gpt 4o/5 when they got these image generation capabilities. Don’t know what’s the reason: my bad prompting or these models being tuned to work with photos/illustrations only
7.
▲
by
destel
1y ago
Some examples are mind blowing. It’s interesting if it can generate web/app designs
8.
▲
by
destel
1y ago
You're not late. Just yesterday I've configured new reply notifications via RSS. Typically function "f" does two things. 1. Performs calculations (this can be parallelized). 2. Writes results somewhere (this must happen
9.
▲
Dart VST3 Toolkit
(github.com)
1 points
by
destel
1y ago
|
0 comments
10.
▲
by
destel
1y ago
Thanks. This replyTo pattern is very similar to promises in other languages.
11.
▲
by
destel
1y ago
UPD. I've just made a small but important clarification to the article. While in many cases it's easier and even preferred to calculate all results, accumulate them somewhere, then sort; this article focuses on memory bound algori
12.
▲
by
destel
1y ago
I've just made a small but important clarification to the article. While in many cases it's easier and even preferred to calculate all results, accumulate them somewhere, then sort; this article focuses on memory bound algorithms
13.
▲
by
destel
1y ago
Wow, that’s some seriously sophisticated stuff - it’s not that often you see a heap used in typical production code (outside of libraries)! Your first example definitely gives me merge-sort vibes - a really clean way to keep things ordered
14.
▲
by
destel
1y ago
I haven’t used Java for about a decade, so I’m not very familiar with streams api. Your snippet looks good and concise. One thing I haven’t emphasized enough in the article is that all algorithms there are designed to work with potentially
15.
▲
by
destel
1y ago
Hi everyone, I’m the author of the article. Happy to answer any questions or discuss concurrency patterns in Go. Curious how others tackle such problems.
16.
▲
Preserving Order in Concurrent Go Apps: Three Approaches Compared
(destel.dev)
77 points
by
destel
1y ago
|
25 comments
17.
▲
by
destel
1y ago
Hi everyone. I built a tiny web game where the goal is to pick the lowest number that nobody else picked. It runs once per day — if someone picks the same number as you, you’re both eliminated. Since the mechanics are simple, I focused on f
18.
▲
Show HN: A daily challenge where the lowest unique number wins
(golow.app)
2 points
by
destel
1y ago
|
1 comments
19.
▲
Real-Time Batching in Go
(destel.dev)
1 points
by
destel
2y ago
|
0 comments
20.
▲
by
destel
2y ago
Author here. While the article uses database updates as the example, the same pattern works great for any high-frequency API calls or operations that could benefit from batching. The goal was to make the solution completely transparent - de
21.
▲
Real-Time Batching in Go: A Clean Pattern for High-Frequency Database Updates
(destel.dev)
3 points
by
destel
2y ago
|
1 comments
22.
▲
by
destel
2y ago
Author here. Recently started a personal dev blog - happy to answer any questions.
23.
▲
Fast Listing of Files from Large S3 Buckets Using Go Concurrency
(destel.dev)
2 points
by
destel
2y ago
|
1 comments
24.
▲
by
destel
2y ago
Thank you very much for the feedback. I thought about something similar some time ago. Buffer of size one, then measure the average time each item spends in the buffer. But for debugging your approach is simpler and more practical.
25.
▲
by
destel
2y ago
Thank you. I "stealed" the name from scala. They have the similar value+error type. Maybe in context it rill the better name could have been "Item"
26.
▲
by
destel
2y ago
I have to be honest - I haven't ever heard about it. Just checked and found it's very mature and popular, though it seems to have had no commits in the last 2 years. After quick scanning, I'd highlight these 2 differences: -
27.
▲
by
destel
2y ago
I have some benchmarks in the project's wiki on Github. I can confirm your point: Rill's main bottleneck is channel operations, the library itself adds negligible overhead on top. Of course, for multi-stage pipelines the number of
28.
▲
by
destel
2y ago
Thank you for the feedback. I agree with your point. The current solution is to make pipeline stages context-aware (which is often happens automatically) and cancel the context before returning. This is the responsibility of the user and ca
29.
▲
by
destel
2y ago
Thank you! I took a quick look at mgmt, it's quite a large and complex project. I'd need to better understand your DAG-based concurrency patterns to say if Rill would be a good fit. Could you share some examples of the concurrent
30.
▲
by
destel
2y ago
Thank you! There are two pieces of motivation here. The first one is removing boilerplate of spawning goroutines that read from one channel and write to another. Such code also needs wait/err group to properly close the output channel.
More ›