2,635 karma · joined August 26, 2008
./src/os/unix/ngx_file_aio_read.c
API's doc https://man7.org/linux/man-pages/man3/aio_read.3.html
Even though the source is there don't mean it's compiled or used though. Might or might not be. No idea about the details.
Caching the front page, server side, instead of rendering it on every request would have given similar result -- my guess. Specially when the query was taking 900ms.
Started with Lenovo. Second one was MSI. And now have moved to cheaper ones as Linux, at least Fedora, runs on anything I buy.
As Linux runs any laptop I happen to be buying without any glitch.
When both can be used simultaneously you can now gradually move from one to the other, or revert back as needed.
This is what I followed.
And then write sql statements for everything else.
A fairer comparison would have been [ total number of reported crashes ] / [ total number of cars on road ].
Comparing it with sales growth will show poor performance for older brands which have a lot of cars on the road vs newer brands that are just release cars now.
The key part. It wasn't possible to write Ruby extensions in Zig until a few weeks back. Now you can.
> I have a story of rewriting part of our production code as Rust extension, which turned out to be 3-4 times faster, but we ditched it anyway, because maintenance cost would be too high.
My solution to this problem is to stick with C. Your code won't get obsolete. Most people are still using C99, and not much has changed in 20 years, even in recent versions.
I had been seeking this confirmation. Both can, and will be using one another's data.
And Parent indicates Overture like an administrative fork of OSM.
First thing I do when moving to a new server is check whether the new box's IP is black listed in any mail-blacklist-dns service. If not, it's good.
What I have also found is that Gmail and other services are relatively forgiving on your server's IP, but marks mail as spam based on context and content.
So Google had the tech for some time now. But like Sony in the 90s they were reluctant to release it fearing it will hurt their current business.
Therefore someone else had to disrupt the market. Google won't do it to themselves.
For context Samba and NFS had historically been buggy or exploitable since the 90s.
> Before Google acquired Youtube, the majority of the code was initially written in PHP, but there were many restrictions and clutters in PHP at the time, so after acquiring Youtube by Google, they moved to Python as one of the core parts of its backend programming.
Python started after google's acquisition. It's not that youtube was "never written in PHP".
https://ourtechroom.com/tech/technologies-programming-langua...
Link :
The source :
https://twitter.com/TechEmails/status/1433837480449613839/ph...
Discussed on HN, 2021
Edit : Python. The point remains the same.
It might be more than what you need, but your needs will increase. The above cost will not.
And also there was the 4th generation language movement at that time, 4GL. Defined by coding like writing English sentences, and not much algo. More akin to our no-code, low-code trend. SQL was also a child from 4GL. C/C++ was then seen as 3GL. And then we can now watch 3GL ultimately took over 4GL, at least until now, for half a century.
Tidbits.
Corrected: COBOL was 3GL.
Guess he's getting full time busy with that.
Until then, human are needed to build those AIs.
I might implement it in C, as soon as I get some time.