pulp_user

5 ms·

1.
by pulp_user 4y ago
Saying things akin to "your compiler is bad" because it doesn't optimize stuff like this is a cop out. For one: Most compilers for most languages are bad by that metric, and interpreters don't even get to play. So this i
2.
by pulp_user 5y ago
You are complaining about a format - with the stated goal to be very simple - not supporting some scientific usecase. What...? Use a different format then. That's not what this is trying to be. In fact, it's the exact opposite of
3.
by pulp_user 5y ago
What are you even talking about? Using sRGB won't make skin magically orange.
4.
by pulp_user 6y ago
(OP here) The main issues I had with them had nothing to do with immediate vs. retained mode, but simply with the unnecessary constraints the big GUI frameworks put on you. Usually the GUI framwork wants to own the project. I need to build
5.
by pulp_user 6y ago
(OP here) The suffering hasn't increased that much. It was all painful before.
6.
by pulp_user 6y ago
(OP here) I adressed that caveat in the late part of the answer. I also noted that I don't even think the performance difference is attributable to immediate vs retained mode. This was just a comparison agains existing applications. As
7.
by pulp_user 6y ago
(OP here) >Are you building vertex buffers? yes >Are you creating backing layers? I am not sure what those are. >Even the immediate mode APIs retain information! Yes, immediate mode only refers to the way the API is designed, it ha
8.
by pulp_user 6y ago
(OP here) I did! And it was enjoyable and didn't take that long (about 2 or 3 weeks initially). I think in the end It actually was still faster to just write the GUI by myself than to use Qt, simply because I would have to get used to