Interesting question! Salesforce has a huge variety of front-end frameworks, and imposing a single one seems impractical (to say the least) from an organizational standpoint. 1/?
Even if it were possible, standardizing on a single front end framework would, for us, reduce efficiency rather than increase it.
We have teams working on hugely disparate products, and there exists no framework that would work well for all.
We have teams working on hugely disparate products, and there exists no framework that would work well for all.
The variety largely comes from acquisitions. Each company we buy comes in with their own stack, and it’s rarely in anybody’s best interest to make them rewrite everything. If It Ain’t Broke, etc etc.
As a developer I crave consistency, but I’ve come to realize that that impulse is _always_ counterproductive when we’re talking about groups of people. Sometimes it’s downright pathological.
The reason the Lightning design system is just markup & CSS is because it needs to be consumed by many different JS frameworks. If it were only available in Salesforce’s homegrown Lightning components, the vast majority of our products wouldn’t be able to use it.
At a small company, it’s totally possible to build a little cathedral of consistency.
But as your organization gets bigger (& no matter how it gets bigger), a bazaar inevitably accumulates around the base of your cathedral.
But as your organization gets bigger (& no matter how it gets bigger), a bazaar inevitably accumulates around the base of your cathedral.
And then one day, you realize that the bazaar is so big & so lively & so compelling that your cathedral has really just become another stall.
That is an amazing day.
That is an amazing day.
It actually never comes for most organizations, but that’s another rant entirely 😅
