HN user

OvervCW

95 karma
Posts0
Comments34
View on HN
No posts found.

There is: your browser or other type of client does not know it can repeat a POST request if it fails, whereas a QUERY request can be freely repeated in case of errors.

Claude Fable 5 1 month ago

One does not need to be able to create it themselves to evaluate if the output is correct. Consider for example that you can easily determine if a meal tastes delicious without being an expert chef, or the fact that NP problems are very difficult to solve but make for easily verifiable solutions.

Copy Fail 3 months ago

Any program on your computer can just run "sudo" to escalate itself.

unless the label is something too low signal to predict

Also, crashes are statistically rare events on arterial and local roads, so it can take years to accumulate sufficient data to establish a valid safety profile for a specific road segment.

That is exactly what this article is about.

I wouldn't be surprised if they did this to lower the support workload, since I have several 2.4Ghz devices that fail to connect to WiFi at all if I put both bands on the same SSID. I intentionally separated them for that reason and portable devices like phones know how to switch between multiple SSIDs based on signal strength anyway.

In my experience Chrome does not just load faster, but it also uses less memory than Firefox because of its more aggressive tab hibernation that is enabled by default.

On my laptop I had to switch from Firefox to Chrome because it kept filling up all of my RAM resulting in other applications crashing.

Nano Banana Pro 8 months ago

How would this stop people from using their iPhone to take pictures of AI generated images?

In what way is it NP-hard? From what I can gather it just eliminates nodes where the pod wouldn't be allowed to run, calculates a score for each and then randomly selects one of the nodes that has the lowest score, so trivially parallelizable.

Go subtleties 9 months ago

Did I add explicit checks for all the errors my function calls might return?

You can check anything with a linter, but it's better when the language disallows you from making the mistake in the first place.

You can forget to use `with` in Python, I guess that's also C now too eh?

When using `with` in Python you don't have to think about what exactly needs to be cleaned up, and it'll happen automatically when there is any kind of error. Consider `http.Get` in Go:

resp, err := http.Get(url)

if err == nil { resp.Body.Close() }

return err

Here you need to specifically remember to call `resp.Body.Close` and in which case to call it. Needlessly complicated.

Then stop writing spaghetti and use a higher level abstraction like `x/sync/errgroup.Group`.

Why is this not part of the standard library? And why does it not implement basic functionality like collecting results?

Go subtleties 9 months ago

No need to talk about generics when we can talk about something simple like the inability to implement type safe enums in Go.

Go subtleties 9 months ago

They are similar in the sense that there are very few abstractions, relying on the programmer to reimplement common patterns and avoid logical mistakes.

You have to put thought into such things as:

- Did I add explicit checks for all the errors my function calls might return?

- Are all of my resources (e.g. file handles) cleaned up properly in all scenarios? Or did I forget a "defer file.Close()"? (A language like C++ solved this problem with RAII in the 1980s)

- Does my Go channel spaghetti properly implement a worker pool system with the right semaphores and error handling?

Go subtleties 9 months ago

In this specific blog post I suppose only "Ranging Directly over Integers" counts, but I was more generally referring to the introduction of features like generics.