title: why does laravel's facade behave like a singleton?
body: <p>I know that laravel uses facades. but basically I can't wrap my head around it why they use it.  Let's take a look at maybe File facade class. Why did they make the File class as facade when they had already FileSystem class? couldn't we write in our code something like this?</p>
  
  <pre><code>$file = new \Illuminate\FileSystem();
  $path = $file-&gt;get(public_path("test.txt"));
  </code></pre>
  
  <p>but laravel decided to use File facade class after which I can write something like this:</p>
  
  <pre><code>$path = File::get(public_path("test.txt")); 
  </code></pre>
  
  <p>Where does the beauty reside? if you look at facade pattern, it gives you easier interface to do big jobs and not use 10 lines of code when you can do it with facade in 2 lines, but laravel's facade makes it hard to understand. </p>
  
  <p>Could it be because of they made facade class so that it works like a singleton and this is its amazing side? but then why is singleton amazing ? </p>
  
  <p>I don't understand what's the idea for laravel's facade. </p>