rwj

The article is a good overview, but I don't think saying that Gebru was fired is accurate. This fact is commonly repeated, but I believe she resigned.

Yes, take their lessons with a grain of salt, but they have a ton of experience, and shouldn't be dismissed out of hand either.

Just one data point, but doesn't Google advocate for living at head? Long-lived software can't be static.

I doubt that everyone is being as deligent as you. I suspect leaving security updates to upstream is not a recipe for secure distributions.

For the record, I see both sides as having legitimate concerns.

You should give Pinker a closer read. He does not say that progress is uniform in space or time. He certainly acknowledges there can be set backs. This is exactly why he emphases the importance of reason - to avoid the setbacks that would come from poor decisions.

I'm sure that many could read it, but reading it and understand are not the same thing. Understanding takes time, often a lot of time. And this is where the simplified bit comes back.

Discussions on social media rarely indicate much effort at nuance...

Your comment about char* aliasing everything is for C, not LLVM.

It's true that gold and silver have industrial uses, but you don't see people hoarding bars of chromium as a store if value. I doubt that gold's price is entirely due to industrial demand...

Peer review for academic papers is typically anonymous. She would have been familiar with the process. In the end, the editor (in this case the manager) takes responsibility for the decision.

I've found it pretty easy debug GitLab CI issues. You know the docker image, so you can create the environment locally. You then need to concat the scripts together.

I will need to check out aerc.

I've only submitted one patch, but there are enough differences from regular email to create quite a barrier.

Don't know the author well enough to know if this is a joke. However, saying something is "easy to see" that has not been accepted for a century must be satire...

In the second paragraph, there is a faulty assumption that all real numbers are computable.

There has been some talk of support for renters. I'm fairly convinced that this is a bad idea, as any increased will go to the property owners. Bring rental prices down means increasing stock, but I'm not sure anyone has a plan for that.

This is a really tricky thing to get right. If you put too many controls in place, people route around and you lose control. If you place too few in place, you lose control. If you try to make the rules flexible, people don't understand the rules, and you lose control.

The syntax is definitely Go :)

The approach is a hybrid. The declarative approach with reconcilation (tree diffing) comes from React. The automatic layout with constraints does come from Flutter.

That's true, but I put that in the bucket of "C++ needs a package manager so that we can use dependencies more complicated than a single header file".

May I ask what's wrong with using xxd? I don't have an opinion about C, but C++ is already pretty complicated, and adding features to the language when there are already well-known solutions doesn't seem wise.

(For the record, I'm aware that there are size limitation when using xxd, but there are also other solutions).

I also did quite a bit of benchmarking, and never saw any quadratic behaviour [0]. However, there is a floor for RSS and and elapsed time, but you would need to test assets less than ~1MB to see it. For assets over a limited range, the graph might look quadratic, but if you cover a large enough range you will see there are two regimes of behaviour.

[0]: http://stonecode.ca/posts/binc_benchmarks/

It's silly, but when I was moving some projects to SourceHut, this was one of the first things I noticed was missing.

There are other ways in which the incentives are misaligned. Granting agencies that prefer to fund researchers who nearly always "succeed" in proving their hypothesis will find that research proposals are low-risk and low-information. At in at least one sense, the ideal experiment is one with a 50/50 chance of failing.

Disconfirmation is also important.

And how was that measured?

One of the lessons from the falls of authoritarian governments was how big a gap there was between public expressions of support and peoples' true feelings.

I'm not sure the implementation details can be ignored so easily. With certain exception, the Go authors do not like implicit conversions and the associated runtime costs.

I look at the discussion of covariance/contravariance and memory layout as two sides of the same coin.

What's rational for the individual is not always well aligned with what's rational for the society.

See also false dichotomy.

The sample size is so small, that the results are nearly meaningless.

Bring on the 1/8 scale model!

This is another way that Go's approach works well. In practice, you will see library code check for common image formats, and then dispatch to optimized code. The advantage here being that optimization is a library concern. Callers still maintain flexibility.

I agree with your examples, but that code is pretty trivial. There is a point where inference can be over used, and that can cause readability issues. The OP ended with a call for empirical research.

Are you asking in the short term or the long term?

Nothing says human safety like a technology that can make a species extinct. The motivations for elimination mosquitoes is noble, but I'm not comfortable about where this technology will go afterwards.