0x696C6961

6 ms·

1.
by 0x696C6961 4d ago
I don't think it's clear at all.
2.
by 0x696C6961 5d ago
Liam's Razor: Never attribute to misalignment what can be explained by a human seeking attention.
3.
by 0x696C6961 5d ago
The https://casl.js.org/v7/en/ link is dead edit: fixed now
4.
by 0x696C6961 8d ago
Jesus dude ... its an LLM, it's not going to fuck you.
5.
by 0x696C6961 10d ago
The only useful generic skill I have is the ast-grep one.
6.
by 0x696C6961 10d ago
I like the mermaid sequence diagrams more. But D2 for everything else. No GitHub integration yet though.
7.
by 0x696C6961 10d ago
It would be cool if the POW could be done ahead of time. That way I don't get stuck waiting while I'm working. Some type of credit/tokens that my browser could then spend.
8.
by 0x696C6961 13d ago
The lazy loading is a harness concern.
9.
by 0x696C6961 13d ago
How is this better than using MCP?
10.
by 0x696C6961 23d ago
Not sure why you're getting downvoted. This approach has been shown to work. The money isn't for funding the maintenance though, it's strictly to keep the riff-raff out.
11.
by 0x696C6961 25d ago
Not working from Thailand
12.
by 0x696C6961 26d ago
Go away
13.
by 0x696C6961 27d ago
Dude you're not normal and I envy your grit.
14.
by 0x696C6961 27d ago
These individuals are demonstrating that they can be replaced with AI. I worry for them.
15.
by 0x696C6961 27d ago
I think you're projecting
16.
by 0x696C6961 27d ago
Lol you don't need an app for this. My (barista) gf did the same thing by just telling Claude to create pages in notion.
17.
by 0x696C6961 27d ago
This is anecdotal, but I know that a lot of my coworkers and coasting and putting up one AI generated PR per day which they've hardly even self reviewed.
18.
by 0x696C6961 27d ago
You can also make breaking changes to internal APIs without versioning or release coordination. Just update all the call sites.
19.
by 0x696C6961 28d ago
I've dreamt about pernosco (rr) style traces being available for tests in PRs. Imagine a DST setup where the PR shows diffs of deterministic test execution traces (I have no idea what these diffs would look like)
20.
by 0x696C6961 28d ago
Well either way, these things usually land in golangci-lint first and get promoted if they're deemed useful enough.
21.
by 0x696C6961 28d ago
I think that's a no-go because vet checks have no-false-positive policy. Ie, when go vet flags something, its a bug.
22.
by 0x696C6961 28d ago
Mhm, probably worth a golang-ci check for duplicate field names which are accessed by methods on the embedded type.
23.
by 0x696C6961 28d ago
random() return 4; // chosen with dice roll
24.
by 0x696C6961 29d ago
The survey started in 2016. But even if it didn't, that still wouldn't make a difference. You're clearly not a serious person, so I think I'm done responding.
25.
by 0x696C6961 29d ago
If they didn't want to add generics, why were they actively working on generics proposals and designs since the inception of the language? Was it a hedge against the potential of being pressured into adding them in the future?
26.
by 0x696C6961 29d ago
This idea that they just caved and added them due to pressure is a false narrative invented by detractors like yourself. Here is a timeline if you're interested: 2009 Go released. June 2010 https://github.com/golang&#x2
27.
by 0x696C6961 1mo ago
The generics implementation is perfectly fine. The fact that you completely dodged my question is telling. But please, keep living in your alternate reality.
28.
by 0x696C6961 1mo ago
If this was true, why did they add generics?
29.
by 0x696C6961 1mo ago
https://github.com/golang/go/issues/70811 Go moves slowly
30.
by 0x696C6961 1mo ago
This is exactly what I do. I don't get why everyone is trying to reinvent the whole development workflow/lifecycle. Our existing tools and processes are pretty good.

More ›