Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
silverwind
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
61.
▲
by
silverwind
7mo ago
How would the LLM exactly discover such unknown CLI commands?
62.
▲
by
silverwind
7mo ago
Why would anyone use a python interpreter that is slower than CPython?
63.
▲
by
silverwind
7mo ago
Mozilla really needs to trim this menu down by default. Who needs "Print selection" in this day and age?
64.
▲
by
silverwind
7mo ago
Hopefully less `border-radius`.
65.
▲
by
silverwind
7mo ago
+1, https://github.com/anthropics/claude-code/issues/6235 is probably the most upvoted github issue that i've seen.
66.
▲
by
silverwind
7mo ago
Good think I never had one.
67.
▲
by
silverwind
7mo ago
I agree it's misleading. Ideally the author would disclose how much of the tree-sitter test suite passes.
68.
▲
by
silverwind
7mo ago
I prefer to have unused code detected during linting, but sadly, eslint has decided to kill off the APIs that support rules like `no-unused-modules`. Running a separate tool like this one or knip in place of a few lint rules just seems impr
69.
▲
by
silverwind
7mo ago
Gitea is definitely watching this one. Initialy tests show a 20x increase in syntax highlighting speed compared to the previous regexp-based approach.
70.
▲
by
silverwind
7mo ago
No watch support in compose: https://github.com/containers/podman-compose/issues/792
71.
▲
by
silverwind
8mo ago
print.enabled should disable all the print stuff.
72.
▲
by
silverwind
8mo ago
Small browsers need to unite if they ever hope to become relevant.
73.
▲
by
silverwind
8mo ago
Definitely, would be great to see a Servo-based Ladybird.
74.
▲
by
silverwind
8mo ago
No, that would probably be pnpm, even thought it's not nearly as fast because it's written in JS.
75.
▲
by
silverwind
8mo ago
Depends on how conservative their minifier is. The more aggressive, the more likely bugs are. esbuild still hits minifier bugs regularily.
76.
▲
by
silverwind
8mo ago
Not true, you can push a file and later gitignore it and it will remain visible on those UIs. It's still part of the repo. Doing it the other way around is also possible but harder as the git client will refuse but can be convinced.
77.
▲
by
silverwind
8mo ago
Quite nice. I had to split into two statements to make it work for both https and ssh because of a bug in git: [includeIf "hasconfig:remote.*.url:git@git.work:*/**"] path = ~/.gitconfig.work [includeIf &q
78.
▲
by
silverwind
8mo ago
CodeQL seems to raise too many false-positives in my experience. And it seems there is no easy way to run it locally, so it's a vendor lock-in situation.
79.
▲
by
silverwind
8mo ago
It's definitely possible. Author publishes a list of vulnerable symbols, and if these symbols have no use, your module is not vulnerable. Test coverage analysis tools have been doing such analysis for ages.
80.
▲
by
silverwind
8mo ago
Govulncheck is good, but not without false-positives. Sometimes it raises "unfixable" vulnerabilities and there's still no way to exclude vulnerabilties by CVE number.
81.
▲
by
silverwind
8mo ago
ReDoS is a bug in the regex engine. Still, V8 etc. seem to refuse to provide a ReDoS-safe regex engine by default.
82.
▲
by
silverwind
8mo ago
They could just invest into Servo's and use that.
83.
▲
by
silverwind
8mo ago
eslint had `--fix` since like 10 years, so this is not exactly new.
84.
▲
by
silverwind
8mo ago
StackOverflow was killed by its toxic moderators. I hope it stays online thought because it's massive source of knowledge, although in many cases outdated already.
85.
▲
by
silverwind
8mo ago
If the test coverage is good it will most likely be fine.
86.
▲
by
silverwind
8mo ago
I think AI is a huge boon as it reduces the human bottleneck. AI is a tool that must to be used well and many people currently raising pull requests seem to think that they don't even need to read the changes which puts unnecessary bur
87.
▲
by
silverwind
8mo ago
I like 2-4 but I despise nested selectors. They make selectors ungreppable.
88.
▲
by
silverwind
8mo ago
Nope, hardcoded deep in the OS internals.
89.
▲
by
silverwind
8mo ago
> Working for free is not fun Open source can be very fun if you genuinely enjoy it. The problem is dealing with people that have wrong expectations, those need to be ignored.
90.
▲
by
silverwind
8mo ago
`make` can do exactly the same.
More ›