Consider: How deeply does a commercial piece of software like, say, the Oracle or DB2 database, or a virtualization product like VMWare, or a device driver, interact with an OS like Linux? And (as long as no significant actual code is lifted from the other entity) does that really “in...
It is useless to say "don't do this" without offering an working alternative if you have several bosses entering which say that they cannot work any more. It is useless to say "let the error occur and let it roll back" if that does not happen. It is useless ...
or even languages which you use and don’t like. Everyone does that already. I don’t want to hear yet another rant about why Ruby sucks from a Java programmer, why Java sucks from a Factor programmer, why Lisp sucks from a Javascript programmer, etc. I’m not even interested in heari...
There are aspects of Linux that I find frustrating, even though I don’t talk about them often. Here are five points that I encounter almost daily:
. . . . “The crucial question is whether the manner of expression is basically incompatible with the normal activity of a particular place at a particular time. . . “The [F]irst [A]mendment does not guarantee the right to communicate one’s views at all times and places or in any...
Christians, God does not want His truth to bend. He wantsyouto bend. What does that mean? It means that in our methodology and in our communication, we need to bend. We need to adapt. We need to reach out. We need to sacrifice. ...
Incompatible locks between the DELETE and INSERT is a plausible explanation for what you're seeing with your table. Keep in mind I don't do trickle inserts in production, but the current locking implementation for deleting rows from a delta rowgroup seems to require a UIX...
I'm opening this issue because: I had been using npm version 5.0.3 in my project and the package-lock.json file had been working exactly as I expected. However, upon updating my npm version to 5.3.0, my package-lock.json no longer works...
defined-as-deleted constructor/operator would cause the whole class to be non-trivial. A similar problem existed with destructors. C++17 clarifies that the presence of such constructor/operators does not cause the class to be non-trivially copyable, hence non-trivial, and that a trivially copy...
wanted to, though I can't imagine why). Why does any normal language need two functions just for copying a string? Why can't we use the assignment operator ('=') like for the other types? Oh, I forgot. There's no such thing as strings in C; just a big continuous stick of ...