why does laravel's facade behave like a singleton?











up vote
1
down vote

favorite












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?



$file = new IlluminateFileSystem();
$path = $file->get(public_path("test.txt"));


but laravel decided to use File facade class after which I can write something like this:



$path = File::get(public_path("test.txt")); 


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.



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 ?



I don't understand what's the idea for laravel's facade.










share|improve this question






















  • laravel.com/docs/5.7/facades
    – Ian Bell
    Nov 21 at 14:06










  • It's to make some features swappable, like for example Storage can be file, AWS, dropbox etc.
    – Thomas Moors
    Nov 21 at 14:07















up vote
1
down vote

favorite












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?



$file = new IlluminateFileSystem();
$path = $file->get(public_path("test.txt"));


but laravel decided to use File facade class after which I can write something like this:



$path = File::get(public_path("test.txt")); 


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.



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 ?



I don't understand what's the idea for laravel's facade.










share|improve this question






















  • laravel.com/docs/5.7/facades
    – Ian Bell
    Nov 21 at 14:06










  • It's to make some features swappable, like for example Storage can be file, AWS, dropbox etc.
    – Thomas Moors
    Nov 21 at 14:07













up vote
1
down vote

favorite









up vote
1
down vote

favorite











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?



$file = new IlluminateFileSystem();
$path = $file->get(public_path("test.txt"));


but laravel decided to use File facade class after which I can write something like this:



$path = File::get(public_path("test.txt")); 


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.



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 ?



I don't understand what's the idea for laravel's facade.










share|improve this question













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?



$file = new IlluminateFileSystem();
$path = $file->get(public_path("test.txt"));


but laravel decided to use File facade class after which I can write something like this:



$path = File::get(public_path("test.txt")); 


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.



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 ?



I don't understand what's the idea for laravel's facade.







php laravel






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 21 at 13:30









Nika Khurashvili

6049




6049












  • laravel.com/docs/5.7/facades
    – Ian Bell
    Nov 21 at 14:06










  • It's to make some features swappable, like for example Storage can be file, AWS, dropbox etc.
    – Thomas Moors
    Nov 21 at 14:07


















  • laravel.com/docs/5.7/facades
    – Ian Bell
    Nov 21 at 14:06










  • It's to make some features swappable, like for example Storage can be file, AWS, dropbox etc.
    – Thomas Moors
    Nov 21 at 14:07
















laravel.com/docs/5.7/facades
– Ian Bell
Nov 21 at 14:06




laravel.com/docs/5.7/facades
– Ian Bell
Nov 21 at 14:06












It's to make some features swappable, like for example Storage can be file, AWS, dropbox etc.
– Thomas Moors
Nov 21 at 14:07




It's to make some features swappable, like for example Storage can be file, AWS, dropbox etc.
– Thomas Moors
Nov 21 at 14:07

















active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














 

draft saved


draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53413147%2fwhy-does-laravels-facade-behave-like-a-singleton%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















 

draft saved


draft discarded



















































 


draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53413147%2fwhy-does-laravels-facade-behave-like-a-singleton%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown