Hacker Newsnew | past | comments | ask | show | jobs | submit | screwreg's commentslogin

Any chance of publishing the algorighm details? The main header (pls.hpp) mentions some links to private google docs.


Thanks for pointing this out! We need to make these public.

For the 10,000 foot view, watch our presentation at the WebGL/WebGPU meetup at GDC!

https://www.khronos.org/events/webgl-webgpu-meetup-GDC-2024


Please, write more about the implementation! There is so little information on this topic in general.

Like, how does sorting pixel segments result in coverage masks? Is there an accumulator somewhere that isn't mentioned?


Stripping copyrights is a great way to start a project: https://github.com/JetBrains/compose-jb/commit/6009cdd6cbdcf...


Quite great. I never understood why you'd want that copy-pasted everywhere: it's just noise.

Isn't a `LICENSE` file at the repo root enough? https://github.com/JetBrains/compose-jb/blob/master/LICENSE


I would love to have a lawyer chime in on this. It seems like the license at the root should be enough to say that you are applying the license to all the code.


Except that whole project is done side-by-side with Google team that works on Jetpack Compose AFAIK. ;)


Actually, there's been another advance since Ryu: Schubfach by Raffaello Giulietti and its optimized derivative Dragonbox by Junekey Jeon. Here's a cool page with implementations and a benchmark: https://github.com/abolz/Drachennest/


This page has a benchmark graph, but without labels on the axes, thus it doesn't even say which algorithm was faster.

My guess is that smaller y values indicate proportionally faster executions.


I'd love to see a post like this on instruction selection.


Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: