Archive inactive frameworks

[krausest]

According to the deprecation policy I'd like to archive some inactive frameworks. Archived frameworks will appear in the history section in the README with a link to the last result table they were included it. The cleanup allows adding new implementations while keeping the benchmark duration bearable.

I'm informing the contributors in this issue. Please let me know if there are good reasons to keep the implementation.

The following candidates appear to have litte activity in the last year. Is it OK to archive them?

• [ ] vuerx-jsx @ryansolid
• [ ] ko-jsx @ryansolid
• [ ] mobx-jsx @ryansolid
• [x] uhydro @Krutsch: done
• [x] domdiff @WebReflection (I know feels like groundhog day, but maybe it turns out differently a year later): done
• [x] neverland @WebReflection: done
• [x] lighterhtml @WebReflection: done
• [x] heresy @WebReflection: done
• [x] hullo @arturkulig done
• [x] resonatejs @CodeMonkeyAlpha: done
• [x] etch (repo is readonly): done
• ~~s2 @gr0uch~~
• ~~redom @pakastin~~
• [x] endorphin @sergeche: done
• [x] sifrr @aadityataparia: done
• [x] 1more @Freak613: done
• ~~doohtml @hman61~~
• [x] sledgehammer (repo is readonly): done
• [x] domvm: done
• [x] fullweb-helpers (repo is readonly): done
• [x] fullweb-template (repo is readonly): done

(legend: checked = will be archived, strike through = will be kept) Non-keyed will follow...