Orchard Dweller

Пікірлер

@Takatou__Yogiri 3 ай бұрын

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.

@Imaginativeone_DF 4 ай бұрын

Got any resources for how to add SQLite?

@aadityavirsingh3485 4 ай бұрын

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

@manjirosanoindo1894 4 ай бұрын

Code please

@yash1152 7 ай бұрын

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

@FranzAllanSee 5 ай бұрын

Try rye. Been playing with it recently 😁

@das_daily_ 7 ай бұрын

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

@Imaginativeone_DF 8 ай бұрын

The nextjs template appears to have been removed.

@scottmiller2591 9 ай бұрын

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

@hrznn 9 ай бұрын

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

@henriquedante 9 ай бұрын

Off topic: the stress syllable of integer is the first: ínteger

@arlaxia 9 ай бұрын

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

@rahulr9539 9 ай бұрын

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

@marksmithcollins 9 ай бұрын

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.

@AnweshAdhikari 10 ай бұрын

❤

@Im_Ninooo 10 ай бұрын

this video made me really like TOML!

@gregoryholder2423 10 ай бұрын

3:21 creepy smile

@hundvd_7 10 ай бұрын

Aside from array tables, I love everything about this

@casraf 10 ай бұрын

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.

@ti4go 10 ай бұрын

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

@kale.online 10 ай бұрын

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

@ximono 10 ай бұрын

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.

@sacredgeometry 10 ай бұрын

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

@nzeu725 10 ай бұрын

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)

@Linuxdirk 10 ай бұрын

Array tables are cursed ...

@ClementMasson 10 ай бұрын

Looks much less natural than yaml, especiales arrays of headers

@DaVyze 10 ай бұрын

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.

@hrudyplayz 10 ай бұрын

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

@orcharddweller 10 ай бұрын

I think you meant YAML, JSONs parser is much simpler than TOMLs, especially for writing.

@hrudyplayz 10 ай бұрын

@@orcharddweller Even though YAML is indeed the worse of them all, it's indeed much easier to implement a TOML parser from scratch than a JSON one. Mainly because TOML mostly separates stuff into different lines and has a less complex syntax to parse overall.

@orcharddweller 10 ай бұрын

@@hrudyplayz Hmm, I've never implement neither of them, so I might be talking out of my ass, but I've done a bit of parsing in my life and just looking at this: www.json.org/json-en.html, the grammar feels much simpler than TOML. Also TOML has inline arrays and inline tables, which are in essence a limited version of JSON. So for parsing TOML you need to be able to parse a lobotomized version of JSON, but that's not necessary the other way.

@sergeikulikov4412 10 ай бұрын

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

@orcharddweller 10 ай бұрын

Its tricky, because in most cases you want to preserve the original style and comments. Poetry for example uses tomlkit, you can check out their approach here: github.com/sdispater/tomlkit In general, I’d probably avoid writing with TOML it unless you really need it.

@1schwererziehbar1 10 ай бұрын

very bad

@gabrielmachado5708 10 ай бұрын

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

@cindrmon 10 ай бұрын

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

@marloelefant7500 10 ай бұрын

What are the advantages of toml over yaml? Like you, I'm currently starting out with toml by configuring hugo config files, but I found it very not obvious. Yaml, on the other hand, I understood immediately on the first look (with the knowledge of json).

@cindrmon 10 ай бұрын

@@marloelefant7500 i guess for me is that you don't have to worry about whitespace indentation in toml (even though in hugo there are some docs that show whitespace indentation, but i choose to ignore it). also having nested selectors in which for yaml, you'd have so many indented lines to select a specific, deeply-nested key, while in toml, you just put it in dot notation making it shorter and more concise. tbh i don't toally hate yaml in general, as it is one of the morely used configuration specs besides json, and it does have its own advantages, but given the option for usage of toml, i would gladly use it.

@urisinger3412 10 ай бұрын

