I'd say it's more nuanced. Reading code properly _is_ writing code. Ie i have to work through the logic as if i'm writing it, which is effectively writing it in my head, before i know if that's what i believe to be optimal.
I can _just_ read the code of course, and understand what it does - but just reading isn't analyzing it to the degree you do when you review/write the code. In that level of analysis you're looking for edge cases, bugs, etc. Reasons you'd write it differently. Which i suspect is functionally similar, if not identical, to writing it.
I'm quite new to property testing, first introduced recently via a Rust property testing framework proptest[0]. So far i've had the feeling that property testing frameworks need to include a way to rationalize complexity, as their assumptions can easily fall short as you illustrated.
Eg the simplest example might be an application where you input an integer, but a smaller int actually drives up the complexity. This idea gets more complex when we consider a list of ints, where a larger list and larger numbers are simpler. Etcetc.
It would be neat if a proptest framework supported (and maybe they do, again, i'm a novice here) a way to rank complexity. Eg a simple function which gives two input failures and you can choose which is the simpler.
Another really neat way to do that might be to actually compute the path complexity as the program runs based on the count of CPU instructions or something. This wouldn't always be a parallel, but would often be the right default i imagine.
Either way in my limited proptest experience, i've found it a bit difficult to design the tests to test what you actually want, but very helpful once you establish that.
As an aside, i hate GPUs on Linux. I'm running Blender and am in the market for a new PC build. The GPU is a huge source of confusion, due to Linux.
I see so many conflicting stories about how well AMD GPUs behave and perform on Linux. Some new, many old. Some even as extreme as "I bought a new AMD GPU and there are no drivers for it yet". Furthermore for Blender specifically AMD seems to get the short stick in performance.
Really leaves me confused as to what to buy. Just venting.
Appreciate the info! I'll have to look into that. As someone who runs Computer Graphics software GPU perf is important to me. I'll be curious to look into how Nouveau behaves there
Sure, i'm willing to accept that - but is your solution for me to buy a new graphics card?
How much of the market share is Nvidia? A stupid quick search's top result says 80%. So 80% of PCs can't run Wayland?
To be clear, i know nothing of compositors/etc, I've had nothing but problems with Xorg, and i want to use Wayland. _and yet_ - it seems like there is not a single PC in my house, or any of my family, that can run Wayland.
I'm happy to accept your statement of where the blame lies. But if you're telling me Nvidia can't run Wayland currently.. does it matter to the end user? When "Most PCs" can't run Wayland his statement of "precious use-case" seems off base.
Yea i'm confused by this line. I'm a Linux-desktop-noob, but i was going to use i3-Wayland, aka Sway, and because i have an Nvidia i was told don't bother. Nvidia Drivers + Wayland sound broken?
Now that may not be true.. but it seemed clear cut. I wanted to try Wayland really bad because i have a multi-DPI monitor setup, and Xorg is awful at that. Yet, it seemed too early.
Nvidia isn't exactly some niche product. Not exactly a "Precious use-case".
I can _just_ read the code of course, and understand what it does - but just reading isn't analyzing it to the degree you do when you review/write the code. In that level of analysis you're looking for edge cases, bugs, etc. Reasons you'd write it differently. Which i suspect is functionally similar, if not identical, to writing it.