title: Why does ASP.NET MVC 4 have so many NuGet packages and which are truly important?
body: <p>As the title says, why do the ASP.NET MVC 4 projects have soooo many NuGet packages? Is the entire framework split into packages now? Which ones are truly important for an empty project that will be a website, no API, etc?</p>
  
  <p><strong>UPDATE</strong></p>
  
  <p>To clarify, I'm not having issue, well, unless you count basic confusion as one. I just want to know why new MVC 4 projects have so many packages installed by default? An empty project has one full page of packages. An internet project has three full pages of packages.</p>
  
  <p>I'm just curious why this is because my current MVC 3 projects use at max five packages.</p>