3 ms·

To give some abstractions out of the box, mostly, so you don’t have to reinvent the wheel - the demands of a lot of websites and applications nowadays include i

To give some abstractions out of the box, mostly, so you don’t have to reinvent the wheel - the demands of a lot of websites and applications nowadays include interactivity on every level, very fast and smooth ui population, and pretty animations. Sometimes the tools are great for working in huge teams on the same codebase, sometimes it’s for giving a lot of features to a smaller team.

FridgeSeal 3y ago
> the demands of a lot of websites and applications nowadays include interactivity on every level The demands of the PM maybe, most users just want something the works and gets out of their way. > very fast and smooth ui population Neither of which your average JS/SPA/behemoth is actually good at. > and pretty animations. I’ll give you this though, JS web apps certainly do rep some pretty animations, often at the cost of thrashing my CPU and ram. Crazy idea, but maybe, if instead of spending ages building “interactivity” we just built “applications that worked”, we might actually have less mess, and build better products.
- taurath 3y ago
  Broadly agree that simpler is better. Having seen systems be built up over time that do significant things (or run on many platforms, or have lots of abstractions) a lot of the time the tougher parts are.. well, complicated. Some of those tools are to make things better for a lot of programmers working on the same project. You have to have some amount of structure then. Sometimes it’s so business people can create content. “Why doesn’t it work simply” is often a business decision.