shabbyrobe

8 ms·

1.
by shabbyrobe 1y ago
That's not what I found in my own experiments, I still had to unmarshal once inside the callback to get the `type` field out, then again once I knew what the type was. Do you have an example handy?
2.
by shabbyrobe 2y ago
IME this is a longstanding pain point with Go. There's an attempt to propose an encoding/json/v2 package [1] being kicked around at the moment [2], spawned from a discussion [3]. This at least seems to improve the situation o
3.
by shabbyrobe 3y ago
Such an instrument is the turbo encabulator.
4.
by shabbyrobe 3y ago
> I would've probably picked the modernc variation Heads up about the modernc library, it has been stuck on an old version of sqlite for several months [1]. It seems like maintainer time is the limiting factor [2]. There has been a
5.
by shabbyrobe 4y ago
I love this visualisation. Is the script to generate it publicly available?
6.
by shabbyrobe 5y ago
Since PEP 591 [1], if using mypy with Python 3.8+ or the typing_extensions module, you can also take advantage of typing.Final, which lets you statically verify something isn't changed. The catch is that it isn't enforced at runti
7.
by shabbyrobe 5y ago
There are fragments of discussion about the download timeout throughout the issue tracker, which end up leading back to this still-open but seemingly forgotten issue about adding InactivityTimeout: https://github.com/golang&
8.
by shabbyrobe 5y ago
I think it could be the same but it doesn't have to be. "What problem does this solve" is a bit more generous as at least, on the face of it, it may offer an opportunity to provide an answer that will be received in good fait
9.
by shabbyrobe 5y ago
There's also the "That Won't Work" person's sibling: the "I Don't See a Use Case" person. In my experience, "I Don't See a Use Case" people require more sophisticated tactics if you act
10.
by shabbyrobe 5y ago
Here's another fun one: https://github.com/git-lfs/git-lfs/issues/2434 > Git on Windows client corrupts files > 4Gb It's apparently an upstream issue with Git on Windows, but if you depend on
11.
by shabbyrobe 6y ago
I really didn't enjoy the game with the biters turned on, but absolutely loved it when I switched to peaceful mode. There are enough problems to sort out without them, like "why do I suddenly not have enough iron plates", or
12.
by shabbyrobe 7y ago
iTerm2 is fantastic! It can be a bit CPU hungry but you get a stack of mod cons out of the bargain. There are tons of proprietary escape codes, not least of all the incredibly useful one for "fireworks"! [1] ^[]1337;RequestA
13.
by shabbyrobe 7y ago
Indeed! Even the Go wiki advocates exactly what you're saying about looking at the tradeoffs: https://github.com/golang/go/wiki/MutexOrChannel
14.
by shabbyrobe 7y ago
I find it kinda strange that Flow has been relegated to the write-in "Other Flavours" section so soon. I know that it has been trending downwards for a while (as TypeScript trends upwards), but it feels like that story's not
15.
by shabbyrobe 7y ago
Which bits of telemetry can't be opted out of? I've set at least a hundred things in my about:config to tamp down on it but I'm never quite sure I've got all of them.
16.
by shabbyrobe 7y ago
The author of this post is also the author of the fantastic "Visualizing Concurrency in Go" [1] article. [1]: https://divan.dev/posts/go_concurrency_visualize/
17.
by shabbyrobe 7y ago
The file is liberally annotated with explanatory comments though. It's really useful if you want to cherry-pick the things that matter to you.
18.
by shabbyrobe 7y ago
Also, things might get a bit weird when you enter this 16-digit... uhh... "invoice number": 9007199254740992.
19.
by shabbyrobe 7y ago
It's not really fixed though. When using vim-go with gopls, I see extortionate memory and CPU usage relative to what gocode used to use, and glacial lookup times compared to what gocode used to offer. Maybe it's perfectly adequate
20.
by shabbyrobe 7y ago
Which is, of course, totally unacceptable. This is a critical use case for doing deep-dive debugging or for code exploration. Fortunately for us there is the wonderfully named "gohack", which does easily expose your deps for editi
21.
by shabbyrobe 8y ago
> Complaining about JS Fatigue is just like complaining about the fact that humanity has created too many tools to solve the problems we have, from email to airplanes and spaceships. No, complaining about JS Fatigue is just like complain
22.
by shabbyrobe 8y ago
Jonathan Swift in 1710: "Falsehood flies, and truth comes limping after it, so that when men come to be undeceived, it is too late; the jest is over, and the tale hath had its effect: like a man, who hath thought of a good repartee whe
23.
by shabbyrobe 8y ago
... which is a form of questioning why it's present. "Attempting to change it" in this situation is more like "submitting the pull request[1]" than "editing the code". The PR tends to only come together af
24.
by shabbyrobe 8y ago
It could just be that the devs on a team don't know how to use those tools yet. Having to learn how to use TypeScript effectively while establishing the patterns that underpin a new project would definitely slow you down. Maybe that&#x
25.
by shabbyrobe 8y ago
You can actually propagate errors from it. It's not pretty but it works: func Pants() (rerr error) { defer func() { if err := doStuff(); err != nil && rerr == nil { rerr = err
26.
by shabbyrobe 8y ago
I'm using a bunch of other extensions and customisations, so I guess there's some dodgy interaction going on somewhere. No time to go spelunking though. I'll just use it on my desktop instead, where I won't notice the lo
27.
by shabbyrobe 8y ago
I just gave it another try. Unfortunately, things haven't improved. `about:performance` shows a "medium" energy impact for TST. My 2015 Macbook's fans come on and stay on until I disable TST again, after which they relia
28.
by shabbyrobe 8y ago
Thank you for providing this detail, I used to use tree tabs before the webextensions fiasco but hadn't gone back to it yet as I wasn't aware it was possible to hide the existing tab bar. I'll definitely give it another shot
29.
by shabbyrobe 8y ago
Wow, I'd love to hear more about this.
30.
by shabbyrobe 8y ago
I've always been curious about the characters in ASCII for this, but I've never seen them used in the wild. Stuff like "Group Separator" (0x1D), "Record Separator" (0x1E) or "Unit Separator" (0x1F) Is

More ›