Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mzimbres
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
4 ms
·
1.
▲
by
mzimbres
2y ago
> In my experience simple blocking code is incredibly misunderstood. I don't think so. You can't even implement a full-duplex protocol properly with sync IO since reading and writing can't happen at the same time on the sa
2.
▲
by
mzimbres
2y ago
> In actual real applications it is not always possible This depends on what are your expectation. IO operations must suspend to wait for data read and writes, therefore it is not possible to avoid Async/Await. In other cases you mi
3.
▲
by
mzimbres
2y ago
Only in poorly designed code you have problems like this where Async Await goes viral. It can be avoided by spiting libraries into an IO part that uses Async/Await and a protocol part that is sans-io. Using async code to access data th
4.
▲
by
mzimbres
2y ago
Here is a low hanging fruit for governments around the world fighting low birth rates. Allow your people to work from home and they will start having more babies, simplle as that. I am my wife had to switch jobs just so we could work more f
5.
▲
by
mzimbres
2y ago
I wonder how did they shared the meat with the rest of the group after chasing down the prey for an hour in random directions.
6.
▲
The costs of asynchronous abstractions (C++)
(github.com)
1 points
by
mzimbres
3y ago
|
0 comments
7.
▲
by
mzimbres
3y ago
Implementing full-duplex protocols asynchronously is much simpler.
8.
▲
by
mzimbres
4y ago
So why rotten meat smells terrible and a steak delicious? Why would we evolve that perception of something that nutritious and which could prevent me from starving. Why my nose keeps telling me to keep away from rotten meant?
9.
▲
by
mzimbres
4y ago
I haven't created Redis itself but a Redis client library. It all started with a chat server I wanted to write on top of Boost.Beast (and by consequence Boost.Asio) and at the time none of the clients available would fill my needs and
10.
▲
by
mzimbres
4y ago
> But as more and more engineers joined us, some shortcomings > of C++ came to bite us: unreadable coding style, memory leak, > segmentation fault, and more. * unreadable coding style: This is not a C++ problem. * memory leak: Memo
11.
▲
The performance of Redis clients with automatic pipelining
(mzimbres.github.io)
1 points
by
mzimbres
4y ago
|
0 comments
12.
▲
by
mzimbres
5y ago
Senders and Receivers is the next big thing Eric is delivering to C++, stay tuned.
13.
▲
by
mzimbres
5y ago
Human beings have been living in europe for over 100,000 years. White skin doesn't seem to be older than a 10,000 years (see the skin analysis of the first briton). I don't think it would have taken so much time to evolve white sk
14.
▲
by
mzimbres
5y ago
For the purpose of climate change I believe it would be enough to breed elephants that adapt well to could climates and populate the area with them.
15.
▲
by
mzimbres
5y ago
Nobody postulated that the speed of light is constant because it was obvious: light just like every other wave has a constant speed in the medium though which it propagates. The fact that nothing can go faster is a consequence of the Lorent
16.
▲
A command line tool to display tree-like data contained in TSV files
(github.com)
4 points
by
mzimbres
6y ago
|
0 comments