Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)RA
Posts
0
Comments
80
Joined
2 yr. ago

  • Once you have the idea, seeing that it works if often easy. But coming up with ideas like that can be really hard, which is why gauss was the only one in his class who got it. There is no general method, you just have to think about stuff for a while, but you can get better with practice. And it feels really good when you prove something for yourself, even if it's relatively straightforward. You can just try to prove some simple things yourself, if you want, the advanced college courses are just for proving really advanced stuff.

  • It's weird because usually the people writing the expressions want to communicate clearly, and stuff like 1/2x is not immediately clear to everyone, so they write the 1/2 as a fraction.

    The same expression on both sides of the division sign only reduce to one if they actually bind to the division sign, which is rarely an issue, but that is exactly the thing that is in question here. I think it's clear that 1 + 1/1 + 1 is 3, not 1, even though 1+1 = 1+1.

    But as you said, of course, the evaluation order is just convention, you can just as well write everything in https://en.m.wikipedia.org/wiki/Reverse_Polish_notation

  • your first line is correct, but while it looks like 1 (and it might be under different conventions), evaluating according to standard rules (left to right if not disambiguated by pemdas) yields

    2(2+2)/2(2+2) = 2(4)/2(4) = 24/24 = 8/24 = 44 = 16

    Using implicit multiplication in quotients is weird and really shouldn't happen, this would usually be written as 8/(2(2+2)) or 8/2(2+2) and both are much clearer

    Your second argument only works if you treat 2(2+2) as a single "thing", which it looks like, but isn't, in this case

  • Are you sure? The way I understand it, ray marching is not something that can really replace ray/pathtracing, it's mainly used for rendering signed distance fields which is cool if you want to draw fractals and stuff, but not very efficient for classical geometry

  • In your case I would just start by copying a full setup someone else made and then customizing it, starting from scratch always takes a lot of effort. Reddit's unixporn was great for that, the alternatives on lemmy are sadly still a little empty.