kevstev
Joined 10 years ago
Joined 10 years ago
It seems he is deeply connected, and probably approaching centimillionaire wealth.
Even if he is burning some bridges, its not going to affect his career at this point.
Edit: I looked at the current interim CEO's profile, not the outgoings, but its almost the same story- he is 55, been on other boards, has experience at director+ level since 1995 listed... this isn't going to hurt his career.
Also, this was the late 90s and while you could get linux running, all the servers were Unix, and the profs made it very clear any issues between differences between Linux and Solaris were ours to deal with... so we were essentially forced to login to their servers. We are truly our own worst enemy sometimes.
But the P11 Pro is now 6.3" and the P8 Pro was 6.7" meaning you have to go up to the P11 Pro XL (for another $200) for the same size. Well technically its 6.8" vs 6.7 but I feel this is just a form of shrinkflation and enshittification. Literally no other improvements on the XL as far as I can tell from the specs, not even a larger battery.
While I certainly don't need a bigger phone, I would be pissed if I just hit the buy button and what came out of the box was half an inch smaller.
Maybe I wasn't being precise enough with my language for this forum, and also my last hands on experience with it was roughly 6 years ago, maybe it's gotten better. But it was much less (and forgive the imprecision!) python/pytorch-like where you say hey take this big blob of data and just slice and dice it on your many cores, and more like ok, here is the data, let's cudamemcopy it in these size chunks over to the gpu itself, to be used by this block of threads and run these commands (kernel in cudaspeak) on it. Much more painstaking and micromanagey of the resources.
Pytorch IMHO feels like a proper abstracted API that hides the details and lets you just unleash the fury at the cost of some efficiency, while the cuda api itself, similar to working with C, forces you to really think about the low level details. I have a heavy backend and systems development background, and while it wasn't really intimidating to me, it was like wow you really have to have a deep working knowledge of how these things work and it felt like a step back in time IMHO.
I doubt that's going to satisfy you but I think it gives a clearer picture of what using cuda is like if you typically use higher level languages and haven't touched C since college.
AMD has had years to try and counter it, but just has not. Google is kinda trying to do an end run around it with TPUs but they are still niche high end stuff with limited availability.
Its really just CUDA, and CUDA can be seen as somewhat akin to C for assembly used by Nvidia's gpus- In many ways a wrapper around the low level hardware that often has those details bleed through.
That booklet doesn't appear to be available online anywhere :(.
I even burned a CD of the smallest ubuntu distro I could find, and its happily running linux and hosting Immich, among other things.
Writing a regex involves always looking up the syntax, and being unable to read it an hour later without having to carefully disect it. I say this with 20+ YOE and I think I am better than the average bear with them.
That said, knowing what they can do is important and very useful. Its just the implementation that never quite sticks.
Take your phones back. Life is immensely better these days.
I think most go this route for comics, graphic novels and some read magazines on it. Niche, but not a gimmick.