I've personally never liked having to go through Angular here, and wished the playground was written with basic events and DOM manipulation. I don't think Angular is very helpful for this application, and its non-idiomatic-Go API is cumbersome.
Is it okay to try to remove the dependency now and rewrite the playground to use plain DOM elements and events? Thoughts, opinions?
If this sounds like a good direction, I might give it a try and see if it leads to a better codebase or not.
neelance
commented
7 years ago
I see in https://github.com/neelance/go-angularjs/commit/ae3e8ed59a0f7fae4a3be7117ce13e78e02331ed that go-angularjs has been deprecated. /cc @neelance The playground currently uses it.
I've personally never liked having to go through Angular here, and wished the playground was written with basic events and DOM manipulation. I don't think Angular is very helpful for this application, and its non-idiomatic-Go API is cumbersome.
Is it okay to try to remove the dependency now and rewrite the playground to use plain DOM elements and events? Thoughts, opinions?
If this sounds like a good direction, I might give it a try and see if it leads to a better codebase or not.