@nprofile1q... @nprofile1q... heh, reminds me that the first version of this CPU netlist visualization used ImDrawList and performance was 'nearly good enough' (in the meantime I switched to a specialized shader rendering a static pre-triangulated mesh)

https://floooh.github.io/visualz80remix/

@nprofile1q... too much code in your switch-prongs IMHO :)

@nprofile1q... it *is* kinda interesting that German just imported the original Dutch word and pronouncation instead of 'germanizing' it to 'Jagt' (hunt) or 'Jäger' (hunter) like we did with other Dutch ship types (like Kruiser => Kreuzer)

@nprofile1q... the infuriating thing about vulkan barriers is that most of them are a no-op on most desktop GPUs (AFAIK) :/

FWIW in sokol-gfx I also have very conservative barriers, but I guess I'll just keep them for now.

A better solution would be to do some sort of 'time travel barriers', e.g. maintain two cmdbufs per sokol render pass, one only for barriers, the other only for render commands. In the sokol-gfx resource binding function, record the required barrier into the barrier cmdbuf... \

@nprofile1q... ...my national cliches are all confused now. Seeing those chopped up German rust buckets lined up in the background along with the DPD container used to smuggle them over the border was expecting the band to be from Poland ;)

...but they're from Finland, where I would expect chopped up Ladas instead...

@nprofile1q... Hugo is fine, especially since it's just a single Go executable. Less things that can break. Can get quite 'fancy' with themes etc though.

This webpage: https://floooh.github.io/fips/

...looks like this in Hugo:

https://github.com/floooh/fips/tree/master/webpage

@nprofile1q... @nprofile1q... I had some success using Claude Opus for bug scanning, basically as fuzzy static analyzer (e.g. it finds wrong comments and messages). Plenty of non-bugs too though.

But on more complex cases (such as my home computer emulator code) it just got stuck in an endless 'reasoning loop', and I guess for large code bases that simply gets to expensive for hobbyists (currently I don't pay for my hobby usage, my employer does heh).

@nprofile1q... IME sRGB always has been a clusterfuck of buggy implementations and missing features, especially in GL drivers. I bet most games do the sRGB conversion before writing to the render target in shader, and also don't bother with sRGB textures but instead pre-convert in the asset pipeline.

@nprofile1q... I bet they'll still manage to make it as slow as running React in a web view ;)

@nprofile1q... IME pretty much all language extensions in VSCode have traditional LSP-based auto-completion (including the Microsoft ones - they just call it 'Intellisense'). AFAIK what they call 'Intellicode' was always Copilot based.