Відео

anything beyond a primitive value in TOML is neither obvious or minimal. TOML kinda sucks. (even Tom admitted this)

i do not use ts. is there no way to use next.js with ts in tauri? with js it did not install next.js by default. it installed just react.

Got any resources for how to add SQLite?

that callback in setTime was a life saver !! subscribed ❤

Code please

1:32 aah yes, i definitely think that "non-python external libraries" should have been in their own category. the absence of this point makes this video kinda pointless for me...

hey guys does anybody knows how can we make the nextjs14 app routers work with tauri?

The nextjs template appears to have been removed.

Jason always seemed like the love child of a data structure and LISP - hard to read and too many keystrokes.

you lost me at array tables, not gonna lie xd amazing quickstart video btw

I've always been too lazy to read the specification, this video was fantastic.

4:50 if you meant to use regex for bare keys you shoild escape the last hyphen with a backslash

It is more close to INI, it would be better not call as '-ML' even it is an acronym of 'minimal language' Anyway it is further from the actual language.

❤

this video made me really like TOML!

3:21 creepy smile

Aside from array tables, I love everything about this

God I hate toml, using arrays/inner keys in it is absolutely terrible, and it doesn't support a lot of character escape sequences. If there's ever a way to get me to avoid updating a config file at all costs, make it in toml.

You just got a new sub! Simple and objective explanation!

Tom's language isn't all that obvious or minimal. JSON ❤

There's a lot I like about TOML, but its sections are not very intutive. I've designed my own format (kesh-lang/na). Still haven't made a compiler for it though. But you're welcome to have a look if you're interested in data notation formats.

toml is just. shitty json without the outer brackets and quotations around keys

toml is super easy, my only experience with it was like on cargo project and now i'm developing a project that involves parsing it with the tomlc99 library (the project is frogmake, it's still in early development and i'm working on it every day)

Array tables are cursed ...

Looks much less natural than yaml, especiales arrays of headers

When Go 1.20 was out, a lot of CI/CD pipelines broke, because the YAML parser interpreted the 1.20 as a number (so: 1.2 instead of 1.20). To avoid this, you had to write "1.20". YAML was blamed for this. I refuted this, pointing to the parser instead. When I used a YAML parser in Go, I got the string value 1.20 instead of a numerical one. Now I tried this with your TOML Visualizer. Same result. "1.20" is interpreted as string. 1.20 as number. YAML isn't worse than TOML. In fact, I'd rather read YAML since it's more natural for me to write it.

TOML is very good, i don't understand a lot of the comments. I'll take TOML over JSON any day. For once, JSON is much harder to read, heavier to write and parse, and pretty much requires an external library due to how complex it is to create a parser of...

What is common solution for stringification, since "there are different ways to represent the same data" ?

very bad

I think this format is unnecessary and JSON hierarchy is much more intuitive. It only looks prettier.

i've learned toml when configuring hugo config files. after learning more about it, i love it more than yaml, and somehow learned a bit of ini. thank you tom for making this

Lol "more readable than EVEN yaml" Dude speaks like yaml is most readable format! Yaml is one of least readable formats ever. In fact, less readable only binary serialisation!

Lol TOML is more like the glue-sniffing inbred cousin of ini and yml.

alright thats cool and all but I'm still using json

toml doesn't need to exist. first of all, who tf is tom? and how is his language "obvious?" granted yaml isn't obvious but it's more sensible than toml. it also does pretty much anything that you might want. sure the yaml spec is huge but you don't have to implement the whole spec if you don't need to. json is also ok for simple things and is about as obvious as can be. you only need to look at an example json file to pretty much figure out how it works. anything more complicated than passing data around or dead-simple configuration though and json falls flat on its face, but that's what we have yaml for. now this tom guy decides to throw his goofy format into the mix and we have one more silly config language that we have to know.

good one

Very stylish approach to a programming video haha, nice.

Watch at 1.25x speed

Give me yaml any day

Been using PDM for quite some time as I found poetries docs initially somewhat difficult to read and understand and I was new to python. (or even why you might use it, and then I started using Linux more frequently and understood lol) Perhaps I missed a convention with python file, naming conventions, but can you go into more detail or link me an article around the section about using a __main__.py as a file? I’m already in the habit of doing an ‘if name == __main__: block in main.py, but I’m not entirely sure what you’re doing here with the __main__.py file and all of that ❤

Tom is a genious

But why?

RIP agent Mulder of the SCP Foundation love the narration 👍

I love the lovecraftian presentation, it's so good lol.

5:20 You can write "please don't" all you want, but all I see is a convenient form to convert my Java property files into.

We have too many config languages at this point

I knew toml was bud but I didn't think it was this bad

Just use ASN.1 - it's a standard, flexible, supports a text format, as well as several binary encodings.

toml is an inconsistent piece of shit

I see several reactions where people prefer JSON over this, but there are things that JSON doesn't do that TOML does that are important for configuration files. The most important one being commenting. All features are superior over JSON for readability, you can make your files readable, and less ambiguity compared to YAML. I think it's mostly very important to understand where it's useful and where it isn't.