I work have built some dense UI for certain types of fixed income (bonds and swaps) trading, looking to move it all to svelte because react cannot handle the quantities of data (and if even if it could the code is unbelievably ugly). Something I've been banging on about for a while is the following: Programmers and designers keep trying to rebuild instagram in every domain, pretty UIs, regular UIs, "simple" UIs. This…
An experiment in UI density created with Svelte
211–220 of 267 posts
Re: An experiment in UI density created with Svelte
#212Earlier quoted context omitted.
Honestly this doesn't even sound like a particularly bad thing. Sort of like how Houdini has literally no competition whatsoever. Like it's actually hilarious how nothing even comes close. It just works so well that nobody can really hope to ever do better, and there is nearly 0 enshittification happening, so its existing users have no reason to ever switch.
Having found more than one thing called that, could you enlighten me as to which Houdini you're referring to, please?
Re: An experiment in UI density created with Svelte
#213Earlier quoted context omitted.
DataTables is great. Been using it for 10+ on a single product. We keep looking for a newer and better replacement, but have yet to find it.
Same, absolutely "stuck" with DataTables. It seems to work well even with comprehensive UI frameworks on top of it like SB Admin Pro. Just super easy to integrate DataTables and has 90% of the features I ever want.
What’s in the other 10%?
Re: An experiment in UI density created with Svelte
#214This is interesting because it proves something to me about my vision and visual comprehension. The "Grid" view is absolutely fine for me. The "Table" view is unworkable. I have a lot of trouble scanning across lines like this, where I will lose which line I am on (when my glance shifts). This, I have realised, is due to the tendency to shift eye dominance slightly across to the right. (My eyes are subtly misaligned…
I think your trouble with the table has far more to do with the design (specifically color) choices made by the author. 1. You mentioned this in passing, but I'll repeat for emphasis: The contrast between a hovered/highlighted table row and ones that are not is too low. I have decent eyes and I also have a hard time seeing it. 2. Table rows (and/or columns) should be striped between two or more high contrast colors f…
Re: An experiment in UI density created with Svelte
#215Above is the evidence that react can handle this sort of thing just fine.
I hacked/converted the page in question to React to show something similar.
Its randomly generating updates to the table and then resorting the table and repeating.
You can grab the source here but I warn you it's hacked together in less than an hour:
Re: An experiment in UI density created with Svelte
#216I work have built some dense UI for certain types of fixed income (bonds and swaps) trading, looking to move it all to svelte because react cannot handle the quantities of data (and if even if it could the code is unbelievably ugly). Something I've been banging on about for a while is the following: Programmers and designers keep trying to rebuild instagram in every domain, pretty UIs, regular UIs, "simple" UIs. This…
https://static.crowdwave.link/index.html
And the source: https://static.crowdwave.link/sveltetest.zip
Re: An experiment in UI density created with Svelte
#217Earlier quoted context omitted.
I don't know that a 15 millisecond difference in rendering performance is going to matter to anyone =/ The memory usage is in megabytes too. It's not much. For sure React is slower on paper, but in most cases it's a non-issue. Nobody chooses React for its performance benefits anyway, but because of its huge ecosystem of libs and developers. In most cases it's fast enough.
The fact that it's fast enough on your 2000$ machine doesn't really tell us much.
Re: An experiment in UI density created with Svelte
#218Earlier quoted context omitted.
> you run into performance problems at the same number of elements regardless of whether they're interactive. As you implemented for the some of these pages, the solution is to go to a canvas. That's surprising. I thought Svelte's whole selling point was ultra-targeted and efficient DOM updates as a result of the compilation step and not having vdom. Are simple large tables still a problem within that paradigm? Which…
The browser can take very long to layout and draw a page with a huge number of DOM elements. Hardware starts to mask a lot of these issues, but even a table with 1000 to 10,000 rows will already cause issues. And table layout is very optimized (for this reason, there are plenty of CSS gotchas around tables). So a 10,000 row plain HTML table still is rendered relatively fast, but not practical for an interactive UI. B…
Similar approach (custom virtual processor) is leveraged by Google docs/sheets.
Canvas rendering may be the last resort when nothing worked.
Re: An experiment in UI density created with Svelte
#219Low UI density is the new emperor's clothes in modern UI design. It's being actively promoted by companies in order to cut design costs, but the truth is that it's only reasonable on touch interfaces or casual apps. Mouse interfaces are fundamentally different, because you have much more pointing precision, so it pays off to show more data on the screen. You don't have to cram your interface with with spaces to make…
Is Cahier built on top of Zotero? It looks very similar. Good notetaking support is something Zotero lacks, so I see the appeal for an alternative that focuses more on it.
Re: An experiment in UI density created with Svelte
#220Earlier quoted context omitted.
Having found more than one thing called that, could you enlighten me as to which Houdini you're referring to, please?
Assuming it's the SideFX product - https://www.sidefx.com/ - it's simply the best in it's class.