Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
darccio
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
13 ms
·
1.
▲
Observability made easy: Serverless and Datadog Orchestrion
(giou-k.github.io)
3 points
by
darccio
6d ago
|
0 comments
2.
▲
Datadog saves over $1M each month by optimizing AI usage
(datadoghq.com)
3 points
by
darccio
17d ago
|
0 comments
3.
▲
The Shape of Go
(luislsousa.com)
3 points
by
darccio
22d ago
|
0 comments
4.
▲
by
darccio
27d ago
Indeed, this approach sounds like the way to go for a really independent ecosystem. Thanks for the clarification and the additional insight!
5.
▲
by
darccio
1mo ago
Just to clarify, when you say "self host issues/PRs" is it mostly "self host a knot"? I kind of expected something similar to what you can do for CI but I'm not able to find any docs regarding self hosting issu
6.
▲
by
darccio
1mo ago
This approach feels just "add friction to your AI usage". It seems the worst of both worlds, both hand-coded and vibe-coded. You paste your code into a chat so it can tell you what to type yourself (the codebase access rule looks
7.
▲
Achieving Local AI Inference with Go 1.27's SIMD Package
(blog.devgenius.io)
5 points
by
darccio
1mo ago
|
0 comments
8.
▲
Using Go for Mobile Apps: A retrospective on a year of development with Gomobile
(davidsobsessions.com)
1 points
by
darccio
2mo ago
|
0 comments
9.
▲
by
darccio
4mo ago
A PR staging area. This would be a good step forward.
10.
▲
by
darccio
4mo ago
I'm a happy smolmachines user. It has some rough edges but it works really great. I haven't tested microsandbox and boxlite, and maybe they consume OCI images too, but smolmachines is a winner because of that.
11.
▲
Twenty Years of Stacking Commits
(julien.danjou.info)
1 points
by
darccio
5mo ago
|
0 comments
12.
▲
The Limits of Self-Improving in Large Language Models
(arxiv.org)
1 points
by
darccio
5mo ago
|
0 comments
13.
▲
Running local LLMs offline on a ten-hour flight
(deploy.live)
129 points
by
darccio
5mo ago
|
105 comments
14.
▲
by
darccio
5mo ago
I wonder if it's usual for other professions/fields to have this tendency to create laws/aphorisms so ingrained. I'm biased as software engineer but it seems to me that is more common in computer science than others.
15.
▲
EU Site-Blocking Is Broken: Report Calls for Ban and Rightsholder Liability
(torrentfreak.com)
5 points
by
darccio
5mo ago
|
0 comments
16.
▲
How I made –dangerously-skip-permissions safe in Claude Code
(codeofchange.io)
1 points
by
darccio
5mo ago
|
0 comments
17.
▲
World Socialist Web Site to Launch Socialism AI (2025)
(wsws.org)
2 points
by
darccio
5mo ago
|
0 comments
18.
▲
The Obscure Relation of Appropriateness
(vincentcarchidi.substack.com)
1 points
by
darccio
5mo ago
|
0 comments
19.
▲
by
darccio
5mo ago
Even with Sonnet or "lower" models like Kimi is trivial. The only thing I still find with AI-generated code is some degree of overengineering.
20.
▲
by
darccio
6mo ago
I don't feel they resist. Quoting them: > We understand your concerns and truly appreciate your suggestions. As previously mentioned, this is not something that is enforced by the reference implementation — these are simply recommen
21.
▲
by
darccio
6mo ago
Having explored that approach (†), I can tell that generating Go assembly is harder than it seems. †: I've tried to transpile Rust code through WASM into Go assembly, and I've also explored how to inject trampolines into Go binari
22.
▲
by
darccio
6mo ago
It makes no sense. eIDAS 2.0 specs don't require specific hardware [0]. They basically store verifiable credentials [1] and any other cryptographically signed attestations. This feels like laziness from German implementers, as they don
23.
▲
Lisette – Rust syntax, Go runtime
(lisette.run)
5 points
by
darccio
6mo ago
|
0 comments
24.
▲
Tracing Goroutines in Realtime with eBPF
(sazak.io)
80 points
by
darccio
6mo ago
|
9 comments
25.
▲
Type Construction and Cycle Detection
(go.dev)
3 points
by
darccio
6mo ago
|
0 comments
26.
▲
by
darccio
6mo ago
Just a heads-up: I changed one of my repos URL [0], released as v0 at the moment, and bumped to v1 alongside the URL change. Go treats v0 and v1 as equivalent, so it tries to bump from v0.x to v1.0.0 keeping the old URL. This causes errors
27.
▲
Building the Good Web
(brennan.day)
2 points
by
darccio
6mo ago
|
0 comments
28.
▲
Can It Resolve Doom? Game Engine in 2k DNS Records
(blog.rice.is)
5 points
by
darccio
6mo ago
|
0 comments
29.
▲
//go:fix inline and the source-level inliner
(go.dev)
11 points
by
darccio
6mo ago
|
2 comments
30.
▲
The Broken Equilibrium
(stackgen.com)
1 points
by
darccio
7mo ago
|
0 comments
More ›