Whoa, having twitch chat as captions is amazing!

I would really like to see the eepers vods, as I didn't get to catch most of the streams. Love watching grumpy zozin

valuable content shouldn't be kept hidden and a lot of us can't make the schedule of watching streams. i think you should publish all the eepers episodes.

2:39:00 cool idea. not that it matters, but that won't be turing machine anymore. Such a machine would have infinite alphabet and infinite number of states. Infinite state machine with recursive states would be easily simulated in finite state machine using a piece of tape for state simulation. This could go further. Instead of [a+b] you could have result of any other turing machine lol. If Integer arithmetic and so on wouldn't be a magic part of the language, but something that has to be provided as another tula program, that would quickly kill any danger of being useful.

You have to look into Product types! "let Pairs = Integers x Integers" is pretty pog

Now I'm wondering how many people know of the vulnerability of calling programs with execv*() since the given argument list may not actually include the program name. Accordingly, you should probably be using env::current_exe instead of env::args for the actual program name. Also, for formatting, especially when using line numbers, I always pad out to at least 4 digits as a default, whether using spaces or 0's to pad. Looking at it written out, I think I understand better why so many languages eschew using = for named parameters, because it looks cursed, but even more so in a formatting print function. For my own language I opted to do a sort of f-string type thing like Python, but I made every string an f-string. Whether you're just assigning to a variable or printing, you could just do "${ 4:line_count}" and it would do a space padded 4 digit representation for the current line count. So my generic print function just takes a flat set of values and does no printf() style processing, but I do also provide my own printf() as well. I also don't like the concept of todo!() that Rust uses, nor that it doesn't warn by default on shadowed variables. Additionally, it is far too noisy of a language. It's like they're aiming for copying C++ but in their own weird syntax that's impossible for a newbie to understand and will make skill transfer more difficult.

pretty scary preview

We need Tsoding merchandise!!!

Thank you....

Thats why I just use nightly and deal with it, all these "unstable" features, like 99% of these features are fine, just have to read through the issue and ensure it doesn't segfault your programme. It would be interesting to introduce some level of stability between unstable and stable, where it allow you to use the feature (behind a flag) on the stable compiler, but retain the freedom to change or remove the feature if circumstances demand it.

" Parsing Lips with Rust "

Can you elaborate or link episode for reasons of hate for Lisp and Rust?

russian programmer screams at rust

определенно нужно выложить на ютуб весь путь к рабочей туле, очень интересно сесть посмотреть, но я не могу быть на стримах

Isn't it just reverse Forth parsing with extra steps and parenthesis counting?

The subtitles : 💀

Am I high or is tula repo on github is just a README?

now parse rust with lisp

Rust, the language of the chosen people

31:14 mah vim can do (most of) dat, but I feel insecure now :-|

Zozin, use more abstraction.

SHUT IT DOWN

Rust becoming popular?