tail_exchange

il y a 10 joursdiscuss

A good UX and a user base. I had it on my phone, but uninstalled after a while because not a single person I know uses it.

tail_exchange

il y a 2 moisdiscuss

[dead]

tail_exchange

il y a 2 moisdiscuss

I do like React. It's still my choice even after trying other tools (including HTMX).

tail_exchange

il y a 2 moisdiscuss

Maybe I just have a bad taste for cars, but this looks awful. Uninspiring. Looks like a Tesla with a Ferrari logo.

Edit: I do love the analog buttons in the interior though. I despise those big screens with all the controls, and no tactile feedback.

tail_exchange

il y a 3 moisdiscuss

I’m glad you recovered, Cliff! I got a signed Klein Bottle from you as one of the first things I did once I moved to North America about a decade ago. It’s sitting proudly on my bookshelf.

tail_exchange

il y a 3 moisdiscuss

For greenfield projects, I agree. It gets the job done, but PHP would never be my choice for a new project. Bun seems like a much better choice in pretty much every criteria.

tail_exchange

il y a 3 moisdiscuss

Iran is far from being the good guys, but I cannot see the US as the good guys here either.

tail_exchange

il y a 8 moisdiscuss

I was very skeptical of Go when I started learning it, but it quickly became my favourite language. I like how simple but powerful it is.

If I had a magic wand, the only things I would add is better nulability checks, add stack traces by default for errors, and exhaustive checks for sum types. Other than that, it does everything I want.

tail_exchange

il y a 10 moisdiscuss

It's very ironic that the way they could have made money was the simple, but boring one: buying and holding bitcoin. Being a shitcoin day-trader is much more exciting though, and that's how they lost all their money.

Maybe that's also what will happen with AI investors when the bubble pops or deflates.

tail_exchange

il y a 10 moisdiscuss

It's only a problem for the GOP if Dems do win elections again. Judging by how things are progressing, it may not happen anymore. They have complete control over everything.

tail_exchange

l’année dernièrediscuss

No. Like always, there will be visual accessibility features such as high contrast, reducing screen motion, dark mode, and reduced transparency. I never had to use them, but according to a family member who is blind, Apple is excellent in terms of accessibility.

tail_exchange

l’année dernièrediscuss

The opposite for me. I'm so tired of the boring and uninspiring flat design, that Apple may have convinced me to get an iPhone next time I upgrade. I don't even notice Android updates anymore, the past 3 or 4 just look and feel the same.

tail_exchange

l’année dernièrediscuss

I'm on the other camp. I'm so tired of the boring flat design, I'm actually considering switching to an iPhone.

tail_exchange

l’année dernièrediscuss

Perhaps something like this?

    result := InvokeWithErrorLogger(
        func (err error) { // Error handler
            incrementMetric("foo")
            log.Error("bar")
        },
        addTwoNumbers, a, b,
    )

But the problem is that this approach is not better than just writing this, which doesn't need any new fancy addition to the language:

    result, err := addTwoNumbers(a, b)
    if err != nil {
        incrementMetric("foo")
        log.Error("bar")
        return fmt.Errorf("addTwoNumbers(%d, %d) = %v", a, b, err)
    }

Hence why all the proposals ended up dying with the lack of traction.

tail_exchange

l’année dernièrediscuss

This doesn't actually makes the process simpler.

Error handling in Go is not just writing "if err != nil { return nil, err }" for every line. You are supposed to enrich the error to add more context to it. For example:

    result, err := addTwoNumbers(a, b)
    if err != nil {
      return fmt.Errorf("addTwoNumbers(%d, %d) = %v", a, b, err)
    }

This way you can enrich the error message and say what was passed to the function. If you try to abstract this logic with a "Handle" function, you'll just create a mess. You'll save yourself the time of writing an IF statement, but you'll need a bunch of arguments that will just make it harder to use.

Not to mention, those helper functions don't account for cases where you don't just want to bubble up an error. What if you want to do more things, like log, emit metrics, clean up resources, and so on? How do you deal with that with the "Handle()" function?

tail_exchange

l’année dernièrediscuss

> there is literally nothing you can do with errors in go except bubble them up, log them, or swallow them

You can also add additional context to the error before bubbling it up. But yes, that part of the point. Instead of bubbling them up, the programmer should instead reflect on whether it is better than just log and proceed, or completely swallow them. This is what error handling is about.

tail_exchange

l’année dernièrediscuss

> In the meantime, tariffs are raised on every country to gauge which side they are on

Why on earth would you be on the side of a country like this? Why we should be an ally of the US right now, if Trump can't even uphold agreements he signed himself 5 years ago? What guarantees do we have that, as soon as we decouple from China, the US won't treat us as a vassal because we gave up our only alternative? The only rational choice is to either be neutral or ally with China.

tail_exchange

l’année dernièrediscuss

It's astonishing how much money they are pouring into a product that is just seems like a worse version of VRChat.

tail_exchange

l’année dernièrediscuss

Very fair point.

tail_exchange

l’année dernièrediscuss

The government is clearly incapable of stopping him, so in the end, it doesn't really matter if it's illegal or not. He'll do it because he can, and he'll get away with it.

tail_exchange

Submissions

Telegram Founder Durov Allowed to Temporarily Leave France

Stripe BFCM Live

comments