delta64

It's slightly odd to say 'wow, epoll can wait on any type of kernel handle, like timerfd and signalfd!' given those *fd interfaces were added just for select/poll/epoll. Strikes me as remarkably ugly design...

I've long thought about these kind of OS designs, and what great features they can enable (such as time travel debugging). But the non-determinism introduced by inter-CPU interactions is a fundamental limitation, hence the need to run everything on a single isolated core.

One day(^TM) I'm really keen to design a multi-core CPU architecture that allows for deterministic message passing between cores in such a way that you could get this kind of software working with true parallelism.

Why would static linking be incompatible with `dlopen`?

Sure, but I think '== might be a function call' is a lot less confusing than '== sometimes compares for equal value and sometimes doesn't'

How is that any different to some opaque method call? By the same logic `a.equals(b)` might be doing something funky under the hood

The obvious thing is to check if the contents are equal. I don't know what cursed C++ you're looking at if you're finding a ton of string implementations not doing exactly that...

The author definitely understands that. The point is: when you don't have operator overloading you get stuff like that which does demonstrably confuse many people

In languages with operator overloading this just isn't a concern at all because == does the obvious thing

Thanks so much! I'll take a look at these when I get a chance

Maybe that'll be my next project. Or instead someone should just write a compiler which outputs a printf format string, perhaps?

It sounds like it should be possible (CMake also has eval), but the lack of OOP isn't so much a problem for what I needed. Packing and unpacking the vectors was more annoying. I can live without OOP, I've written enough C to get used to it haha.

It figures out which rows to render using its own worker index

Thanks! This is extremely impressive, and looks like far more effort haha

> The model being rendered also is hard-coded in the ray tracer.

This is true - but there's no reason why it couldn't be modified to read in a scene description. It's more a proof of concept than anything else.

Speaking as the author of the post, I completely agree! I got burned so many times by random shit that made no sense. Stringly typed languages are the absolute worst.