Is there any reason not to use static class methods for a Service in angular 2?
<p>I'm building my first Angular 2 app using Ionic, and am building out a couple of services.  The tutorial doesn't use static methods, but to me, it seems that in my use case, static methods and properties are the way to go.  To NOT use static methods would be like this:</p>

<pre><code>import {MyService} from "../services/MyService";
@Component({
  templateUrl:"page.html",
  providers: [MyService]
})

export class MyNewClass{
    constructor(private myService: MyService){}

    //to use:
    this.MyService.get()
}
</code></pre>

<p>VS </p>

<pre><code>import {MyService} from "../services/MyService";
@Component({
  templateUrl:"page.html"
})

export class MyNewClass{
    constructor(){}

    //to use:
    MyService.get()
}
</code></pre>

<p>Now in my use case, <code>MyService</code> data doesn't change across the whole app.  I load up the data a single time, and need to use it all across the app.  I would like to have a static array in MyService that contains the info that all the other classes use.  The benefit to this, in my opinion, is that it is very clear that there is a single instance across the whole app - no guessing.  Also, I don't have to write <code>providers: [MyService]</code>, and don't have to inject it into the constructor, which I think would be a very good things as I don't want the constructor parameters to become unreadable due to length. Is there anything wrong with this?</p>