@the_baserate@alexanderrX_ If you do it right, you're always under manufacturer warranty and servicing fees are covered. You'll basically pay the same when buying a 20k shitbox, but you actually get the newest tech and dont have to worry about crashing down randomly.
@mlcarldev@asaio87 This is the only correct answer in this thread. A model which can run locally simply cannot compete with a model that requires tens to hundreds of GPUs in a cluster.
@igorakhmetov@MatRopert@ChShersh Oh wow I didn't know that. My lldb setup struggles with PEB/TEB, its a dealbreaker since I work a lot with FFIs. Also my lldb struggles unwinding the stack on an exception, so I won't know the exact try/catch block that caused it (win32 calls). How does clion manage to do that?
@igorakhmetov@MatRopert@ChShersh Yea via lldb (ive also set it up on cursor like that), but you're gonna want a msvc native debugger for enterprise level software (let's say UE5 or something like that)
@MatRopert@ChShersh The msvc (cppvsdbg) debugger is only offered via msft IDEs like vscode and visual studio. So if you want to debug msvc compiled code in let's say cursor or clion, good luck lol
@ericzakariasson@thenomadevel Typing in the commit input field in the version control panel (editor, not agents windows) is really laggy for me. Clearing/Archiving all agents for the projects makes it less laggy
@kapilansh_twt This was easily the most influential lecture I attended at ETH Zurich in my Bachelor's. Not only does it teach you the groundwork for working with modern SIMD architecture, it also reshapes how you write and optimize low level language code for any microarch.