Exercise 1: Choosing a Framework for a Large Enterprise Team — Possible Solution
====================================================================

THE SCENARIO'S OWN REQUIREMENTS
------------------------------
The team wants three specific things: strict conventions, enforced
structure, and TypeScript from day one - and is explicitly willing to
accept a steeper learning curve to get them.

MATCHING AGAINST THE LESSON'S "HOW TO CHOOSE" SECTION
------------------------------
Per this lesson, Angular is recommended for exactly this profile: "A
large team or enterprise app where consistency, structure, and
one-official-way-per-task matter more than flexibility; TypeScript and
strong conventions are a plus, not a cost." Angular is also the only
one of the three where TypeScript is mandatory rather than optional
(per the "At a Glance" table), and its "Opinionatedness" row is rated
High - "batteries included" - compared to React's Low and Vue's
Medium.

WHY THE OTHER TWO DON'T FIT AS WELL
------------------------------
React's own strength - "unmatched flexibility, pick your own stack" -
is close to the opposite of what this team is asking for: flexibility
means the team itself has to decide and enforce every convention
rather than getting one built in. Vue sits in the middle and would
still work reasonably well, but its own "Weaknesses" list notes it's
"less common in large enterprise shops" and lacks Angular's single
corporate backer, both real considerations for a large, long-lived
internal app.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly identifies Angular as the fit, ties the choice directly
back to the lesson's own explicit "How to Choose" row for Angular
rather than a generic impression of the framework, and explains why
the accepted trade-off (steeper learning curve) is exactly what the
lesson itself names as Angular's own cost for this profile of team.