วีดีโอ

I'm loving your videos man

are the stack devs really so full?

I really enjoyed watching the epiphanies you encountered and was amazed at the speed at which you pick up the language. I think watching you figuring out the neat parts of the language was more satisfying then learning it myself, because you have a deeper understanding of the implications of the language features.

Love your video's but I have stopped watching them because the constant moving maze above your head really triggers my Asperger and ADHD to a point where I can't follow along or I have to concentrate so hard that I tire out on these long videos. I wonder if you would consider removing it?

Mind giving me the skinny on the "Zig on the client" part? Are you somehow transforming Zig to JS, or to whatever JS is being transformed(compiled/interpreted, whatever) when Firefox is executing that?...

what’s up what’s up

What libraries are being used in your terminal? Especially for the file handling?

dead beef is a funny address... you got my clickthrough just based on that.

What is this thumbnail. LOL

Thank you and a wonderful zig series

02:12:55 Using last_insert_rowid() is a mistake I think. In some cases there is no row inserted and it doesn't return something sane. This resulted in us saying "hey I have this session ID and it belongs to this user", but the user was invalid, which made the join invalid, etc. I've adjusted off screen to use the RETURNING clause in sqlite and parse the id out of it

Sweet!!

What happens when write a comment

failable is the new fallible

Seconding a comment I saw on an earlier video-I would absolutely love to watch a 20 minute summary of your projects, either as a single final summary or as intermittent updates. Your projects are really awesome to see! The 2 hour long videos are challenging to keep up with, though.

Cool stuff

This is perhaps the most complex way to integrate OAuth nowadays. I love it.

hell yeah

Thanks!

Thanks!

01:38:15 It's actually possible to fix this by just inverting the dependency order. E.g. instead of HttpConnection owning something that gives it responses to write, have a specific connection own an HttpConnection and forward polls to it. See github.com/sphaerophoria/ball-machine/blob/dcc4ec5b03435d00b190dfbfbff2be55195419eb/src/http_test.zig#L8 as an example (WIP commit, will probably get garbage collected at some point)

crazy man. been watching your videos recently. mad respect

it really is terrible, but that's web dev

I've implemented OpenID in work settings like 4-5 times and I'm still just as confused as you are to be honest

only one whats up, the whats up are decreasing per video

This channel is a blessing for learning more than just the basics of zig. Youre a legend @sphaerophoria

Hello, I like your videos and I learn by watching you program and explain things, I love your content. I wanted to ask you a favor, which is to zoom in on the code, there is a lot of empty space and I don't see the code close enough... You can take a look at how a guy does it with content similar to yours, called "tsoding", if it's not a bother, put the code in the largest terminal, that is, zoom in. Thank you! Sorry if I wrote something wrong, English is not my first language and I translated it with the translator. Thank you so much!

i haven't watched the streams in entirety so might have missed it, but i'm curious why you're not using websockets for this? the epoll implementation would still be a cool learning experience, but the protocol itself would be better suited for the task than HTTP (as i understand it). love the series (and your videos in general) btw, keep it up :)

Great video! happy to find someone doing interesting things in Zig

I had a couple post-stream realizations... 1. We can give callback data directly to an epoll instance if the handler has a stable memory location. We can create a item pool that is basically a std.ArrayList with a list of IDs that can be reused and that simplifies a lot of the code 2. It makes a lot more sense to just register a single handler that handles both input and output for a given socket. Again this simplifies a lot because we no longer need the double indirection of file descriptor -> list of callbacks. This also means that each individual callback does not need a specific id 3. If we return a value from our epoll callback that says "I am finished, please delete me", that simplifies a lot of stuff as well. We can just buffer all deletions until we aren't iterating anymore which is pretty nice 4. Epoll links to files are automatically closed if the file descriptor is closed, we don't actually have to unregister connections if we're careful Latest and greatest at github.com/sphaerophoria/ball-machine/blob/526a78fe5aa027e366c6897002313b7438e665db/src/event_loop.zig (note may disappear after some future git gcs, but by that point there should be something in master)

Amazing video, currently watching still. I'm pretty new to this stuff but I think node.js uses libuv which is a library that uses epoll/an event loop. When there isn't any work left to do, the loop ends and the node process exits. My question is...when you start a web server, does it add a file descriptor to the list of fds and that fd stays there indefinitely until you close it when doing ctrl-c or something in the terminal? In other words, how does a web server keep the event loop indefinitely running?

Thank you for such consistency in creating this quality content. Though new to zig, these are super helpful.

01:25:35 Is ``` var connection = try self.server.accept(); var echoer = TcpEchoer.init(self.alloc, connection) catch |e| { connection.stream.close(); return e; }; ``` equivalent to ``` var connection = try self.server.accept(); errdefer connection.stream.close(); var echoer = try TcpEchoer.init(self.alloc, connection); ``` or am I misunderstanding `errdefer`? On a side note, `errdefer ` can capture error. Might be useful for lazy catch all error logging.

Bro can you share the github repo of the project

WIP commit (that may end up deleted in the future) that really slims down the interface and fixes some of the uglyness around the registration stuff github.com/sphaerophoria/ball-machine/commit/fb995b3db2ae66eccde001dd25577479346e157e

Spending more than an hour learning how to traverse a tree in Zig. 🙄

There is a lot of good knowledge here. Zig to wasm, rust to zig, zig to rust, zig to C. But all of it is 2 hours plus 😢😢😢.

whats up whats up whats up

I played with an alternative method today and it worked really well. * Copy paste structs from zig to C header, mark structs as extern in zig * Write C bindings API by hand * Write a comptime function that asserts that structs are the same. Struct size, field offsets, struct alignment, etc. * Write a comptime function that asserts that all exported functions have parameters and return types that match according to previous bullet * Use the zig types in the bindings impl file

Guru programmer at work! Amazing!

You know you could also run :LspRestart to restart the language server.

i’m so glad i found this channel

so crazy that that zig searches for dependency loops with DFS(basically a stack) but doesn't tell you either the stack or the duplicated value when it reports errors

I remember zig having -femit-h at one time.

I love your videos man, thanks for making them

I can't read anything when you scroll around so fast like you do. Just FYI

@sphaerophoria There is a great talk done by a core maintainer on Zig exactly about the memory layout optimizations for the compiler. I highly recommend it. Andrew Kelley - Practical DOD. Its on Vimeo, I don't think youtube lets me link it

Significant code cleanup (wip branch, git garbage collection may delete in the far future): github.com/sphaerophoria/ball-machine/commit/2ae83498847120d120952917a78e14231307dfcd

whats up whats up

That was fast, the stream just happened