Toms a genius!!

@yaroslavpanych2067 10 ай бұрын

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!

@RealCheesyBread 10 ай бұрын

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

@xdMatthewbx 10 ай бұрын

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

@harleyspeedthrust4013 10 ай бұрын

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.

@manishmg3994 10 ай бұрын

good one

@VHenrik007 10 ай бұрын

Very stylish approach to a programming video haha, nice.

@poisonouspotato1 10 ай бұрын

Watch at 1.25x speed

@Liamnissan22222 10 ай бұрын

Give me yaml any day

@Hellbending 10 ай бұрын

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 ❤

@orcharddweller 10 ай бұрын

__main__.py is the file you want to use when you need an entrypoint to your program. It's so that you can run it with python -m module_name instead of python -m module_name.main here's the docs: docs.python.org/3/library/__main__.html

@Hellbending 10 ай бұрын

@@orcharddweller having a quick skim through the docs. It seems like this is more specific to packaging things onto pypy or for the building of pulling packages down, that along the right lines? I’ve always just done python(the interpreter) and then main.py and then at the bottom of main.py I’ll have an “if name main” block and then just call main with any runtime specific things for the JIT. TIL - it’s not just a convention haha cheers bro

@orcharddweller 10 ай бұрын

There's a million ways to run your stuff in python (which imho is a bad thing). Its fine to just run a script file, but then you have to make sure that your dependencies are properly installed, and you might end up with some very subtle bugs with your imports unless you're really careful. Running scripts as modules means you have to adhere to python packaging rules. And that's a good thing, because you can expect all the things you build to just work, and you have some rules to follow that will most likely work with all the toolings that you potentially use.

@juniorceccon 10 ай бұрын

Tom is a genious

@khatharrmalkavian3306 10 ай бұрын

But why?

@90hijacked 10 ай бұрын

RIP agent Mulder of the SCP Foundation love the narration 👍

@ratfuk9340 10 ай бұрын

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

@D0Samp 10 ай бұрын

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.

@sm5304 10 ай бұрын

We have too many config languages at this point

@DaverSomethingSomething 10 ай бұрын

Still way better than it used to be when everyone invented their own thinking parsing was a trivial thing.

@StarOnCheek 10 ай бұрын

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

@lhpl 10 ай бұрын

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

@D0Samp 10 ай бұрын

That said, that one standardized text format is an XML transformation, if you plan for a text-first use case like a configuration file you might as well use XML directly. The most common "text" form of ASN.1 that users encounter regularly is probably Base64-encoded BER.

@lhpl 10 ай бұрын

@@D0Samp While XML certainly is an encodin scheme for ASN.1 defined data, I was thinking of the possibility of representing example data in ASN.1 itself. It is possible to do so, iirc. (In practice, nobody would want to do so of course, as then you'd need an ASN.1 compiler to parse configuration files.)

@guai9632 10 ай бұрын

toml is an inconsistent piece of shit

@LaPingvino 10 ай бұрын

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.

@lhpl 10 ай бұрын

You do know that the absence of comments in JSON is meant as a _feature_ ?

@orcharddweller 10 ай бұрын

Yup, those are different formats, and while I don’t believe TOML is flawless, it has certain features that make it better than JSON for the job its supposed to do.

@ShadowManceri 10 ай бұрын

Variants of JSON like JSONC and HJSON also include ability to comment. I don't think JSON is that great for config file as long it needs to be edited by a human. It's rather clunky to use the moment you go into complex structures. But if it's just simple one level object with few keys then it's a simple solution to a simple problem. Lack of comments still is kind of big negative for config files especially.

@CoolerQ 10 ай бұрын

JSON is really a pain because of the strict formatting/lack of comments, but what is the "less ambiguity compared to YAML"? I've never found YAML to be ambiguous.

@lhpl 10 ай бұрын

@@CoolerQ no?

Ең жақсы KZbin

Пікірлер