วีดีโอ

unimportant note: the code at 1:18 is broken main.zig:6:19: error: use of undeclared identifier 'i' (exit status 1) it should be result += curr

I remember hearing that as a developer you're job is not writing code but providing solutions, and writing code is just a tool you use to to provide those software solutions. To provide a good experience you need to look and the end users needs and work from there.

i agree that zig is the future of systems programming [rust is trash btw], but for that to happen it needs to have a big and stable ecosystem, and to do that you need programmers who have a strong understanding of the past/present which is C.

Text on 27:30 is amazing! Just compare this transparent and friendly approach to something like J. Blow's suicidal suggestions. =/

cool project for learning all these inner workings of a TE

8:40 Reading the actual source code of the programming language is something I started doing on the regular since starting with Zig. It kind of indirectly tells me how the code should be written, while also explaining to me what it does.

whoever. came up with the citrus duck. THANK YOU

What I some times do @27:22 when I just dont wanna deal with type mismatches in testing, is set a comptime parameter to accept a type, which I send by doing typeof on the whateverI am trying to send to the function, and the actual parameters that the function will use will be set to that comptime type. I sometimes do the same for the return values ( from within that function )

U0 being one thing it is the same as 0! = 1 which makes perfect mathematical sense ( you can prove in more than one way, but set theory is usually used to prove it). Very easy way to think about it: there exists only one way to represent an empty set.

Perfect scope of clarifying zig pointers for programmers. I've dealt with slices, raw pointers, typed pointers etc. But I ran by accident into a slice type error and couldn't figure it out. I also found the memory ownership of sized arrrays unexpected, I thought they were just a typed pointer.

Very cool talk, thanks

best talk i've seen this year, thanks!

Really good video, thank you for making it and posting. I fixed a bug in a program I'm writing and I had no clue how my changes fixed it, this video explained exactly why it was broken in the first place and how my changes fixed the issue

Just use java and virtual threads

Treating everything as a batch is really super powerful. It is very similar to what Structure and Interpretation of Computer Programs says "everything is a list"

Zig and minimal js? Let’s go

cool!

Very interesting talk! But I feel like the title doesn't really match the content? Felt like it wasn't so much about abstraction (or over abstraction) as much as it was error handling, and just general C vs Zig comparison

We are looking for what??? 🤨 17:36

In our enterprise we are required to run Windows even though almost all of my work is on AIX via SecureCRT. I do have WSL2 Ubuntu. What are the chances I can run this and when?

I get the points about layers of abstraction and stacks of dependencies. But it's a real shame to illustrate this with a totally freaky Rust example. I mean: 1) I have created web servers in using high level libraries in Rust with bazillions of dependencies and none of them were anything close to that slow. 2) I see no reason why one could not write the equivalent of that 200 line C server in Rust for equivalent results and lack of dependencies. 3) Rust, C and apparently Roc give you exactly the same choice about how many layers of crap you have between your code and the OS or machine. The choice is yours not for example Rust's. Conversely you do not get that choice with needing V8 and a bunch of libs and an OS underneath, before you even start on the actual JS. modules one might use. I do agree that the explosion of dependencies that happens when people have access to a system that makes it passive, like Cargo or NPM, is disturbing and sometimes problematic. Go Zed editor by the way, been using for a few months now, fast and sweet.

❤Excellent talk, very relaxing vibes, thank you!

Sounds like Loris has never had good cheddar.

Brings back memories... A) a mark-and-sweep garbage collector is just one page of code and can be ok for non-real time, with much non-pointer data. B) combining allocation and memory mapping (to storage, to transport buffers) is a handy piece of toolkit to have, and not so much more work. Of course it restricts many options. Thanks for the presentation!

I got diagnosed in my 30s and when people ask about what meds are like, I pretty much always say it lets you decide to do something and then do it. An incredible ability to have.

So that memory alignment tricks from 2022 didn't help?

This talk was super valuable to me, thank you

thank you very much for this, really learned alot

Why on Earth would you make '\' syntactically important in a language designed for one-liners?

I recently read that ADHD can be related to kpu/hpu (metabolic disorder(s))

Ghostty is still in close beta.

zig is getting me back into low level code after decades of hiding from the crazy and old C preprocessor. Reading macro laden code haunts my dreams and tooling only helps me a little. I'm very thankful for this language :) <3

28:50 - could be "Alexithymia", but I'm no expert, I just googled

"I am just kinda some guy" is sincerely pretty inspirational

You made it to 10k 🎉

539 Upton Loaf

Thanks!

starts at 9:19

30:55 "We can read this code, but VERY few engineers out there could write it from scratch." Instead of saying why I hate this sentence, I am just going to cite Brian Kernighan here: "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it."

Great introductory talk about OSM editing!

I googled the characters immediately, "running shoes" was the final clue. Now watching the "Sneakers" for the first time (half-through, and it's amazing!). Best intro VSR, and another delightful presentation of Joran.

@22:40 if the function ( such as init ) only uses the single pointer is it automatically noalias?

I'm 100% agree that making a language server to work with comptime stuff is very very hard and changeling, for example after all these years we don't have a lsp for C macros but as I see many times that zig gurus break the rules of nature and making impossible a possibility, I think we are gonna have an amazing lsp when the core main goals achieved.

Ghostty seems really cool. I can't wait to start using the v1. Maybe becoming a beta tester could be interesting as well!

6411 Jovani Road

Watching Joran's presentations influenced my musical interests (not counting system programming) in the past years more than anything else. Another great one!

Spencer Coves

17:25 Wow, I should start doing that for my projects, e.g try and tell users what to do to get it to work

8:30 "I would rather do anything than write a couple lines of perl" LOL

Jackson Robert White Laura Johnson Helen