Current US tax law requires much information the IRS doesn't have, including taxpayer marital status (are you living in the same household with your spouse?), number and age of dependents (are they in school?), itemized deductions, etc. The IRS does attempt to prepare returns for non-filers, they have very low accuracy. Countries that prepare income tax returns for the taxpayer have tax laws designed to be compatible with that mode of filing.

T'so's coment is more legitimate than many here admit. Linus's rules for changes in kernel interfaces require that if T'so changes an interface that he is responsible for patching any other places in the kernel that use that interface. If there are Rust funtions affected, and he doesn't know Rust, then that effectively precludes him from making (or approving) any change to the interfaces he is responsible for. The Rust folk are effectilvely asking for control over changes to the kernel interfaces. It is a pretty big ask, and something Linus needs to address directly.

A truely great and humorous take on this topic is at https://idlewords.com/talks/we...

I believe it (true calling number) is visible to owners of 800 type numbers, but not to regular customers of the phone system.

About 10% of tax returns itemize.

Unless you tell it, the IRS doesn't know your marital status or number and ages of your dependents, all of which is important to calculate your tax liability. That said, the IRS could do the calculations for you if you submit the data. Years ago they would do that for returns with the earned income credit.

It appears they use "asked" price to value the NFTs. If they used the "bid" price, the numbers would be different.

The dollar and the Euro do have a commitment from the respective governments to maintain their value. This is far from ironclad, but it a lot more than bitcoin has.

I have been distributing static binaries for an application for many years now - it always works fine. I don't understand why it is discouraged.

Here in Cambridge Massachusetts we have had electric busses powered by overhead lines since the 1920s. There aren't really any problems. Buses can pass double parked cars since the power polls swivel and are about 25 feet long. The busses are standard busses with electric traction and come from General Motors. For some reason there has never been a big fuss about them.

I just checked amazon.com for "smr drive" and found several drives labeled SMR but for much higher prices than regular or unlabeled SMR drives. Very odd marketing.

Several people have suggested that the results are due to hospitals with poor security also having slow response times. However the design of the study takes this into account using the difference-in-differences method. It looks at the change in response time before and after the intrusion and compares it to the change in response time for other hospitals. A poorly run hospital may be slow, but the study shows that it gets slower after an intrusion compared to other hospitals.

I think most compilers will move the bounds check out of the loop, at least if some level of optimization is requested. However the main problem for C-style languages isn't arrays but pointers. It seems to be harder for the compiler to check pointer references.

The Wehe web page is not clear on how significant the throttling is. For example, it seems the 22% of Sprint Skype calls are throttled at .5mbs, but it isn't clear that the unthrottled calls are much faster - they don't say anything about the unthrottled speed.

The response from the industry association is a little bit odd. They claim both that no throttling is going on, and that it is a good thing. I suppose it isn't supposed to be read carefully, so they provide all possible arguments, even at the risk of self-contradiction.

Also, I don't understand why only mobile is considered. We can no longer watch Netflix in the evening, because Comcast/Xfinity no longer provides enough bandwidth for Netflix to function. Why no test for wired connections?

Just Google "openbsd httpd".