salojoo

8 ms·

1.
by salojoo 1y ago
The amount of concurrent webgl canvases on a page is limited by browsers. I believe it's somewhere between 8-20 depending on the browser. Hopefully webgpu would lift that limit?
2.
by salojoo 1y ago
I'm rendering charts. The native API conveniently provides the fundamentals with lines and rectangles. In addition masking and text have been very useful. Interaction is also supported by the API with hit regions, though I've opte
3.
by salojoo 1y ago
I evaluated this vs pixi and native canvas API. In the end I decided to use native API. Konva didn't have enough performance for my use case and pixi webgl has a limit on the number of canvases on the screen at the same time The native
4.
by salojoo 2y ago
You should wait for M5 to get M4 for a discount
5.
by salojoo 2y ago
This is good news. Feels refreshing to see some respect towards users for a change.
6.
by salojoo 2y ago
Right, I didn't know it was possible to bypass full channels like that with select/default. Thanks for spelling it out
7.
by salojoo 2y ago
We probably both understand the underlying concepts correctly. But just in case: also buffered channels will block if full. So I don't see how notifications get discarded (meaning lost). But somehow that's what your text says?
8.
by salojoo 2y ago
"Instead, a received notification is immediately sent into buffered channel, which means it’s discarded if the channel is full" Shouldn't the channel rather block than discard if full? Anyway, nice and relevant article for me
9.
by salojoo 2y ago
Vinge introduced me to space opera with zones of thought. Such amazing books I've read multiple times.
10.
by salojoo 3y ago
Performance per dollar has traditionally been the selling point with PCs. Performance per watt is the selling point with Apple silicon. Does this one fit somewhere in between?
11.
by salojoo 3y ago
https://github.com/sraoss/pg_ivm
12.
by salojoo 3y ago
Have you tried pg_repack?