Viewing profile — crimsonalucard1

Doesn't the net CO2 in the air increase? So you harvest CO2 to into fuel. That fuel is burned and the CO2 is released back into the air. So net difference is zero. But to harvest t…

>If you say IO is the bottleneck, then you're claiming there is no significant difference between python and node. That's what a bottleneck means. This is my claim that this SHOULD…

I'm hoping that other then treating diseases this thing can aid with enhancement.

I think you need to pause before considering this route. Are you that exceptional? This level of intelligence is incredibly rare and unless you're 100% sure you're capable of this,…

>Unless you've actually profiled the thing and shown where the time is used, all your assertions are nonsense. It's data science that is causing this data driven attitude to invade…

>Well, it's odd that you say that, when previously you were claiming that it was caused by Python. Is it caused by Python, or is Python negligible? It's not odd. Think harder. I'm …

> I just think that your comparison with _node.js_ when there are a bunch of confounding variables is nonsense And I'm saying all those confounding variables you're talking about a…

>Your logic makes perfect sense, in a world where I/O bound processes, JIT versus interpretation differences, garbage collection versus reference counting differences, etc., don't …

Except the problem here is that those tests were bottlenecked by IO. Whether you're testing C++, pypy, libuv, or whatever it doesn't matter. All that matters is the concurrency mod…

As a general rule it works. Work friends are not friends. There are exceptions but don't expect anything.

Except IO is the bottleneck here. The concurrency model for IO should determine overall speed. If python async is slower for IO tasks then sync then that IS an unexpected result an…

When I talk about async await I'm talking about everything that encompasses supporting that syntax. This includes the I/O event loop. So really we're in agreement. You're talking a…

Bottleneck is IO. Concurrency model should be the limiting factor here. NodeJS is faster than flask because of the concurrency model and NOT because of the JIT. The python async im…

NodeJS primitives are enough to produce the same functionality as flask without the need for an extra framework.

Right but this test focused on concurrent IO. The bottleneck is not the interpreter but the concurrency model. It doesn't matter if you coded it in C++, the JIT shouldn't even be a…

The database is the bottleneck. JIT or even C++ shouldn't even be a factor here. Something is wrong with the python implimentation of async await.

Yep and this test being shown is actually saying that about 5 sync workers acting on thousands of requests is faster then python async workers. Theoretically it makes no sense. A T…

>And no I'm not interested in whatever benchmark you're going to want to post, That's rude. Let's put it this way. NodeJS and nginx leveled the playing field. It destroyed the lamp…

No man. Nodejs will beat the flask benchmark. For this specific test there is no downside to async. What’s going on here is python specific.

This is not what is happening with flask/uwsgi. There is a fixed number of threads and processes with flask. The threads are only parallel for io and the processes are parallel alw…

Yeah except nodejs will beat flask in this same exact benchmark. Explain that.

I see this elitist attitude all over the internet. First it was people saying “Guys why are you over reacting to corona the flu is worse.” Then it was people saying “Guys, stop buy…

Dynamic code upgrades? Can you explain what that is and why a type system will prevent that from happening?

Yeah but usually that's not the case. Usually you can get it back. I would say more often than not it's reversible.