(I suppose the SQL part of my app is not the problem though, rather the number crunching that happens on the data returned. I do lots of caching on the results instead to make the site seem responsive.)
Must-have Django packages
51–60 of 100 posts
Re: Must-have Django packages
#52What are people using these days for compiling their static assets (js minification + concatenation, etc)? We have been using django-pipeline but it has been a nightmare.
Re: Must-have Django packages
#53What are people using these days for compiling their static assets (js minification + concatenation, etc)? We have been using django-pipeline but it has been a nightmare.
and with compress like this: {% compress js %}
{% endcompress %}
so that referencing static files is consistent.[0]: https://github.com/jezdez/django_compressor
[1]: https://docs.djangoproject.com/en/dev/ref/contrib/staticfile...
Re: Must-have Django packages
#54Amusingly, my must-have Django packages are mostly things that replace large chunks of Django (Jinja2 for templates, a DB connector/ORM for whatever database the project needs, which even for PostgreSQL is often plain SQLAlchemy). I guess I'll just use flask.py or something for my next project. This is not meant as criticism, just my personal experience.
I myself love Django, though I find some parts of it a bit over-engineered (in the Java style). That is changing for the better in recent releases though. I'm thinking the render_to_response stuff and management commands, etc.
Re: Must-have Django packages
#55"Django REST framework is an insane framework" I'm fed up with this kind of oppressive language. This is heteronormative and is discriminatory to the mentally ill. It's stuff like this that leads to the imbalance and under-representation in the industry. Let's boycott this author. (I would love not to have to write " " but having seen some of the comments here, I think I need to. I wonder how many white-knights-for-w…
An experiment: Next time you reach for some euphemism for mental illness, consider a couple of alternative phrasings (that do not use the euphemism). Decide if the alternatives are clearer or more precise. I don't run around taking issue with word choices, but if I run that experiment, I usually choose one of the alternative phrasings.
Re: Must-have Django packages
#56Earlier quoted context omitted.
I think
I was not trolling by the definition I know. I just thought that it might lead to an interesting conversation. It's just too hard to communicate on the internet, especially with people who don't share your conversational goals. I think I just found a new year's resolution.
"submit a deliberately provocative posting to an online message board with the aim of inciting an angry response."
Message board? Check! Deliberately provocative? Check! Angry responses? Check! Must be trolling.
Re: Must-have Django packages
#57Earlier quoted context omitted.
I was not trolling by the definition I know. I just thought that it might lead to an interesting conversation. It's just too hard to communicate on the internet, especially with people who don't share your conversational goals. I think I just found a new year's resolution.
Judging by your history on this site, you've done nothing but trolling.
My original point was that the absolute application of principles designed to bring about equality could be harmful and that we need to apply contextual understanding to language. If the expression of that idea makes you angry, that's fine, but it's not trolling.
Anyway, I'm bowing out of this thread as it doesn't look like pursuing this idea is constructive.
Re: Must-have Django packages
#58Everyone recommends the django-toolbar for spotting slowdowns in your SQL... ok, installed it. I almost never see any tips on how to actually do that though. What now? (I suppose the SQL part of my app is not the problem though, rather the number crunching that happens on the data returned. I do lots of caching on the results instead to make the site seem responsive.)
Re: Must-have Django packages
#59Everyone recommends the django-toolbar for spotting slowdowns in your SQL... ok, installed it. I almost never see any tips on how to actually do that though. What now? (I suppose the SQL part of my app is not the problem though, rather the number crunching that happens on the data returned. I do lots of caching on the results instead to make the site seem responsive.)
If you're doing a lot of # crunching, you might try using Cython for those bits. You can get a 10x speedup without changing semantics and just annotating types.
Re: Must-have Django packages
#60"Django REST framework is an insane framework" I'm fed up with this kind of oppressive language. This is heteronormative and is discriminatory to the mentally ill. It's stuff like this that leads to the imbalance and under-representation in the industry. Let's boycott this author. (I would love not to have to write " " but having seen some of the comments here, I think I need to. I wonder how many white-knights-for-w…