35 ms·
> adopting an established valid opinion to guide the team's development Different requirements allow for different settings. Coming from an Enterprise Applicat
by _the_inflator 6y ago
> adopting an established valid opinion to guide the team's development
Different requirements allow for different settings. Coming from an Enterprise Application background, I found this being more often the case or the only case.
Working with different teams, developer fluctuation, different time zones, different skill sets, a framework guides the development process far better.
Vanilla JS is something that should be avoided in team setups. There is too much mental overload that is usually not justified by the benefits. It is like deliberately choosing assembler language when Java or C# would do the job better.
Frameworks got a bad rep. For me, they are tools that should be used.
- morrvs 6y agoI've heard the Assembly vs. C analogy a couple times now, and find it hard to apply: Assembly languages come in many flavors whereas C is a single, standard abstraction over these. DOM is a single, standard API whereas frameworks/libraries come in many, ever-changing flavors and provide different abstractions over the DOM. It's a very different situation. Also, the level of abstraction that C provides over assembly is amazing. The level of abstraction that React provides over the DOM is comparably low (they are based on the same programming language).