<commit_before># snuggsi

Browser extensions.

https://w3c.github.io/webcomponents/spec/custom

_Why?_ We don't need _(yet)_ another framework.
We need _"syntactic sugar"_ around new spec driven browser features.
"Browser extensions" if you will.
For instance the _"DOM Extensions"_ are great to use
as you are always interacting with Living DOM nodes.
This gives you the ability to gradually incorporate
your extension of choice a la carte into your existing client side code!
Best of all, works in your favorite browser today! _for the most part_.
This means you can try out the extensions just by "Copy & Pasta"'ing directly
into your console straight from the README!

Modern client side Javascript specs have been moving at light speed the past couple of years.
Best to avoid front end frameworks wherever possible as the browser
can provide you with all you need in 2017! If you are uncomfortable
with a particular browser's javascript implementation then
pollyfills are typically trivial to implement.
These backwards compatibility snippets can be injected
prior to your code. In the future they removed when you
feel your respective browser landscape has matured.
And if a feature we've implemented doesn't work to your liking feel free to
[submit an issue](https://github.com/snuggs/snuggsi) and we will attempt
a [polyfill](https://en.wikipedia.org/wiki/Polyfill) for you ASAP!

*Using modern browser specifications have allowed us to decrease
framework code by ~80%*. Hence why these are _"extensions"_ and<commit_msg>Update Mission Statement<commit_after># snuggsi

Browser extensions.

https://w3c.github.io/webcomponents/spec/custom

_Why?_ We don't need _(yet)_ another framework.
We need _"syntactic sugar"_ around new spec driven browser features.
_"Browser extensions"_ if you will.
For instance the _"DOM Extensions"_ are great to use
as you are always interacting with Living DOM nodes.
This gives you the ability to gradually incorporate
your extension of choice a la carte into your existing client side code!
Best of all, works in your favorite browser today! _for the most part_.
This means you can try out the extensions just by "Copy & Pasta"'ing directly
into your console straight from the README!

Modern client side Javascript specs have been moving at light speed the past couple of years.
Best to avoid front end frameworks wherever possible as the browser
can provide you with all you need in 2017! If you are uncomfortable
with a particular browser's javascript implementation then
pollyfills are typically trivial to implement.
These backwards compatibility snippets can be injected
prior to your code. In the future they removed when you
feel your respective browser landscape has matured.
And if a feature we've implemented doesn't work to your liking feel free to
[submit an issue](https://github.com/snuggs/snuggsi) and we will attempt
a [polyfill](https://en.wikipedia.org/wiki/Polyfill) for you ASAP!

*Using modern browser specifications have allowed us to decrease
framework code by ~80%*. Hence why these are _"extensions"_ and
{'fraction_non_alphanumeric': 0.0475415174210355, 'fraction_numerical': 0.004558775643112993, 'mean_word_length': 4.965048543689321, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 6, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6552061', 'n_tokens_mistral': 789, 'n_tokens_neox': 728, 'n_words': 445}