robinei

6 ms·

31.
by robinei 6y ago
I assume they dismantled and sold what they could? Like the roller coaster
32.
by robinei 6y ago
No, in reality 3.1 was actually very fast.
33.
by robinei 6y ago
I'm not convinced that redrawing on input events is especially inefficient. No need to redraw continuously.
34.
by robinei 6y ago
There is no reason an IMGUI cannot efficiently construct a hierarchy in the background and do a fast Flutter-like linear layout pass on it before processing input and rendering it. Then throw this away and do it all over again for the next
35.
by robinei 6y ago
The most important reason for "do" is avoiding excessive indentation, when starting with the first expression on the same line. And "fn" is good for something that you will want to avoid taking too much space, since you
36.
by robinei 6y ago
I also think that engineering concerns can dictate or at least strongly influence language design. It can still lead to innovation though, like in the way Zig handles async/await, and how it will try to handle recursion. It is just inn
37.
by robinei 6y ago
I have the feeling that what will push Zig ahead is the uncanny sense of technical aesthetics shown by the creator. Unsexy details like language simplicity, what-you-read-is-what-runs, orders of magnitude faster compile times, effortless cr
38.
by robinei 11y ago
If the banks were going to default without taxpayer help, why didn't we just nationalize them and let the share holders take the loss they themselves have set themselves up for? Then we could shoulder the cost of getting the banks aflo
39.
by robinei 11y ago
I meant to say homogenous array, which I assume you were talking about.
40.
by robinei 11y ago
Since you are talking about a heterogeneous [edit: homogeneous] array, you would store the concrete structs continously in Rust as well. Rust would also not waste space in the vector for storing a vtable-pointer, and would instead construct