Months choosing routing?
If so then they have bigger problems.
Re:Angular 13
by friendly_chap on Thursday November 04, 2021 @06:54AM
(#29105521)
It's life. It's one thing to call people amateurs from a sofa and an other to find yourself in 20 person team arguing about things.
The easy solution to arguments is having less things to argue about, similarly how Go solved formatting wars by an official format, Angular solves those fights by providing a default implementation.
Re:Angular 13
by 5e92cb50239222b on Thursday November 04, 2021 @07:23AM
(#29105677)
It's not life, it's your typical bike-shedding. React is being used on much larger teams all the time without spending months on arguing whether react-router is the right choice. I don't think I have ever spent more than ten minutes on choosing which library concoction works best for a given project.
In less dysfunctional organizations you go with whatever the technical lead specified.
Re:Angular 13
by friendly_chap on Thursday November 04, 2021 @07:40AM
(#29105821)
> It's not life, it's your typical bike-shedding
It's typical because it's life and it happens often.
> In less dysfunctional organizations
Dysfunction is the norm.
I am arguing for opinionated tools in general, I'm not saying you can't make it without them.
Similarly I advise against lottery while not doubting you won at it.
JSX mixing presentation and business logic also looks weird for someone who lived at a time when not doing MVC in PHP was a blasphemy and would not get you a respectable job.
Admittedly AngularJS was horrible but nowadays Angular offers me everything I need while I watch other people moving to Nextjs or whatever latest buzz frameworks for features Angular provides (like server side rendering).