cyber_kinetist

I know that HN is quite American-centric, but for rest of the developed world (particularity Europe and East Asia), we're already worried about an impending world war.

Support Vector Machines involve solving a large QP optimization problem... which is often done by running a variant of gradient descent (or one of the second- or quasi-second-order optimization algorithms, which involves finding the Hessian as well as the gradient)

At least the Chinese AI companies are doing good service open-sourcing their models back to the public.

There is a real danger if Valve ever gets sold in bad hands - the only hope is Gabe Newell living long enough or find a good successor who can continue having a majority stake in the company.

The "no A, no B, no C" pattern is a phrase that's frequently generated by Claude Code.

Which counteracts with the EU's desire to have any kind of sovereign AI. Guess you have to lose something if you want to earn something...

I've read both, but Baudrillard is more lucid and insightful in his writing. I would suggest reading Symbollic Exchange and Death (his magnum opus) instead of Simulacra and Simulation first though.

It has been a while since bro has become a gender-neutral term, particularly in younger circles...

Niche as in... I haven't heard anyone using it except for the studio that made it (Gaijin Entertainment). Might be a good language (at least from what the docs suggest), but needs some marketing to increase adoption...

For gamedev scripting, the gap has not been filled yet. Lua is good for embedding but the language itself is terrible for LLM usage (too much dynamic typing). C# is too heavy for scripting usage (long compile times, clunky to embed into a C++ engine), and other alternatives (AngelScript, daScript, ...) are just too niche.

Nope it uses modern OpenGL and LWJGL bindings under the hood. Recently they're in the process of switching the entire thing to Vulkan.

Note that I've used the term "Graphics Programming" rather than just "Computer Graphics".

The RTR book doesn't teach you the programming side of things at all, the material is more theoretical and reads more like a reference book. Most importantly it doesn't have any examples with full source code, so it's not a friendly book to follow for beginners. The PBR book is much better in this regard, but it mainly focuses on offline ray tracing / path tracing which is bit of a distinct topic from conventional real-time rendering on the GPU.