jackhalford

19 ms·

211.
by jackhalford 7y ago
Ok maybe I was user pointers wrong in Rust. And I must confess that I never really understood lifetimes either, however * I don't think that low level code needs to be "messy", and * I don't think that adding an abstract
212.
by jackhalford 7y ago
migration from 0.4 to 0.5 was ok. AFAICT there the big change for 0.6 syntax wise is the drop or varargs in favour of tuples. I'll take some time to do the switch when 0.6 hits but I'm confident it won't take long because of
213.
by jackhalford 7y ago
I don't follow JAI but maybe Jonathan Blow should try zig, it's a great fit for game development and I remember him mentioning that he wants a language that is fun to write in.
214.
by jackhalford 7y ago
this exactly, the language doesn't know about generics but having first class types + comptime allows you to do generics. Writing C feels like a chore now.
215.
by jackhalford 7y ago
> caring about the assembly output is a spectacular case of premature optimization I don't agree! at least for operating systems. Consider that some operating system code may be run a million times per second, on a million different
216.
by jackhalford 7y ago
OSDev can be hit or miss. All of the bootstrapping was done following this [0] tutorial for Rust, which translates easily to zig. For the more advanced parts you can find usefull ones in [1] or use the OSDev search bar. For even more advanc
217.
by jackhalford 7y ago
Hi, that's a great idea, it would be a good exercise for me especially. I always enjoy watching Andy's live zig coding on youtube.
218.
by jackhalford 7y ago
In general you'll find that zig is easier to read than Rust (see the first version of this project in Rust [0]) because it's a simpler language. For kernel programming this is even more so the case: * zig has native support for ar
219.
by jackhalford 7y ago
Hi, author here! I've just finished writing the pre-emptive multitasking [0](only round robbin though, nothing fancy). I'm currently writing an ATA driver [1], the idea is to implement ext2. I used to do this in Rust but I switche
220.
by jackhalford 7y ago
OSdev wiki is really the mecca when starting the build your own kernel. I've used it almost exclusively while building my own [1], thanks to this tutorial [2] osdev I have just finished pre-emptive multitasking! However the more a kern
221.
by jackhalford 8y ago
.ko is already used for kernel objects :(
222.
by jackhalford 8y ago
very cool to see such a powerful insight from userspace, although there's quite a few steps before doing the main loop. I had to google everything: ASLR, MTRR, frequency scaling. Thank you for commenting it so well!