1,909 karma · joined September 24, 2012
for example, a key argument in favor of forks was that fork and knife is vastly superior to chopstick and knife when eating steak. Asian cultures simply don't have this issue, because they don't eat steak, because they don't (historically) have huge pastures for free cattle grazing. in Asian cuisine, meat is served pre-cut, not in large chunks for the diner to cut themselves. therefore, Asians don't have the problem of cutting steak at the table.
similarly, Americans rarely eat soft tofu; although tofu is gaining popularity in the US, mainstream grocery stores and restaurants selling tofu tend to sell firm tofu, probably mainly because it's closer to meat in texture. firm tofu is usually served pre-cut, for various reasons including that firm tofu is usually served with stronger and more uniform flavoring. therefore, Americans don't need to cut their soft tofu at the table.
chopsticks are also useful for taking individual bites out of a shared plate without disturbing the remaining contents. consider taking one bite of a shared salad using a fork: it's impossible to do so without either slightly crushing the remainder of the salad, which is impolite, or using the fork as a spoon, which is highly inefficient (salad falls off easily). Americans don't have this problem because they generally take a large portion of salad using a spoon or tongs, then use the fork to take bites from their own plate where it's acceptable to slightly crush the salad.
edit to add: I enjoy Chinese-American fast food, but like all fast food, it is designed to be cheap, not luxury. it would be like going to an American-style fast food restaurant and complaining that all American food is bad because it gets your hands dirty when eating, or complaining that the cheap disposable plastic utensils are hard to clean (which gets to another point that disposable wooden chopsticks are probably much better for the environment than disposable plastic forks/knives, but that's a digression from a digression)
additionally, if your device has less than a few megabytes of storage, you'll almost certainly be using static linking, which automatically prunes unused code from properly designed libraries.
> Microwave ovens are not tuned to any specific resonance frequency for water molecules in the food, but rather produce a broad spectrum of frequencies, cooking food via dielectric heating of polar molecules, including water. Several absorption peaks for water lie within the microwave range, and while it is true that these peaks are caused by quantization of molecular energy levels corresponding to a single frequency, water absorbs radiation across the entire microwave spectrum.
huh? the official wine packages for ubuntu, debian, and i believe fedora provide separate wine-devel and wine-staging packages, which can be installed in parallel with each other and with distro packages. in fact, debian (and ubuntu) as well as arch provide separate wine and wine-staging packages as part of the distro itself, no separate repo required.
wine has no special support for relocated installations, but no more or less so than any large Unix program; you can install as many copies as you want, but they must be compiled with different --prefixes, and you cannot use different versions of wine simultaneously with the same WINEPREFIX.
therefore, there must at least be several switches between the devices, and realistically, probably one or more routers.
I believe the main reason why gdb kinda stinks is that it can be: traditional Unix-like operating systems typically have smaller components with well-defined interfaces, making them much easier to debug. Windows has too many DLLs, too many interfaces between them, and poor definition of layers. Quick, what's the difference between kernel32 and kernelbase? How do I tell which one a program is using?
This is not to say that Unix-like systems have perfect interfaces, merely that they're generally better-factored than interfaces inside Windows and Windows applications. Further comments can be made of the differences between Windows and Mac "applications" and Linux "programs": for example, the difference is not only in GUI or TUI or CLI: Firefox is an "application", but Notepad and Calculator are "programs"; Paint is a "program", but Paint 3D is an "application".
1. google xxhash, click first result (github)
2. open xxhash.c
3. see it is mostly empty, go back and open xxhash.h. this file is 6k lines (not 20k), it probably has most or all of the implementation somewhere.
4. starting from top of file, read intro docs: "xxHash [...] is proposed in four flavors, in three families: 1. @ref XXH32_family: Classic 32-bit hash function." i will select XXH32 for illustration.
5. scroll down to examples, which calls "return XXH32(string, length, seed);"
6. ctrl-f "XXH32(", could be done in any text editor (even notepad)
7. press enter 6 times
8. see "@brief The implementation for @ref XXH32().", we have probably arrived at the core or reasonably close to it. if that didn't work, then I would try "XXH32 (", which would immediately find the XXH32 function.
of the 6k lines, about 550 are empty, about 2800 are comments, and about 800 are preprocessor directives. the comments appear to be mostly useful comments, not the "/* Frobnicate the bar. */ int Bar::frobnicate()" type which tend to be seen in IDE-overuse projects.
Multiple -filter, -af or -vf options specified for stream 0, only the last option '-filter:v transpose=1' will be used.
-vn, -an, -ss, and -to are specified as output rather than input options, which are much more efficient.why not? prosecute them normally, if they show up then the trial proceeds as usual, if not then convict them in absentia and then forfeit the goods. why does this require a whole new system that bypasses all the constitutional rights for domestic citizens?
Setting that aside, this is the exact purpose of speed limits, not one-way streets. One-way streets do not prevent pedestrians from popping out behind "bends, turns, hills/humps, or other obstructions", or children, or debris, or potholes, or stopped or malfunctioning cars, or construction, or sudden road ends...
Edit: If you can't stop in time for a bicycle, you can't stop in time for anything, and you need to drive slower. Unfortunately, many American drivers seem to believe that they own the road, and if dumb children run out onto the road and get flattened, that's their own fault for breaking the law.