Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
dolmen
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
16 ms
·
181.
▲
by
dolmen
7mo ago
It does: https://github.com/dolmen-go/codegen/blob/master/.github/wor...
182.
▲
by
dolmen
7mo ago
Is this the Stephen Dolan creator of jq? https://jqlang.org/
183.
▲
by
dolmen
7mo ago
Stop trusting any dependency now.
184.
▲
by
dolmen
7mo ago
It looks like a search for the command line tool available to send content to the clipboard. Can't tell if that obfuscated code works though.
185.
▲
by
dolmen
7mo ago
Esc :q!
186.
▲
by
dolmen
7mo ago
The dishwasher and the washing machine don't auto fill. Scaling issues as family grows. Ex: sorting socks.
187.
▲
by
dolmen
7mo ago
Like for humans, teaching the good way to do things works better than forbidding a few bad behaviours.
188.
▲
by
dolmen
7mo ago
"more reliably" is still not "reliably".
189.
▲
by
dolmen
7mo ago
Paris' périphérique is nowadays limited to 50 km/h.
190.
▲
by
dolmen
7mo ago
None.
191.
▲
by
dolmen
7mo ago
All interactions with the "author" of the "research" in this thread also. Reading HNN is not interesting anymore if bots are allowed at the party.
192.
▲
by
dolmen
7mo ago
As creators of Go have strong ties with the creators of C, that idea is not so dated.
193.
▲
by
dolmen
7mo ago
Tell us about your concrete experience of development in Perl.
194.
▲
by
dolmen
7mo ago
So your shared .venv is the vector for the agent to escape the sandbox.
195.
▲
by
dolmen
7mo ago
And note that "crétin" means "dumb", so mispronouncing "chrétien" can seriously go wrong. https://fr.wiktionary.org/wiki/cr%C3%A9tin
196.
▲
by
dolmen
7mo ago
Ask AI about a strategy and tools to build to figure out.
197.
▲
by
dolmen
8mo ago
The right solution is to be registered at Cloudflare, but then getting the customer reach the guy who handles Cloudflare settings (a few clicks) is the hard part.
198.
▲
by
dolmen
9mo ago
Your production deployment might be done with container images, but Dockerfile is not the only way to build them. Guix has builtin support to build container images without Dockerfile.
199.
▲
by
dolmen
9mo ago
Switch off the phone, then leave.
200.
▲
by
dolmen
9mo ago
I recommend La Cité de la dentelle, in Calais, North of France (good train stop between Paris and London). Leavers machine that weight tons. Technology from 19th century that is still in production nowadays. https://www.cite-dent
201.
▲
by
dolmen
10mo ago
I don't get the logic of cleaning dishes BEFORE putting them in the dishwasher.
202.
▲
by
dolmen
10mo ago
I think there is still space for an alternate Go syntax for scripting with the following constraints: * a single file exposing a "main" package and its "func main()" * import syntax that merges requires from go.mod (impo
203.
▲
by
dolmen
10mo ago
Also, for Go oneliners: https://github.com/dolmen-go/goeval (Disclaimer: author here)
204.
▲
by
dolmen
10mo ago
… so presenting it as a paraphrase is misleading.
205.
▲
by
dolmen
10mo ago
As you think Go is a wrong way for computing, tell us about the others routes that we should explore…
206.
▲
by
dolmen
10mo ago
Access control to your (customer's) data may also be a concern that rules out managed services like RDS.
207.
▲
by
dolmen
10mo ago
But first ensure that the input error is properly reported to the client in the response body (ideally in a structured way), so the client could have figured out by himself. If a fix is needed on your side for this matter, having a conversa
208.
▲
by
dolmen
10mo ago
Log4J style logging is effectively a hook system. But it is too easy to badly use it with too high level and delegate level fixing to the end user.
209.
▲
by
dolmen
10mo ago
TLDR: I agree. A library might also be used in multiple place, maybe deeply in a dependency stack, so the execution context (high level stack) matters more than which library got a failure. So handling failures should stay in the hands of t
210.
▲
by
dolmen
10mo ago
The idiomatic practice in Go for libraries is to wrap returned errors and errors can be unwrapped with stdlib tooling. This is more useful to handle errors at runtime than digging into a stack trace.
More ›