[โ€“] 3 points 5 months ago (1 child)

Don't hesitate or overthink it. Just dive headfirst into it. The day you start is the best moment. The thing you chose to do, is the best.

Learn by playing around. Play to your strengths. Dabble with coding, sound, graphics, mechanics, and figure out what gets the fire going. Feed that fire.

When you've had a bit of taste, try to complete a small simple project. This is surprisingly difficult! Learn to remove features and complexity, simplifying until you can actually finish the game.

  • source
  • [โ€“] 1 point 5 months ago

    I am perplexed that they refuse to acknowledge some pretty deep issues I see every major Go project run into:

    • There are corner cases where it is literally impossible to check of the value of a type-param interface is nil.
    • Type-params on methods
    • Type-safe enums
  • source
  • [โ€“] 15 points 6 months ago (1 child)

    No default gnome app will be able to toggle that default. You can hack it in gsettings.

    And worse, the fact there is a setting means that only the default will be tested. The feature will slowly but surely bitrot. In a few years we'll see a proposal to remove it entirely. This is how software development works.

  • source
  • parent
  • context
  • [โ€“] 28 points 7 months ago

    Many moons ago I did a project at uni where we implemented elliptic curve cryptography in Java and released it as open source. Unsurprisingly, we had no idea what we were doing. Some years later I get a random mail from someone using it on some embedded system...

    I don't want to know, and I fear that ist is paramount that I maintain plausible deniability ๐Ÿ˜‚โ™ฅ๏ธ๐Ÿ™

  • source
  •  

    In the original proof of concept for ranging over functions, iter.Pull was implemented via goroutines and channels, which has a massive overhead.

    When I dug in to see what the released code did I was delighted to see that the go devs implemented actual coroutines to power it. Which is one of the only ways to get sensible performance from this.

    Will the coro package be exposed as public API in the future? Here's to hoping โ™ฅ๏ธ

    view more: next โ€บ