undefined | Better HN

0 pointsechopom6y ago0 comments

> my product has a combination of Angular, React, Vue and server-rendered pages.

This is intended by Micro Front.

Most Billions Dollars SaaS are based on this Frankenstein type of architecture, the goal is simple :

- Support legacy code with Zero Effort

The result for the end user is absolutely horrendous , it create slow and bloated web pages with Megabytes of JavaScript with UI of various style and behavior similar to Confluence/ Jira etc...

This architecture fits perfectly fit the state of the current market :

- Push lots of stuff out "as fast as possible"

- Turn over in software in +20%, people who build Jira 5 years ago aren't there anymore , they cashed in their stocks and went somewhere else to get a bigger paycheck

- The people who build those apps , most of the time , don't use them...

Leaders of Atlassian use Gmail and GDrive , I'm pretty confident that they don't even use Jira or any of their own software...

Those apps are so slow and bloated it's astonishing...Yet when something is the "norm" in the industry , it's definitely not an issue.

0 comments

1 comments · 1 top-level

JMTQp8lwXL6y ago

Let's not bury the lede here. The problem is with coordinating, not the colorful selection of technologies used. Most teams use abstractions on top of Webpack, because they are not interested in how a bundler works, and would rather focus on product features (from a business perspective: I can somewhat appreciate this sentiment). Since most teams haven't ever picked up Webpack, and barely touch facades surrounding it, good luck telling them to add module federation to their configuration.

j / k navigate · click thread line to collapse