yeah i get that.
generally most modern UIs are moving away from those reactive patterns (React, Svelte, etc) just cuz the composition can be optimized (Kotlin compiler plugin, shadow-DOM, etc), and a lot of people—myself included—find that declarative design easier to reason about. and yeah i guess i outed myself as an Android dev, but i can’t in good conscience recommend the node based Android XML UI lol (although that’s a different SDK).
anyway, not to yuck your yum. i played around with JavaFX back in the day but never made anything to speak of. i’ll have to check out more of your blog!



i personally have pushed back on every “infinite scrolling” feature request from product designers. first, you think you need it; you don’t. second, you think it’s just so nifty! it isn’t. oh is your content is dynamically generated? what was wrong with Reddit’s pager that launched that site into popularity?
it’s unnecessary complexity that hides information from the user, makes API calls (which are, spoilers, paginated) more complicated, can cause the obvious memory/resource consumption issues, and just generally disempowers the user. which i guess on a social media app is the point. but totally counter to the goals of a fleet management system lol