Is case sensitivity important? Tom is going to implement a new programming language of his invention.  But before actually starting working on it, he wants to know whether his language should be case sensitive or not.

On one hand, case insensitivity seems more easy to implement to him, but he worries that it could cause a lack in the possibilities of combinations of characters that form a variable, meaning that longer variable names should then be used to avoid naming clashes (for an example, you can use Hello, HEllo, heLLo and a bunch of other possibilities if the language is case sensitive, but only HELLO if not).

But Tom is a meticulous person, so just a worry isn't enough for him. He wants to know the numbers.

The challenge

Write a function (or a full program if your language doesn't support them) that, given an integer n as the input, outputs (or returns) the difference in the number of permutations possible for a string of length n with case sensitivity and without.

In Tom's language, variable names can include all alphabet letters, underscores and, starting from the second character, digits.

Testcases

Input (length of the variable) -&gt; Output (difference between the possibilities with case sensitivity and the possibilities with case insensitivity)
0 -&gt; 0
1 -&gt; 26
2 -&gt; 2340
5 -&gt; 784304586
8 -&gt; 206202813193260
9 -&gt; 13057419408922746


Non-competing C++ reference implementation

void diff(int n) {
    long long total[2] = {0, 0}; //array holding the result for case insensivity ([0]) and case sensitivity ([1])

    for (int c = 1; c &lt;= 2; c ++) //1 = insensitivity, 2 = sensitivity
        for (int l = 1; l &lt;= n; l ++) //each character of the name
            if (l == 1)
                total[c - 1] = 26 * c + 1; //first character can't be a number
            else
                total[c - 1] *= 26 * c + 1 + 10; //starting from the second character, characters can include numbers

    std::cout &lt;&lt; total[1] - total[0] &lt;&lt; std::endl;
}


Scoring

Tom likes golf, so the shortest program in bytes wins.

Note

It's okay if maybe the last two testcases aren't right because of numerical precision. After all, I am not even sure my code handled number 9 correctly.
JavaScript (ES7), 43 bytes



f=(n,a=53,b=27)=&gt;n?--n?f(n,a*63,b*37):a-b:0
&lt;input type=number value=0 min=0 max=9 style=width:4ch oninput=o.textContent=f(+this.value)&gt;&lt;div id=o&gt;0&lt;/div&gt;




Not reduces day today - 55 bytes.