Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
silverwind
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
by
silverwind
7d ago
It's quite a lot wider and thicker than a mini, and imho looks quite ugly when folded, I don't see the appeal as a single-handed device.
2.
▲
by
silverwind
12d ago
Yeah, the UI is the real and only reason to use Nitter. It's a very similar situation with old reddit.
3.
▲
by
silverwind
13d ago
Isn't that basically AsyncGenerator?
4.
▲
by
silverwind
23d ago
It's possible to drive them hard enough to really read everything, but you have to go really hard on them with many many cycles.
5.
▲
by
silverwind
24d ago
Those benchmarks don't tell much, they only check if a problem was solved, not how. Also there's surely a lot of benchmaxxing going on in the model training.
6.
▲
by
silverwind
27d ago
There are no EU instances of GitHub, it's all in the US only.
7.
▲
by
silverwind
27d ago
More importantly: Once Anthropic is gone, all knowlege is lost.
8.
▲
by
silverwind
1mo ago
Most models are trained to be as "helpful" as possible which may work for a chatbot but not for code.
9.
▲
by
silverwind
1mo ago
Changing output style shouldn't affect thinking at all.
10.
▲
by
silverwind
2mo ago
It's sad that such basic stuff took this long. If we're lucky we might even see a `Map` function in our lifetimes.
11.
▲
by
silverwind
2mo ago
It's like 100 times slower than ruff. They had to massive caching techniques to get it to a remotely acceptable speed.
12.
▲
by
silverwind
2mo ago
On problem of such go linters is they can only lint what the compiler sees so if you have multiple `build` tags, you need to run multiple lint passes. No other language's linter operates like they, they all operate on file level.
13.
▲
by
silverwind
2mo ago
Yes, tsconfig is a mess to scope. It needs a re-design to allow glob-based matching for all options and in typescript instead of jsonc.
14.
▲
by
silverwind
2mo ago
Seems they not running these agents with the same permissions of the user prompting them, what a disaster.
15.
▲
by
silverwind
3mo ago
I think tsdown is much better suited for CLI and library builds. Vite has many web-isms that don't matter for these.
16.
▲
by
silverwind
4mo ago
Yeah, a missed opportunity. But I'm sure such a compiler will eventually arise.
17.
▲
by
silverwind
4mo ago
True, sometimes a Claude answer is so on the spot, it'd a waste to not post it alongside your short summary.
18.
▲
by
silverwind
4mo ago
PR spam is a major problems for repo that run bounties. Maybe GitHub should temporarily block accounts from raising PRs if like 95%+ of them are getting rejected.
19.
▲
by
silverwind
4mo ago
Knowing them, I expect a release probably next week, have fun in production with it.
20.
▲
by
silverwind
4mo ago
It'll always be a cat-and-mouse game. If npm adds protections, it'll only yield false-positives and workarounds will be trivial.
21.
▲
by
silverwind
4mo ago
Almost all these recent compromises seem to involve either cache poisoning or prompt injection via untrusted variables.
22.
▲
by
silverwind
4mo ago
Python had these too, no ecosystem is safe.
23.
▲
by
silverwind
4mo ago
I think it's just a case of brain drain, followed by reckless AI adoption which both drove the quality down.
24.
▲
by
silverwind
4mo ago
All those forks turned out to be inferior projects with substantially less contributions than the originals.
25.
▲
by
silverwind
4mo ago
It's definitely helpful to know whether a PR was AI-assisted or not and the git attribution line is a simple and effective way of communicating that. I also recommend specifying model name and version so the maintainer knows upfront th
26.
▲
by
silverwind
4mo ago
I'm going even simpler, just bare docker with a idempotent bash wrapper.
27.
▲
by
silverwind
5mo ago
I hope Node eventually gets a WebSocket server like Bun has.
28.
▲
by
silverwind
5mo ago
Problem with Go is the type system is rudimentary, so you can't "restrict" AIs as well as you could in Typescript.
29.
▲
by
silverwind
5mo ago
https://www.typescriptlang.org/tsconfig/#erasableSyntaxOnly covers them all, I strongly recommend running with that option enabled to be future-proof.
30.
▲
by
silverwind
5mo ago
Modern Typescript does not need runtime features.
More ›