colonwqbang

When you think about it, 24 years is not such a long time for a machine to keep doing what it's supposed to be doing. It says something about our profession that we find a 24-year service life surprising.

There are airliners that have been in service for over 50 years.

The article then ends by displaying an ad for Apple products.

Could you clue us in? What is mathematics actually about?

If you subtract the "meaningless phrase", the title of the book is just "Music Theory". Do this for every book written about music, art, mathematics and you'll just have a lot of books with identical and quite dull titles.

It's funny, some people commenting here seem to be a bit lost.

It's also obvious from the article that his home was indeed searched.

The idea that the government would not obtain a warrant if they suspect you of stealing millions...

I don't think you know what you are talking about.

Another way to look at it: Microsoft APIs have fallen from grace. Even their own devs don't dogfood anymore. They download something that Facebook made instead and reimplement the Holy Start Menu using that.

I didn't say that json can represent all rational numbers. I said that all json numbers have an obvious interpretation as a rational number.

So far you haven't really shown an example of a json number which has an ambiguous or ill defined interpretation.

Maybe you mean that json numbers may not fit into 32 bit integers or double floats. That's certainly true but I don't see it as a deficiency in the standard. There is no limit on the size of strings in json, so why have a limit on numbers?

How do you feel numbers are ill defined in json? The syntactical definition is clear and seems to yield a unique and obvious interpretation of json numbers as mathematical rational numbers.

A given programming language may not have a built in representation for rational numbers in general. That isn't the fault of json.

...The code signing requirement?

Has nothing to do with go. You added a dependency which is not portable. It is well known that systemd project only targets Linux.

Vendorise systemd and compile only the journal parts, if they are portable and can be isolated from the rest. Otherwise just shell out to journalctl.

Your post could be (uncharitably) paraphrased as: "once you have written correct C++ code, the drawbacks of C++ are not relevant". That is true, and the same is true of C. But it's not really a counterargument to Rust. It doesn't much help those us who have to deliver that correct code in the first place.

True, but locks are not only needed inside IRQ handler routines.

I wrote "multithreaded" but I really meant "multicore". If two cores are contending for a lock I don't see how irq protection help. As long as there is only one core, I agree.