News for hackers. Stuff that matters.
Re:Why Vanilla JavaScript by dsego on Monday July 13, 2026 @04:38AM (#48889632)
But it's harder to have component composition. Consider also lists and adding/removing items and so on, juggling all of it gets insanely complex and requires MVC or MVVM patterns like with backbone.js
Re:Why Vanilla JavaScript by inigyou on Monday July 13, 2026 @07:26AM (#48891029)
You just call updateFieldVisibility() every time the list selection changes and don't worry about the redundancy.
Re:Why Vanilla JavaScript by oneeyedpigeon on Monday July 13, 2026 @05:40AM (#48890106)
But now we're back at "Not everyone is building complex UIs like google sheets". I agree with the underlying sentiment of this thread: overengineering is way more common than underengineering.
Re:Why Vanilla JavaScript by dsego on Monday July 13, 2026 @06:17AM (#48890419)
Eventually each crud form evolves into something more complex, the bar is set higher today, we expect pagination, filtering, search, inline editing, grids, instant validation, auto-save, push notifications, state sync, ... that's not a complex UI nowadays, it's expected. Not sure what a non-complex UI looks like.