Hacker News new | past | comments | ask | show | jobs | submit login

I started my webdev time with Django and flask, switched to Spring boot at the next job with various templating languages, depending on the artefact and some laravel sprinkled in.

Finally, the employer decreed that moving forward all frontends had to be done in Angular (version 6 or 7 at that time) and I have to say... I don't understand the point you're trying to make.

The frontend stacks aren't particularly more complex then the equivalent application done with html templates and varying ways to update the DOM.

Personally I'd say they're easier, which is why UX also started to demand state changes to be animated etc, requests to be automatically retried and handle every potential error scenario, which was never even attempted with pure backend websites

Nowadays I prefer using Typescript for anything html related and would not use backend templates unless the website is not going to be interactive




> I don't understand the point you're trying to make.

> The frontend stacks aren't particularly more complex

I'm not making a point about programmer experience at all. I'm saying that for most uses of most sites, the fact that Angular (or similar) is running in the user's browser is making the user experience worse. Performance is worse, accessibility can be worse, and so forth. And (again, for most uses of most sites) there is no benefit to the end user.

Consider the blogs, brochureware sites, landing pages, and e-commerce product pages that absolutely don't need something like Angular that today nonetheless do include it. Most Web apps are much closer to those than to Google Earth, Facebook, or Spotify's Web player.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: