From 2ee45a82b4b95eb5f17fc82426d0c1b4a6fd9fb9 Mon Sep 17 00:00:00 2001 From: Matthew Griffith Date: Mon, 1 Jul 2019 20:54:50 -0400 Subject: [PATCH] Remove project post because I ended up doing it --- notes/projects/BenchmarkSuite.md | 12 ------------ 1 file changed, 12 deletions(-) delete mode 100644 notes/projects/BenchmarkSuite.md diff --git a/notes/projects/BenchmarkSuite.md b/notes/projects/BenchmarkSuite.md deleted file mode 100644 index 9fcf22f..0000000 --- a/notes/projects/BenchmarkSuite.md +++ /dev/null @@ -1,12 +0,0 @@ -# Benchmark Suite - -It would be nice to be able to keep track of `elm-ui`'s performance characteristics and the easiest way to do that would be to write a benchmark suite. - -[This project](https://github.com/webbhuset/test-elm-performance) did a great job implementing a critical rendering path benchmark. - -However, it's pretty awkward for me to use when I'm doing any sort of performance-based development. - -I'd love it if someone were to take that codebase and: - -- Make the benchmark runnable via cli and output results as json, likely via [headless chrome](https://developers.google.com/web/updates/2017/04/headless-chrome). -- Make it really easy to test new view functions. Meaning I'd love the ability to just write a view function and run a tool which would benchmark it render-wise. \ No newline at end of file