I’ve done professional work on an old Unix system where the full build was more than 2 hours, and an incremental stop-rebuild-restart cycle was 20 minutes.
You get to where you really stare at your edits for a while before you hit build.
I’ve done professional work on an old Unix system where the full build was more than 2 hours, and an incremental stop-rebuild-restart cycle was 20 minutes.
You get to where you really stare at your edits for a while before you hit build.
That’s an implementation-defined behaviour.
I don’t know about your definition of “living wage,” but In-n-Out has a long-standing reputation for paying decent and above-market wages, both in 2016 and today.
I would guess that most of the current price premium over inflation is attributable to the current record high beef prices owing to a record low North American cattle herd.


This doesn’t happen “on a distro” because all of the different software functions are at different safety criticalities. The autopilot is (usually) level B, the air data system that delivers altitude and airspeed is level A, the navigation computer is level C (because pilots can still navigate without the aid of the computer). And so on.
At level C, the standard is statement coverage with unit tests. At level B, it’s decision coverage, covering every branch. And at level A, it’s modified condition / decision coverage, which is a lot more complex and expensive to write.
If you mix code for stuff at different levels, you have to develop the whole package to the highest level. Unless you can prove that the lower level code can’t interfere with the higher level code.
The easiest way to prove that is to put the different levels into different computers, so they’re only talking to each other on some digital bus interface. That’s called “hardware partitioning”. There’s also “software partitioning”, but it requires an operating system or supervisor layer to provide the guarantees, and that operating system has to be developed to the highest safety level that it handles.
Final result: you still see a lot of discrete computer boxes on airplanes. Various vendors have developed safety-critical OSes for main avionics computers, but they’re closed-source, and usually not based on Linux at all.


Allegedly, Outlook doesn’t handle intermittent broken connectivity very well when you’re trying to configure it initially. Such as when your gateway is handing off between TDRS and the fricken Deep Space Network.


IMAX film is twice as wide as standard film. 70 mm instead of 35 mm. The IMAX film platters are physically ginormous. All that extra film gives you a bunch of extra resolution compared to regular film.
The first catch is that “IMAX standard” may not be real IMAX. I don’t know exactly what that means. Perhaps it could even be digital projection that aims to be comparable to IMAX in some ways?
Second catch is that a lot of films that are shown in IMAX theaters were not actually shot on IMAX originally. If a film was shot on 35mm, say, and then printed onto IMAX, you don’t get all of the resolution benefits, and you may also get letter boxes or pan-and-scan because the aspect ratio isn’t the same. IMAX cameras are massively more expensive and logistically difficult than regular film cameras.


Usually in these stories, Batman or whoever leaves behind enough evidence to support a successful prosecution, along with the tied-up bad guy.
The vigilante broke the law to gain evidence, so all the evidence the vigilante obtained would be thrown out,
That’s actually an interesting situation. The fourth and fifth amendments put restrictions on the government, not private vigilantes. So if the cops just happen to find evidence in plain view, there won’t be a direct constitutional reason to suppress it.
Now if the local prosecutor has a pattern or practice of deliberately turning a blind eye to the unlicensed private investigators that routinely supply them with illegally obtained information, there’s probably a claim there. But it’s a lot more complicated to make that case than a straight-up 4th amendment case.
For me 1.0 only means that I’ve delivered the software to a paying customer.
They don’t like the U.S. either, as they believe that they are an imperialist power that wants to take advantage of the Middle East. That is one reason that the United States deems Iran an enemy.
In 1953, the CIA and MI6 effectively ended representative democracy in Iran when they backed a coup d’etat that deposed Iranian prime minister Mohammed Mosadegh. Mosadegh had tried to audit the books of the Anglo-Iranian Oil Company (which later became a division of BP).
The 1953 coup resulted in the Shah of Iran, Reza Pahlavi, ruling autocratically and with heavy support from the United States. This status continued until 1979, when an Islamist revolution deposed the Shah and installed the Islamist government led by a clerical Supreme Leader that exists today.
In 2013, the CIA released declassified documents that showed that the CIA planned and carried out the 1953 coup using all kinds of abhorrent tactics, including bribery of public officials, astroturfed paid protesters, and false flag operations.
So hopefully that explains why the US is “the great Satan” to Iran, and why Iran keeps spouting “death to USA” rhetoric.


It would have been really helpful if Steve Patterson could have cited a case number or a caption or something.
That painting should be old enough to be in the public domain. (Although photographs thereof get their own copyright terms.)


The credit card companies have always tried to prevent merchants from doing this by inserting language prohibiting either credit card surcharges or cash discounts into the contract agreements with the merchants. Obviously, credit card companies want to make it easy and convenient for consumers to use their credit cards.
I can’t immediately find it, but at some point I think 10-15 years ago, some merchants sued the credit card companies over this, and they won a court ruling that said that the clauses forbidding cash discounts and surcharging are unenforceable. As a result, merchants are now free to do it, but there are various rules. And some state legislatures have started to get involved with regulating things.
Not even. ed is The Standard Editor.


Some of those bags are still on the moon today, in the lockers on the descent stages where they were left.
Windows does, in fact, have signals. They’re just not all the same as Unix signals, and the behavior is different. Here’s a write-up.
You’re correct there is no “please terminate but you don’t have to” signal in Windows. Windowless processes sometimes make up their own nonstandard events to implement the functionality. As you mentioned, windowed processes have WM_CLOSE.
Memory access violations (akin to SIGSEGV), and other system exceptions can be handled through Structured Exception Handling.
It was also common to have a single step mode, where the CPU advances one cycle per switch press. Very useful for debugging.
And you could frequently read out the contents of registers directly on rows of lights. This led to the trope of the blinky light computer in Star Trek (original series) and elsewhere. Because the lights would flash in various patterns when the computer was running, as the register contents changed. But in the single step mode you could interpret the values.


Nvidia has entered the chat.
Rust has many container-like objects that may or may contain a value, like Box. Most of these have an unwrap() method that either obtains the inner value or panics the whole application.


The license holder is attaching additional terms and conditions that are incompatible with publicly disclosing the driver source code.
Without the monocoque, I doubt it can pass modern crash safety tests. Nor is there any safe place to install air bags.