Semantic UI components css class names vs Google's Material Design Lite for web

gistfile1.html

<!-- LOL -->

<!-- http://semantic-ui.com/elements/button.html -->
<button class="ui button">
  Follow
</button>

<!-- http://www.getmdl.io/components/index.html#buttons-section -->
<button class="mdl-button mdl-js-button mdl-button--raised mdl-js-ripple-effect">
  Button
</button>

<!-- http://semantic-ui.com/collections/table.html  -->
<table class="ui celled table">
  <thead>
   
<!-- http://www.getmdl.io/components/index.html#tables-section -->
<table class="mdl-data-table mdl-js-data-table mdl-data-table--selectable mdl-shadow--2dp">
  <thead>

@jlukic @paxer: The question is: What is the focus? I think of GMD more as a kit to create web-components, while SemanticUI already has these.

So while with GMD you can precisely decide how a element should look with class-styling, it is a lot of overhead if you already have functioning components like those in SUI.

So comparing two frameworks which (imho) have different targets is not very elegant.