8000 Stores. Pagination. Frustration · Issue #63 · acdlite/flummox · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Stores. Pagination. Frustration #63
Open
@ivan-kleshnin

Description

@ivan-kleshnin

Not exactly a flummox question, but would be great to discuss it somewhere.
It's up to @acdlite to close this as offtopic if he wants to keep issues clear (some people do).
Some people also prefer to discuss on Gitter. But those threads are temporal and non indexable.


Pagination is a good example to illustrate some thoughts. Everyone makes pagination so
we should have countless implementations, libraries and competition here, right?
Well... actually no.

When I've come from backend programming I just wanted to reimplement basic CRUD stuff. All that features I had before: filters, sorts, pagination. I expected to find multiple solutions, smart decisions for this. So naive! I started with Backbone. I read through a lot of Backbone books. I watched a couple of Backbone video courses. About zero enlightment. They didn't even approach the questions of state management. Load all your data, then do frontend-only filters, frontend-only sorts, frontend-only pagination. Backend versions were more scalable!

I switched to Ampersand. Same things there. Just improved Backbone, still bloody low-level.
Logicless templates. No, thanks. Then React. Better render, same widgets / todo apps.
Still no state management solutions.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0