Show HN: World's most performant web table (multicore, DOM-based)

15 pointsposted 10 days ago
by snabriel
(github.com)

17 Comments

TristanBall

10 days ago

That's very, very nice.

I live in a world of Confluence tables, but it's nice to know that not everyone is suffering.

user

10 days ago

[deleted]

user

10 days ago

[deleted]

GranPC

10 days ago

10-15 FPS on Firefox for Android.

TowerTall

8 days ago

I got 60 FPS using brave when my laptop was plugin in. When unplugging and it went into low battery mode, FPS dropped to 30

snabriel

7 days ago

yeah all laptop power saving modes throttles the fps. and otherwise it's capped to your hz on your display (or whatever chrome decides is the limit) which seems to be 60

c0balt

9 days ago

Getting a solid 60 (pegged to display refresh rate) on a pixel 6a on Firefox on Android.

edelhans

10 days ago

For comparison - I'm getting solid 120fps with Brave on Android.

snabriel

9 days ago

weird, maybe your browser just happens to be very unoptimized or does not have hardware acceleration / disabled hardware acceleration

grahamj

10 days ago

No tests?!

user

10 days ago

[deleted]

tharkun__

10 days ago

No wonder it's fast. I clicked the Try It link and I literally just get a white screen with scrollbars and the FPS display.

tharkun__

9 days ago

Can't edit any longer but just to clarify: That was on DuckDuckGo on Android, which is my one and only browser on mobile. So if something doesn't work with it, I disengage. Given this is HN, benefit of the doubt :)

Meaning now trying it on Desktop with Firefox and DuckDuckGo as an extension it works just fine.

On both, the FPS display is basically pegged at 60 FPS. So I think this is probably technologically awesome work for the performance side and just isn't compatible with some specific setup(s).

snabriel

7 days ago

ah yeah that makes sense, i use SharedArrayBuffers which i think duckduckgo on android might not support. the project is more of a template or a place to learn than a plug and play web table at this stage, will make a fallback to running everything on the main thread for browsers that don't want to implement SharedArrayBuffer