3 ms·
That's an interesting point. So what's the counterargument?
by orblivion 17y ago
That's an interesting point. So what's the counterargument?
- forsaken 17y agoRolling your own is silly and counter productive. Something needed to be chosen, and JQuery is the obvious choice. Totally pragmatic.
- trusko 17y agoI agree. I think it was good decision as well.
- handelaar 17y agoThat django-admin is a discrete application. Django itself, and thus your app, remains resolutely uncommitted to one particular JS framework.
- ubernostrum 17y agoI summarized my feelings here: http://news.ycombinator.com/item?id=942771 http://news.ycombinator.com/item?id=942771
- acdha 17y agoI think that's a big argument for something like jQuery which takes care not to declare tons of globals or extend base classes. If the change doesn't use jQuery.noConflict() it probably should if for no reason other than avoiding any possibility of confusion when someone sees $() in code. As for extensive customizations, how much additional concern does this add? It seems unlikely that those people aren't also using admin hacks to work around the areas which didn't used to be user-serviceable so they're probably going to need to be careful about upgrades for many other reasons. This at least gives a consistent baseline and widely-used extension mechanism for future work.
- bad_user 17y agoMy customizations all use jQuery anyway :)