Viewing profile — benrazdev

why does an RSS feed aggregator even need ads in the first place?

I'll never forget walking through a tech store and seeing a HP printer that advertised itself as being "AI-powered". I don't know how you advertise a printer to make it exciting to…

My best guess is that the font I am using (WOFF2 variable font) might be tripping up the browser.

I agree with your point in general, but I would challenge the idea that tuples aren't something that is intuitive to explain (even in less than 30 seconds). Perhaps it's difficult …

Its not really a matter of logic, I guess. Writing `pub` is personally more annoying to me than writing `if err != nil`. I understand that most people don't like how capitalization…

I can't speak for other Rust programmers but I can speak for myself. I obviously enjoy programming Rust and I like many of the choices it made, but I am well aware of the tradeoffs…

Technically, with generics, you could get a Result that is almost as good as Rust, but it is unidiomatic and awkward to write: type Result[T, E any] struct { Val T Err E IsErr bool…

>that is, all the information that would be present in a typical Rust error handling scenario as well --- is encoded in the type tree of the errors. it's only present when you down…

From what the comments are saying I think you downcast with `errors.As` and then work on the underlying error type. But I don't know for sure.

>No enums? [...] We're stuck with magic numbers? In go you don't strictly need magic numbers because you can define constants: type Status int const ( IoProblem Status = iota // we…

Correct me if I am wrong, but does it not mean that they are type-erased though? The whole point of returning an interface is to perform type-erasure. If I have struct S { X int } …

>this is false. It's mostly false. Technically, if you use `fmt.Errorf`, then the caller can't get anything useful out of your errors. Types are promises. All the `error` interface…

>> difficulty of writing if err != nil >Literally the simplest way to deal with errors (cognitively and character wise). Since AI autocomplete entered the scene, typing this repeti…

My understanding is that using `error` as a return type performs type erasure and that the only information given to the caller is the value of the `e.Error()` function. I now unde…

Thanks for all of the comments! I want to clarify that I think very highly of Go as a language. I think it gets most things right. It's hard to introduce an abstraction into a lang…