• 49 Posts
  • 5.5K Comments
Joined 3 years ago
cake
Cake day: August 17th, 2023

help-circle
  • As a passionate Golang hater, I can gladly explain!

    • It’s not just the repeated if err != nil, even though that’s already bad enough. But the really fucked up part is the := bullshit. It makes moving code around unnecessarily annoying, and it’s telling that few other languages share Golang’s approach.
    • The lowercase/uppercase rules for private/public stuff is theoretically not a horrible idea, but it makes the code look much more inconsistent. I find _ much easier to read, and this leaves upper/lower to signal other details. But I see that this is mostly personal preference.
    • Fairly basic operations take much, much more code than they should (e.g. deserializing JSON while handling extra args, or basic functional operations - though that should change sooner rather than later with the new generic methods, right?)
    • The decision to initialize every non-pointer primitive with the “bottom value” (or whatever it’s called again) makes sense in isolation, but it’s really unfortunate that they don’t support additive types, because this means a bunch of common tasks need to use pointers, and unfortunately the type system is worthless when it comes to preventing segfaults caused by bugs with pointers.
    • I find that most Go libraries have basically no documentation, if you’re lucky you get an example that might vaguely be related to whatever you want to know. I’ve had much better experiences in other languages.

    All in all IMO most Go code is 5x longer than necessary to actually express itself in a readable manner, all because the language still doesn’t have proper error handling or generic support (until recently at least). At the same time it’s fairly inflexible, the type system is still shallow and basic, and it’s still way too easy to shoot yourself in the foot.

    The only good thing Go has going is the single file deployments, but I’ll gladly spend one hour of every remaining day of my life setting up containers, if it means I never have to touch anything Go again.












  • FooBarringtontoLemmy ShitpostThe Matrix
    link
    fedilink
    arrow-up
    4
    ·
    12 days ago

    Hm, I think it does make the message stronger. If a single event (development of sentient machines) leads to our downfall, it’s easy to shrug it off as “bad luck”, because who could have foreseen it back then?

    But if we had multiple chances to correct course and we kept fucking up, it removes any doubt that it’s a human flaw, which means “humanity must reflect and change, or this is the inevitable conclusion”.


  • AI could be useful if it could orchestrate more complex tasks that the relevant apps don’t natively support. But of course that’s not what we’re getting.

    I use lots and lots of timers every day to structure my chores and work. For example, I’d sometimes love to be able to start one timer, and have another one set to automatically start as soon as I stop the ringing from the first (which might take a few minutes).

    Very simple requirements, but specialized enough that I’d have to write it myself. But I can’t see phone AIs supporting something like this in this decade.



  • Interesting, as someone who didn’t read the book,

    spoiler

    The chase sequence was one of my favorite parts! A few reasons:

    • It didn’t feel zany at all to me. I was focusing only on Ryland and felt his panic, to me his actions looked like an animal trying to run from certain death.
    • The betrayal by everyone he worked with during that time made it a much more intense gut punch for me. Especially Carl.
    • And most important: It felt true to his character. If he faced it stoically, it would have felt like fake Pathos to me. Instead it was a wonderful display of character growth (going from having to be dragged onto the ship to save billions, to risking his life and future to save his buddies’ people).