• 0 Posts
  • 151 Comments
Joined 3 years ago
cake
Cake day: August 17th, 2023

help-circle


  • I’m not sure I agree. The real world is never going to run perfectly, so some slack must be included (either by adding buffer time to schedules, or using the way you mention). Of course there are examples like Japan that have done a really good job at optimizing these systems, but you won’t be able to successfully apply their approach to every country. Some locations require more work to achieve this, others require less.

    Generally the closer you get to an “ideal” performance, the more costly every further improvement gets. If 7 min isn’t reasonable, what number would be? Say we manage to shave off two minutes, at twice the cost of the current system. Is that really worth it?

    The better approach is to include reasonable slack time in people’s train schedules, while increasing frequencies so missing a connection doesn’t result in hour-long wait times.


  • Palpatine secretly controlled the whole trade blockade around Naboo as well as directing Count Dooku, Darth Maul and General Grievous among many other shenanigans.

    To compare it to German history: Palpatine didn’t just light the metaphorical Reichstag on fire, my Geschwisty. He used an armada of tanks assembled into a Voltron-style robot that shoots Flammenwerfer capable of turning air into fuel.














  • 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.




  • It’s cool that you enjoyed it! But there’s no need to pretend that this is a binary choice. Guardians of the Galaxy is also capeshit with a stoic woman, yet IMO Gamorra is a much more interesting character than Captain Marvel.

    I also liked many parts of the movie, but some other parts were big enough misses that I’m not really interested in rewatching.