4 ms·
I disagree; you add complexity to a stack for a reason, usually to provide functionality that would be difficult to reproduce otherwise. Hand-building a reacti
by TameAntelope 5y ago
I disagree; you add complexity to a stack for a reason, usually to provide functionality that would be difficult to reproduce otherwise.
Hand-building a reactive (lowercase r) table with sorting, filtering, etc. that's performant at large data volumes to keep your stack "simple", would be a nightmare to maintain and wouldn't allow other developers to bring prior experience with them when they later have to maintain that code.
- trasz 5y agoI agree, but what you are describing is a different thing: it's reinventing the wheel, not avoiding additional complexity. Avoiding additional complexity would be not having that reactive table. (And that of course would probably result in worse user experience, so it's really not a good example of what I've meant.)
- TameAntelope 5y ago> SQLite, a $5 linux VPS, vanilla JS, and a single line deploy script. This environment would necessitate "reinventing the wheel but so much worse" for anything other than the absolute most trivial applications.
- trasz 5y agoNot at all - it’s way simpler to set up than anything involving kubernetes, virtualization, or containers, and incomparably easier to fix when it breaks.