[–] 3 points 8 months ago (2 children)

VSCode is Electron, i.e. a webpage, so it's not hugely surprising that they opted for the natively supported JavaScript Object Notation. And also shows that they don't care for using the right tool for the job to begin with.

Personally, I much prefer TOML over YAML, because it does not have significant whitespace, and because you can read the spec in a reasonable amount of time. It just has so much less complexity, while still covering the vast majority of use-cases perfectly well.

  • source
  • parent
  • context
  • [–] 3 points 8 months ago* (last edited 8 months ago) (1 child)

    I'm only being pedantic. Toml is not bad. Yaml I personally don't like because I don't approve of semantically required whitespace but I know I'm in the minority there.

    • It's not the norm in smaller companies, but big companies can use config servers where an app will retrieve its config on startup over the network. To be fair, I think they fall back to a platform specific encoding though.
    • Better hope it's built in. I don't remember the last time I verified a Content-Length was accurate. Also this generally applies to networking; disk writes don't get this same verification especially if a process is killed mid-write.
    • True point, no real notes. I've recently been dealing with streaming JSON for AI, it's SOO verbose for the few tokens that come across in each message. I don't know how gRPC wasn't chosen, or at least made an option, but oh well.

    You make good, valid points and I know I'm talking about edge cases that require the stars to align to break. It reminds me of an old, not-quite-relevant-but-oh-well saying "a 'one in a million' chance at 1GHz happens every millisecond." The law of large numbers isn't always on our side.

  • source
  • parent
  • context
  • [–] [S] 4 points 8 months ago

    Right, it's the lack of any double checking that's shocking. I use LLMs to make mermaid diagrams of code all the time, it's super useful, but you have to actually read through what it generates.

  • source
  • parent
  • context
  • [–] 3 points 8 months ago (1 child)

    I think throwing up a slop chart like this is incredibly lazy for a company to post. They almost always get something wrong or invent stuff.

    If you are having a conversation with someone about a topic and need something kinda quick, and sorta accurate to help explain something in a pinch, slopcharts aren't useless. I've generated a couple based on niche manuals/handbooks. Probably better tools for the job, just the thing I happened to reach for.

  • source
  • [–] 1 point 8 months ago

    Why forward instructions to an artist and wait when you can forward it to AI and get it instantly.

    It would be very easy to make.... But not as easy as describing what you need to AI and clicking a button.

    I consistently ask LLMs things that I could Google; it's just massively convenient.

  • source
  • parent
  • context
  • [–] 2 points 8 months ago* (1 child)

    We just document that this is how you write the config file:

    [network]
    bind.host = "127.0.0.1"
    bind.port = 1234
    
    # etc.
    

    And that seems straightforward enough. Yeah, technically users can opt to use inline tables or raw strings or whatever, but they don't have to.

  • source
  • parent
  • context
  • [–] 4 points 8 months ago (3 children)

    Well, you can still decide how much of the TOML features you actually use in your specific application. For example, I'm currently involved in two projects at $DAYJOB where we read TOML configurations and we don't make use of the inline tables that OP memes about in either of them.

    Ultimately, the big advantage of TOML over INI is that it standardizes all kinds of small INI extensions that folks have come up with over the decades. As such, it has a formal specification and in particular only one specification.
    You can assume that you can read the same TOML file from two different programming languages, which you cannot just assume for INI.

  • source
  • parent
  • context
  • [–] 4 points 8 months ago* (4 children)

    INI can be nicer for non-techies due to its flat structure. However, TOML seems to be in an awkward spot: either I want flat approachable (I'll pick INI) or not (I'll pick JSONC). Why would I want a mix?

  • source
  • parent
  • context
  • [–] 1 point 8 months ago

    I've seen so many game jam entries where the code is like this. Delicately balanced and using so many assumptions to just get the thing out the door.

    It's funny when they decide to make a full game out of it and realize that it's gonna take them 6 months just to undo the tech debt of the original "demo"

  • source
  • parent
  • context
  • [–] 39 points 8 months ago* (last edited 8 months ago) (2 children)

    Counterpoints:

    • TOML is intended for configuration, not for data serialization, so you shouldn't be sending it over the wire in all too crazy ways anyways.
    • Most protocols will have a built-in way of knowing when the whole content has been transferred, typically by putting a content length into the header.
    • Having to wait until the closing } or ] can also be a disadvantage of JSON, since you cannot stream it, i.e. start processing the fields/elements before the whole thing has arrived. (You probably still don't want to use TOML for that, though. JSONL, CSV or such are a better idea.)
  • source
  • parent
  • context
  • view more: ‹ prev next ›