Alex I find the notion that you think changing terms that have bad racial
connotations to be "embarrassing" to be entirely without merit. It is not
embarrassing to consider the feelings of Black and other minority people
when using language. Moreover, racism is not simply a US only phenomenon.
I wonder about the end-result payoff of this approach. In general,
Django/Python code is not going to be I/O bound, which is where
asynchronous approaches are going to get the bang for your buck. Even when
it comes to DB access—the DB is a lot faster than the python and django
code running
Chiming in. As a long-time django user (nearly a decade), websockets is an
area that the project on the whole is very, very, far behind the leading
edge of the web industry. It's great, often desirable, to not be *on* the
leading edge, but in my opinion, the project is too far behind it.
There
AM UTC-4, John Obelenus wrote:
>
> Can I ask a dumb question? Why did you only discover this with adding
> Whitenoise, and not the default/common middleware stack that comes in
> django? Asking that question in another way: What is specific to whitenoise
> that this constant loadin
Can I ask a dumb question? Why did you only discover this with adding
Whitenoise, and not the default/common middleware stack that comes in
django? Asking that question in another way: What is specific to whitenoise
that this constant loading of middleware causes such a perf hit? This
question
