icholy

Has uncle Bob actually produced any useful software? Are there any examples of his work out there which can be analysed?

> Also, a nitpick - you can call async functions from sync ones, you just can't access the return value.

Or wait for them to finish.

I wish we had an rr for nodejs.

There are some bugs I would never have figured out without this technique. It feels like cheating.

Goland uses delve which has rr support

That's up to debuggers to implement. lldb, gdb, and delve all support rr traces.

It works with pretty much any compiled language.

I use https://github.com/simonw/llm-cmd

We used to have a rule where you couldn't move issues "backwards" in the workflow. Accidentally closed an issue? Gotta create a new one.

At my work you can mark any issue with "won't fix". The issues are right pretty often though.

Blender didn't start as open source.

All of the blank lines can be deleted from that function without reducing the readability.

Whitespace is useful in normal prose because it has no inherent visual structure aside from punctuation. A programing language is inherently structured into logical functions and blocks. If your function is so complex that you need to start adding whitespace to make it visually parseable then that's its own problem.

I prefer no blank lines. If you feel like you need one, write a line comment instead describing the next section.

I want an LLM which uses an LSP to gather more context.

I was one of the people who signed up for plus that day. It took me a while to realizing that the voice feature was not the same one being demoed. I think it was a bad move to roll it out like that.

There's a benefit of microservices that I don't hear talked about. At my workplace, there's absolutely no respect for api boundaries. Devs will monkey patch and reach into other module's internals without a second thought. I can't imagine the monstrosity that would exist if the network boundary wasn't there to stop them ...

The password requirements on some websites seem like they're designed to deter me from creating an account.

Suggesting try/catch indicates that you have virtually no experience using Go. You're standing on the side lines yelling stupid/non-sensical feature requests and getting upset when you're not taken seriously.

Neovim core has lots of bugs.

This is how I've been feeling about neovim recently.

I've been using claude 3 with semgrep and the results are impressive https://github.com/icholy/semgrepx

Creating stack traces is expensive.

Why spend your time coding when you could be fiddling with configuration files all day? I love re-learning how to make package.json, tsconfig, esbuild, eslint, prettier, mocha and webpack play nice every time I start a new project.

I skimmed the README, but I don't see anything similar to the grep-like behavior described in the post.

Maybe you should try the same.

I was really hoping this would be rr but more general purpose.

What you're actually saying is "I don't understand the colored function problem".

> This is in contrast to the fact that Go's cheap threading means that you don't need to colour your functions with async or not async. But this quote that you sort of have to do this with context or no context.

This doesn't have the usual problems associated with colored functions though (ie, calling async functions from non-async functions or vice-versa). If you don't need cancellation, pass a `context.Background()` and you're done.

> If goroutines are so cheap then why not let the library spawn them. As long as the interface doesn't reveal if they are being used or not it shouldn't matter.

Agreed. providing a synchronous API is what's important.

You can, which makes me wonder why they added the range-over-int functionality when it could have been a function in the proposed iter package:

   for x := range iter.N(10) { ... }