Stupid. NIH.
"Why didn’t you just use React?" "We like knowing in detail how code works". Such a common motif these days. Cool I hope that was worth 2 months of x devs' time.
"Why didn’t you just use React?" "We like knowing in detail how code works". Such a common motif these days. Cool I hope that was worth 2 months of x devs' time.
Reading bad code is harder than writing bad code.
But after some amount of time, the ease of simply reading someone else's working codebase compared to debugging/designing and reading your own becomes overwhelming.
So off the bat, writing is easy, but as soon as the amount of code you've written gets near to the complexity of what you avoided reading, you're going to wish you'd just read up a bit.
There are a lot of serious javascript nerds who defensively coded the living crap out of react (and for that matter ember, angular, etc)... starting from scratch in light of that seems quite intense. Even if I were going to embark on such a quest (let's say for pure functional programming style), I'd probably start looking at the ideas in Om (clojurescript react) before writing my own.
I think I'm biased towards not coding because laziness pays dividends later once maintenance, etc come into play.