Angular: The Documentary An origin story (Category Engineering)
I saw an interesting one. documentary About the creation and development of the front framework Angular. This film is interesting to watch even if you are not interested in the history of frontline frameworks. ||(By the way, there is also a documentary about react and I am already talking about it.|| told). Angular was born as an internal experiment at Google that was initially dismissed by big teams. (Gmail and Maps)It became a massive framework and went through a painful second life. (Angular 2+). Now a little.
1. How Angular Appeared Inside Google (localism) The project was launched by the team that worked on Google Feedback. She drowned in 17 000 Lines of frontend and low testability. Then Miszko Hevery proposed a bold move: rewrite everything in two weeks with his hobby project. (GetAngular/AngularJS). It was three, but the code shrunk to ~1 500 It was a moment of truth, and management saw value in the approach and gave the green light to the development. In general, it is clear that Angular was born not as a global top-down initiative, but rather as a local engineering idea, proven prototype treatment of real team pain. 2. Struggle for Resources and No on the Road At launch, AngularJS didn’t get a fixture from the flagships inside Google – many said something in the style of “good toy, good luck”. Support came after demonstrating dramatic complexity/code savings and development speed. First, a small team, a lot of skepticism, few resources; then organic growth around the first successful implementations. In a large company, it is better to once radically show value on a working case than to convince for a long time with words. 3. How Dart appeared in Angular and why AngularJS and Angular split further The next fork was productivity, statistical analysis, and tree-shaking. Inside Google at this point, Dart was strong. (With its dart2js and aggressive tree-shaking)The Angular team experimented between JS, AtScript and Dart. As a result, Google and Microsoft agreed on TypeScript: the key ideas of AtScript hit TS 1.5Angular 2 It was built on TypeScript, while supporting AngularDart for large internal products. (Ads/AdSense). This is what cemented the historic split: AngularJS (1.x) angular (2+) - two different worlds. As a result, we can see that Dart influenced the allocation of additional resources, framework architecture and compilation. (Staticity, AOT, tree-shaking)But the "language stake" in the open ecosystem has shifted toward TypeScript. 4. Large migrations Angular had two key migrations: Architectural gap AngularJS → Angular (2+) - without backward compatibility. Redesign for mobility, modularity, typing and future compilation. This is the most painful point in history. Change the render engine to Ivy (Angular 9) - already internal replacement of the View Engine with a new compiler / renderer, specially designed for fine granular tree-shaking and smaller bundles. The transition was a default in v9 and brought tangible size savings without rewriting applications from scratch. Both migrations were painful but seem necessary. 5. How Angular Feels Now and Plans Angular is on the rise again: Mature reactivity (Signals), strong SSR/hydration, focus on DX and performance, neat majors without "world scrap". And Google plans to move Wiz features (internal framework within Google) Public Angular. The current roadmap is available on angular.dev/roadmap.
In general, the documentary seemed interesting to me as a technical manager and an engineer - there are many useful lessons to be learned from this story about how to create and develop large projects.
#Software #SoftwareDevelopment #Architecture #Engineering #Management #OpenSource