3 ms·
From an application manager/solution manager perspective, I see 2 main reasons and a few smaller ones: 1. more and more complex UI. Things that used to be done
by AdrianB1 4y ago
From an application manager/solution manager perspective, I see 2 main reasons and a few smaller ones:
1. more and more complex UI. Things that used to be done in a native app are now in a browser, this has good and bad parts.
2. a lot of show off from the developers side going for overly engineered solutions. Nobody likes HTML+CSS and JavaScript anymore, if there is no cool framework with tons of tooling and dependencies than they are not happy. (yes, I know, flak incoming)
Other reasons are the complexity of dependency chains, the lack of security mindset by having hundreds of dependencies looking for a left-pad, the complexity coming from the testing of these overengineered and overly complex solutions, the move towards hybrid front end-back end management of state, rendering etc. There is also the overstretching of the frontend development role, now a fe dev needs to not just write the equivalent of HTML+CSS+JS but also containers, devops, CI/CD, all that jazz.
- wellanyway 4y agoHow much of that complex UI is managing state of the notifocations that are out to rape your brain and how much is actually useful?