title: Are vuex mapGetters even worth using?
body: <p>So I believe the title introduces my question. Given you're introducing a new dependency in each component you want to use mapGetters in, this adds bloat to your package. </p>
  
  <p>This also means your component is now specifically bound to Vue, which is 1 more thing to contend with were you to port components over to another framework like React. </p>
  
  <p>Consider these 2 computed property lists: </p>
  
  <pre><code>import { mapGetters} from 'vuex'
      computed: {
          ...mapGetters({
            active:'interface/active',
            mode:'interface/mode',
            views:'interface/views',
          }),
      }
  </code></pre>
  
  <p>vs </p>
  
  <pre><code>computed: {
        active:() { return this.$store.getters['interface/active'],
        mode:{ return this.$store.getters['interface/mode']},
        views:{ return this.$store.getters['interface/views']},
  }
  </code></pre>
  
  <p>Sure the latter is a tad bit more verbose, but nothing overly bad. You've still got all your getter data the same way in either scenario. To be this seems like totally unnecessary fluff for the small benefit of saving a few characters.  </p>
  
  <p>The former example weighs in at 207B (201 characters)</p>
  
  <p>while the later example weights in at 207B (201 characters).</p>
  
  <p>To me that means in terms of type savings, there's virtually none to be had. However I do concede that the former is more readable, portable and ultimately easier to maintain as your relevant data is all in 1 spot. </p>