Live by cutting edge, get cut by cutting edge. Tech is churn and burn.
Warning: Semi-off-topic Rant Ahead
Even with "regular" software, more devs and companies are more interested in chasing buzzwords than parsimony and simplicity. The result is a moving messy target. There are tools from the 90's that dev's are 4x more productive under because they are integrated tools rather than glued-on layers, requiring about 1/4 the code per feature. You don't need to worry about "separation of UI and biz logic" because BOTH are so compact that there is almost no down-side to mixing them in the same class. The separation-of-concerns movement was to manage bloated stacks & teams better, not an evolutionary step up.
They are not web-scale and not mobile-friendly, but that turned out not to matter. Internal biz didn't need mobile after all, and we spent all that bloat and trial-and-error trying to get dual-device layouts to work right in vein. People like to tell stories about how such tools became problematic when they needed "enterprise scale", but most our internal apps are not enterprise-scale.
The assumption is often that a web/enterprise tool can scale both down and up such that it's used on smaller projects also. Wrong Answer!* That's a failed assumption, creating bloated fragile smaller apps. One Tool Size Does NOT Fit All. Internal is not external. Desktop is not mobile. Small is not Web-scale. One of the reasons the F-35 got so expensive is that it tried to be everything to everybody. Maybe one day they'll make an affordable version, but the journey was expensive and bug-ridden.
Humans, you are doing IT wrong.
* It may be possible to have the small-end and big-end tools share a lot of features, conventions, and libraries, but not be the same tool. This hypothetical set should share what makes sense to share, and separate for target size when not. Do note that lack of data volume doesn't necessarily mean "simple". Billing can get rather complex for service companies, for example, but there is typically only say 30 invoiced being generated a day, including drafts.