nitrix

You're confused. It's not Anthropic's responsibility to monitor and fix everything that's said correctly or incorrectly about them. They're doing excellent given what they're capable to do in this situation.

Error handling is as important as the happy path of an application. It’s not something you sweep under the rug.

The err != nil quickly turns into metrics, logs, fallback strategies, retry mechanisms, flight recording, rate limiting, updating caches, so on.

Anyone who’s trying to shorten this hasn’t maintained any actual real software.

Some more examples:

  int v, *w, x[5], *y[5], (*z[5])(int, int);

Where v is an int, w is a pointer, x is an array, y is an array of pointers, z is an array of function pointers, etc.

Similarly, typedef is also just a keyword in front of a regular declaration.

  int foo[5];
  typedef int foo[5];

  int bar(void);
  typedef int bar(void);

Now you can use `bar *` as a function pointer.

The entire language works like this.

I think it’s similar to telling children to look both ways before crossing the street. If you don’t explain why, they won’t see the point and optimize by not doing it. Instead, if you emphasize it’s for safety to avoid mistakes, that’s something Claude is trained to highly value and more likely to abide by.

I'm doubtful the venn diagram intersection of engineers and the world cup is as big as you think it is.

I’m the Alex mentioned in the acknowledgments, feel free to ask your questions.

Yes, the () operator dereference function pointers automatically for you for convenience. There's also the surprise that you can infinitely dereference function pointers as they just yield you more function pointers.

That is correct.

  int x, *p, arr[5], fn(), (*pfn)();

Using x, or dereferencing p, or subscripting the array arr, or declaring a function that can be called with fn, or dereferencing the function pointer pfn then calling it, all these things would produce an int.

It's the intended way to read/write declarations/expressions. As a consequence, asterisks ends up placed near the identifiers. The confused ones will think it's a stylistic choice and won't understand any of this.

They're important conversations but people don't want to engage in them every second of their living lives. The point of entertainment is to be able to compartementalize and regulate.

If they do what you suggest, all the creativity that makes the platform attractive is going to flock to somewhere else.

Or people are just trying to not be reminded every second of their living lives that there's one conflict or another going on. TikTok is made in China and used worldwide. Not many things are relatable and relevant to a world wide audience.

That's fine. Not every platform has to work the same way and attract the same communities.

> "The C standard library provides malloc/free/resize"

It does not provide a `resize`. You're thinking of `realloc` on hosted environments.

Okay, but put the panels on rooftops, not over that nice greenery.