Evan Carroll
Looking at the code we have different options to fixing this, 1. Make it such that all BuilderErrors derive `Eq`, and `PartialEq`. 2. Make it such that all BuilderError implement...
So then we should be clear we don't support `Eq`, or `PartialEq` for the BuilderError, and that subsequently you can't test the error you returned with `assert_eq!()`? Seems like it...
I'm not a fan of this patch, the system currently sucks and it needs a total rewrite. It's a disgusting mess. That said, this is a step in the right...
Removing JQuery UI is awesome though. Fuck that system with a load of bricks. @michaelpelletier++ What do you guys think of relying on Bootstrap, and migrating everything to use Bootstrap...
I vote for lodash if we're going that direction. It'll run on the server-side/dev code if we write it. That said man, beggers can't be choosers. The big obstacle is...
Can we either fix this stuff, or yank it and let's rebuild it with new Tech?
I think rewriting the whole question interface would be beneficial to begin with. The user should not type in anything but the ID and the weights. The question and answer...
It's no different if we're copy-pasting it. Lol. If they want to shut us down, they can. They can always claim the questions were copyrighted. We can't get around that...
You have to know the primary key. The rest is all room for error and unneeded. We use it to generate a description, but we could easily cache it client...
you're so close man. come on fork it and submit a patch.