fffggg

Terminal environment? You're gauging the performance of the kernel by interactive typing performance?

I don't know where to start.

That's just to become an acquiring bank, to save on exchange fees.

Ultimately VISA determines who gets to participate in the VISA credit exchange network and will fine acquiring banks who participate in things like this. No one can force their way in and avoid responsibility -- period.

One obvious example would be if you had hired the interviewee in question. If so, it would be awfully difficult to demonstrate discrimination against them!

Don't get me wrong, it is a very bad idea to ask these questions. But it is not illegal, strictly speaking.

Can you cite the relevant Texas statute? I don't believe you are correct.

It is very common for confused employers to claim it is illegal, but as eli described this is an oversimplification and is not actually true.

Here's one for you: City real estate dips in price. Suburb real estate rises, especially at the fringe of the suburbs. A self-driving car with a LTE wireless hotspot would make a previously absurd commute manageable.

Heck, you could sleep during your drive in to work.

This question is equally applicable to all data sources -- not just filesystems. The question applies to sockets, IPC, databases, everything.

That's incorrect. As was already pointed out this issue has nothing to do with reading data from the filesystem or manipulating variables internal to the program and everything to do with poor choices made when using printf.

In other words, those files aren't causing the QEMU program internals to re-interpolate one variable as two values. They're merely messing up a poorly written data exchange format.

Other languages such as I listed above simply do not have the same issue. The C program did not mis-interpret a variable as two separate values because it contained spaces. That is the nature of the danger with shell -- any reference to a variable in Bourne involves string interpolation and tokenization. This simply does not happen in C.

This rant misplaces its frustration. This is not a problem with unix filesystems, this is a problem with Bourne Shell scripts, and with UNIX argument parsing semantics.

Bourne shell is notorious for its problematic quoting, both of filesystem data and of any data from any other source. Every example in which he described a problem with a filename parameter could just as well be a problem with a non-filename parameter. The correct solution is to not program complicated scripts in Bourne Shell, and instead use a language which does not implement variable access by interpolating strings and then re-tokenizing and re-evaluating them. Examples of satisfactory languages include Perl, Python, Ruby.

Regarding UNIX arguments and the dash, it is an unfortunate aspect to the flag argc/argv/envp calling convention for unix programs. Some other operating systems provide more structure in their calling convention, explicitly separating different types of parameters from one another. This is both a strength and a weakness, as it results in a uniform yet inflexible systems interface. One of the greatest strengths of UNIX is that its calling convention is so flexible. The semantics used today are quite different from the semantics used 40 years ago -- yet execve() remains unchanged. I would encourage anyone interested to do a bit of historical digging here, and see how those more ridged system APIs fared over time.

Anyway, the solution to his initial question of using `ls` is the -- argument, which signifies argument parsing should be disabled for the remainder of argv: ls -- *

The correct answer to his dotfile/glob question is: "glob() and the Bourne shell do not have the semantics you're after. Do not use them, use readdir()."

The correct answer to his find -print question is: Yes, print's use of whitespace was a mistake, and it is a mistake repeated continually throughout the land of shell scripting and accompanying standard UNIX utilities. As he notes, it is why print0 was introduced. Making print0 standard is far easier than reworking filesystem semantics (and, reworking userland in this manner is a more complete solution as it addresses data integrity issues from non-filesystem inputs as well). If you want reliable, correct programs, do not write them in shell.

Regarding the expense of clinical trials, it's important to note that the scientific results of a clinical trial are not protected by either patent or copyright. Pure research data cannot be restricted under any form of IP. Factual data without a creative element is explicitly exempted from both the patent and copyright system.

A published paper on the results of a trial may fall under copyright, but the factual observations and conclusions cannot be.

The "clinical trials are expensive" argument is incredibly disingenuous.

It's much, much worse than what you describe. They are seizing domains based on the preference of a private entity. There is no allegation of criminal infringement against dajaz1.com -- not even a little bit.

This is not an issue of harassing minor offenders, this is an issue of harassing those who have not offended in the slightest. Who are guilty of nothing more than saying something (in the form of links) which the RIAA does not wish to hear.

Not to mention you can write down the seed itself and simply type it into another phone.

"I just know that is a stolen car"

Which is why criminals do not charge half of its used value -- they charge 100% of the used value just like everyone else.

You cannot tell a stolen bike on craigslist apart from a non-stolen bike based on the price alone.

The problem of stolen cars is addressed through licensing and registration. Not to mention, bicycles do not have a reliable and standardized VIN system like cars do. The fact is, the hassle of creating and enforcing such a system probably outweighs the positive aspects of preventing bike crime.

Absolutely.

When a civil contract is broken the appropriate response is a trial in a court of law. Businesses are quite familiar with the debt collection process. A judge and possibly a jury are needed to resolve these types of disputes fairly.

Under no circumstances should a merchant be permitted to forcefully take funds from another person, outside the purview of the law.

Not designing for an appropriately sized earthquake is itself an engineering failure.

FDIC? In Brazil?