atilimcetin

With 128GB ram, the price tag would be pretty high. And lots of application does not work Windows on Arm. Even Microsoft provides something like Rosetta 2 for windows, still x86 architecture would be the most popular one for Windows for a looong time.

Saying that I think this is product is kinda dead on arrival.

Oh very nice idea to get rid of the min operator.

Interesting article. I tend to use

- min(floor(x*256),255) (from float to uint8)

- i/255 (from uint8 to float)

Basically a mix of the 2 approaches mentioned in the article.

For all integers between [0,255], if I do uint8 -> float -> uint8 conversion, I will get the same result. That's the important part for me.

I use pi + openrouter (with qwen3.6-max-preview) a lot. I never hit any stability or performance problems yet.

Writing detailed and a bit math heavy blog post about specular microfacet-based BRDFs.

“Nice try”? This is really unfair and untasty.

Thanks for the reply. Noted :)

The title looks very promising. I’ve added this library to my to-do list to take a deeper look at it. Using this standart library within restricted safe subset of C++ can be a strong opponent for Zig (at least for myself).

I'm directly using https://chat.qwen.ai (Qwen3.6-Plus) and planning to switch to Qwen Code with subscription.

Nowadays, I'm working on a realtime path tracer where you need proper understanding of microfacet reflection models, PDFs, (multiple) importance sampling, ReSTIR, etc.. Saying that mine is a pretty unique specific use case.

And I've using Claude, Gemini, GLM, Qwen to double check my math, my code and to get practical information to make my path tracer more efficient. Claude and Gemini failed me more than a couple of times with wrong, misleading and unnecessary information but on the other hand Qwen always gave me proper, practical and correct information. I almost stopped using Claude and Gemini to not to waste my time anymore.

Claude code may shine developing web applications, backends and simple games. But it's definitely not for me. And this is the story of my specific use case.

After reading Sebastian Aaltonen's No Graphics API blog post [1], now I'm working on implementing the suggested API using Metal 4.

Also I gave that blog post to Claude Code and asked to implement the API and it made terrible terrible mistakes. Just saying.

[1] https://www.sebastianaaltonen.com/blog/no-graphics-api

I had to deal with the same problem on a GPU once. What worked for me was subdividing the cubic Bezier curve into smaller quadratic ones and then finding the roots of a cubic polynomial for each.

Whenever constraint programming languages come up, you can’t miss mentioning Håkan Kjellerstrand. He’s put together an amazing collection of problems and examples—including plenty for MiniZinc—on his site: https://www.hakank.org/minizinc/

Although not sure, it can be related to NLI models described here https://paperswithcode.com/task/natural-language-inference

I think this paper is as important as original Gaussian Splatting paper.

IMHO, developing with Node.js, Java, Python, Go, etc.. within MacOS is more convenient compared to Windows machines.

Also I can highly recommend using version managers (e.g. nvm, jenv, pyenv, gvm, etc..) for these languages to quickly install and manage different versions.

Home page of that arxiv paper: https://opencoder-llm.github.io/

My favourite is daisyUI