Skip welcome & menu and move to editor
Welcome to JS Bin
File
Add library
Share
Login or Register
Blog
Help
Load cached copy from
  • Run with JS
  • Save
  • Share
  • …
 
<!DOCTYPE html>
<html>
<head>
<script src="//ajax.googleapis.com/ajax/libs/angularjs/1.3.2/angular.min.js"></script>
  <meta charset="utf-8">
  <title>JS Bin</title>
<link href='http://fonts.googleapis.com/css?family=Andika' rel='stylesheet' type='text/css'>
</head>
<body ng-app="app" class="app">
  <h1>Angular's Global Context</h1>
  <div class="subtitle">AngularJS, the bad parts... :-(</div>
  
  <div class="smaller">
    Color Code:<br />
    <div class="app">- Black: "app" module (depends on mod1 and mod2)</div>
    <div class="mod1">- Blue: "mod1" module (depends on nothing)</div>
    <div class="mod2">- Red: "mod2" module (depends on nothing)</div>
  </div>
  <br />
  <br />
  
  The module "app" depends on mod1, so this should render
  <first-mod></first-mod>
  
  <br />
  <br />
  
  The module "app" depends on mod2, so this should render:
  <second-mod></second-mod>
  
  ... but it does... Because app depends on both mod1 and mod2
  
  <br />
  <br />
  
  What it should be is, for mod2 to use mod1 stuff, it MUST require it as a dependency.
  
  
  <br />
  <br />
  
  Why is this bad? Because it makes it IMPOSSIBLE to enforce modularity in angular without some kind of preprocessor to somehow parse all the templates and understand which module belongs to which template and... no... stop... just stop....
​
  <br />
  <br />
  
  So, Angular's <strong>super lame</strong> then right? No, it's not super lame. It's still super awesome. But this part about angular... Yeah, this is a bad part :-(
</body>
</html>
Output

You can jump to the latest bin by adding /latest to your URL

Dismiss x
public
Bin info
kentcdoddspro
0viewers