loglog

The bots can also write Rust instead of C++, doing away with the arcane nonsense accumulated by that legacy language. SCNR.

Bureaucracy gives you leverage against slop. Review seriously, but limit the time that you spend. This will stall the slop. When the culprit complains, tell your boss "I spend X hours per week on reviews. If you need more throughput, the PRs quality needs to improve."

Writing and reading design documentation can be slower than pair programming. On the other hand, info about code design also belongs into inline documentation or commit messages (in this order of preference), so the effort might not be wasted.

It's not just documentation. Everything that makes programming easier is now suddenly valued, because wasting tokens is obviously worse than wasting your employees' time.

This claim is plain malicious. Of course falling asset prices would be excellent for the median person, since they would be less extremely priced out of everywhere. This is one of the central benefits of a wealth tax.

For that kind of implementation, ...

This is the key point, what is the meaning of "zero knowledge" here? It seems that you need to know something about the implementation, even if it is not the full implementation. Compare this to a zero knowledge proof that you have, say, a factorization gadget, which works by you running the gadget on adversarial input, thus convincing the adversary that you can factor any of their integers. That discloses no implementation details of your factorization gadget, which can be an efficient classical algorithm, a quantum computer, or a phone line to God.

The list of tools that Pythonheads present as a definite solution to their problems changes every year, yet the results are still far behind Rust/Scala/Kotlin/C#.

Surpassing DB's punctuality is the first large-scale example of the "Overtaking without catching up" East German slogan coming true.

The "fix everything" button is abolishing zoning laws, and its aggregate cost is negative. Aggregate cost is not the issue preventing problems from being solved.

on top of a well designed language constructed over past language design experience

While I believe that Chris Lattner is a great compiler designer, his language design record has been less stellar. Swift bidirectional type inference for instance feels like it was implemented because they had a compiler algorithm that they wanted to use, rather than a genuine need, and is just a completely avoidable problem. Trying to make a HPC language that is also Python compatible was doomed from the start. Hopefully the damage from going into this direction will remain limited.

Mojo is NOT Python compatible (although they initially wanted it to be). So they got all downsides without the upsides.

How is it possible to provide a zero knowledge proof that their circuit works for large problem instances if there is no efficient way to run or simulate the circuit with the required instance size?

"I believe that almost anything that has been formalised today in any system could have been formalised in AUTOMATH. Its main drawbacks were its notation, which really was horrible, and its complete lack of automation. Proofs were long and unreadable." That's like saying that anything that could be programmed today in your modern language of choice could have been programmed 50 years ago in assembly. Technically yes, economically no.

There are videos on the internet of drones being shot down with an assault rifle out of a 50 year old training plane, 1914 style.

A Bundeswehr worth of equipment is so little nowadays that Bundeswehr itself lost several Bundeswehrs worth of equipment while being at peace for the last few decades.

Americans are very comfortable with eminent domain, as long as it is applied to brown people.

This makes sense, because parking a car does take a similar amount of space as a studio apartment.

1. Java is mentioned in their comparison table. They just don't use it much. 2. There is really no reason to include Java in the search for your preferred language, since Kotlin is strictly better along every relevant axis.

That's a very low bar. Any language feels consistent compared to C++.

On a national scale, keeping a stock of transformers is peanuts. For this to be viable, they only need to be interchangeable, not identical.

I recommend to block the Linkedin feed with uBlock.

Traveling? Lake home? I am glad to go to work just to not listen to my wife how we are so poor and cannot have nice things.

how many people here have actually worked at an early stage startup in a lead role

Obviously very few, because these roles are impossible to get into. What else did you expect?

Operator of the LinkedIn Website:

LinkedIn Ireland Unlimited Company Wilton Place, Dublin 2, Ireland

php is the only popular language that regularly removes insane legacy cruft (to be fair, they have more insane cruft than almost any other language to begin with).

Real men know that infinite sets are just a tool for proving statements in Peano arithmetic, and complex numbers must be endowed with the standard metric structure, as God intended, since otherwise we cannot use them to approximate IEEE 754 floats.

Your link is _not_ about a country that _actually_ imposed a sugar tax.

Counting warnings is a poor practice, because you don't see where warnings exist or are added or removed while reading or writing code. Suppression annotations in code next to where the problem occurs are more explicit, and the progress is easy to measure with e.g. git log -S. The main difficulty is automating adding these annotations. For at least one static analysis systems, there is an off the shelf solution: https://github.com/palantir/suppressible-error-prone

That's right, much of the market is negative sum.

Wealth tax is the best type of tax, because it incentivizes productive activities against speculation. It should be levied on a continuous basis rather than on transaction basis though, which is just basic numerical analysis.