Information
Current intended usage breaks down when loading massive amounts of homebrew. Pain points include:
- 127MiB localStorage per-key limit (browser/env dependant?)
- list loading performance
- list search performance (current
isLazySearch workaround is insufficient vs. e.g. pagination)
- building internal data lists (see e.g. _MAX_DATA_CHUNK_SIZE)
- likely more
An intentional pass to better support mass-homebrew cases would enable sillier setups short-term, and ensure health vs. ever-increasing amounts of partnered content long-term.
Who would use it?
Anyone with a lot of homebrew
How would it work?
Better than it does right now
Indifferent - revilowaldow (Lyra)
Upvote - dagnasty69
Upvote - n1tro_dynamite18 (nitro_dynamite18)
Upvote - freedverse (DM Ϝrêêdvêrsє)
Upvote - mikahn (Mikahn)
Indifferent - the_hydro (The_Hydro)
Indifferent - shkrym (shkrym)
Indifferent - alicenull (Λlicenull)
Upvote - man3500 (Man3500)
Votes: +5 / -0 / ±4
Information
Current intended usage breaks down when loading massive amounts of homebrew. Pain points include:
isLazySearchworkaround is insufficient vs. e.g. pagination)An intentional pass to better support mass-homebrew cases would enable sillier setups short-term, and ensure health vs. ever-increasing amounts of partnered content long-term.
Who would use it?
Anyone with a lot of homebrew
How would it work?
Better than it does right now
Votes: +5 / -0 / ±4