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

- i = min(floor(f * 256), 255) (from float to uint8)

- f = 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.

--

edit: I wondered what's the maximum jitter amount that I can introduce to the float and get the same uint8 value. And also these 0->0.0 and 255->1.0 should map properly.

With my approach at the top, the jitter margin that I can introduce is 1/65280.

But with the article's approach

- i = floor(f * 255 + 0.5)

- f = i / 255

maximum jitter margin is 1/510 (which is better).

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 somewhat specific use case.

And I use 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’ve 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

IMHO, one of the most useful free resource to begin and improve your art is Drawabox[1]. (Its lessons teach much more than just drawing a box.)

[1] https://drawabox.com/

Looks great! Can you also consider supporting svelte[1] (and sveltekit[2]) officialy?

[1] https://svelte.dev

[2] https://kit.svelte.dev

sure!!

I've started writing a technical book about "how to develop a game boy emulator from scratch". :fingers_crossed:

I'm using typst[1] for my writing journey.

[1] https://typst.app/

I can recommend Cem Yuksel's youtube videos about interactive computer graphics - https://www.youtube.com/watch?v=UVCuWQV_-Es&list=PLplnkTzzqs...

There are lots of good suggestions here. My first preference would be pico-8 (already mentioned).

But also I can also suggest another interesting option: GB Studio - https://www.gbstudio.dev It's a quick and easy to use drag and drop retro game creator for game boy. It also supports visual scripting.

I came here to say the same thing. I have some experience with both asciidoc and typst and anybody uses/tried using asciidoc should try typst and see for themselves how good it is.

I remembered the same. Perspective correction needs a division operation for each pixel and while drawing a scanline, calculating it every 16 pixels and linearly interpolating between them make a huge speed difference.

Today I saw https://pl.aiwright.dev/ (An AI-powered dialogue generation tool for interactive narratives.) Can be interesting to look into it.

Learning to play a musical instrument

I've started with the Vangoa EWI-100, which is an affordable, silent, and good enough MIDI EWI (electronic wind instrument) device. I have also been learning some of the technical details of MIDI. I sometimes use it alone, and sometimes with a Cocos Reaper with free VSTs. I have only been doing this for 4 days, but I am already enjoying it a lot.

If I continue to play it, most probably I will upgrade to a better EWI.

Recently my favorite is core contracts of Uniswap V3 - https://github.com/Uniswap/v3-core Lots of nice ideas for a restrictive computing platform like EVM.

My favorite chess variant is duck chess: https://duckchess.com/ (and HN discussion: https://news.ycombinator.com/item?id=31429290)