DevelopingElk

As with many inventions, the Wright brothers weren't the first inventors of the airplane but the last ones. Everyone else built off them.

There are multiple factors. There is vehicle related degradation and also weather related. In areas with a freeze that cycle road maintenance has a flat cost component. Someone needs to pay for roads.

There are plenty of longer bridges, but those are multi-span bridges. The Straits of Messina are extremely deep and the area is tectonicly active. So it isn't feasible to build supports in the middle of the strait. If it were feasible then it would have been done a long time ago.

The design calls for the longest single span suspension bridge in the world. By a lot. It also needs to hold up to powerful storms.

The other alternative would be a pontoon bridge. The one in Seattle crossing lake Washington is 2km long, so that would work (https://en.wikipedia.org/wiki/Lacey_V._Murrow_Memorial_Bridg...). However, The Straits of Messina are one of the most active shipping lanes and the maritime traffic is more valuable than the road traffic. The pontoon bridge works in Seattle because the main port is in the Puget Sound and there isn't any major shipping in Lake Washington.

Free Electron Lasers have potential to generate more tunable radiation with higher luminosity. Despite this they aren't a drop in replacement for the current EUV light sources. A free electron laser is 200 meters long, so a single laser would feed multiple EUV machines for it to be economical. This technology is very promising but it has been under development for a while. Does anyone know what the current difficulties are?

It can be done, but airplane GPS receivers aren't jamming resistant. This is expected to change in the next decades.

Across an application the penalty is normally 1-5%. Most business code benefits from the increased safety. Parsers are an exception, but the large attack surface sometimes makes it a good idea there too.

The article needs absolute efficiency figures to know if this is a good idea. I also wonder if better conversation electronics could make a difference. I'm guessing there is some tradeoff between cost of conversion and volume/weight/efficiency.

The other question is how this fits in with regenerative braking. Is this power conversion circuit dual purpose?

The movement has been towards making batteries structurally integral to the vehicle to save weight in the frame.

Yes. The break even is at around 15,000 to 20,000 miles driven for replacing an ICE. This obviously varies depending on electricity source.

Interesting. I think single person RFCs are like most other forms of publication in that there is a long tail of unused ones and a few that take off. But you miss all the shots you don't take.

Context: I am a software engineer working at AWS in Commerce Platform - International Expansion. All opinions here are my own. Also, I am just an fairly new engineer, not a lawyer.

Countries in Europe are covered by the EMEA SARL (Except for Turkey) https://aws.amazon.com/legal/aws-emea-countries/. When we generate invoices we look at your contact and billing addresses, and since they are EU we will have them come from the EMEA SARL. We may also have it come from a branch of the EMEA SARL if it exists in your country (for example Greece). If your business has a contract with AWS then the contract can override this behavior. AWS applies taxes under some circumstances, see https://aws.amazon.com/legal/aws-emea/.

With regards to tariffs, my understanding is that its a big maybe. EMEA SARL is a fully owned subsidiary of Amazon Web Service Inc. so for tariff purposes it may be treated as AWS Inc. Alternatively, the tariffs could be structured to only apply to US usage. Its the EU's choice. If the EU wants them apply to all AWS/GCP usage then they will.

I like how this change was done with no excess drama and that Christoph is continuing to stay involved with Linux. This could be a break for the controversy to cool down and the developers to get back to developing.

It should be fairly easy to upgrade compatible APIs server side from reading the AWS docs. All that needs doing is to accept and ignore the new checksum header. I also expect that taking advantage of the checksum would be reasonable, a CRC32 isn't that hard.

https://aws.amazon.com/blogs/aws/introducing-default-data-in...

Can you please point to where on the article documentation is being paywalled? I'm not seeing it. If Amazon removed it can you point to an archive link?

Yes, this article is only talking about asymmetric cryptography. Symmetric cryptography and hashes are based on NP complete problems.This is only when generalized appropriately, most individual hashes/ciphers are fixed so there isn't really a way to talk about their complexity. The broader class of block cipher like problems is NP complete, and very hard.

No, it has to do with the coupon collectors problem. The key idea behind this algorithm is to do more looking for an empty spot up front.

I might be misreading their algorithm, but from my look at the paper the key improvement is a non-uniform strategy where they divide the array into buckets and focus on different buckets as they fill the table. This increases the average number of locations to be probed even when the table is emptier. They still place the item in the first empty slot they see with this strategy.

The "skipping slots" has to do with jumping ahead in the hash sequence.

My understanding is that yes, in some circumstances this can help inhibit crack formation.

The place where it won't has to do with settlement, where the soil beneath the rose sinks unevenly. This is a major initiator of pothole formation. Road construction is tightly cost constrained, so this will come down to exact price.

I'm also looking forward to part 3.

A good counterpoint to some of the concerns in the series is https://cacr.uwaterloo.ca/techreports/2015/cacr2015-01.pdf. This article shows "several examples of attempts to avoid random oracles that have led to protocols that have security weaknesses".

Of course, that article is only focused on more classical constructions and not on the newer SNARKS/SNARG/STARK and other constructions in the zero knowledge zoo. So there isn't really a disagreement, but we probably shouldn't ditch random oracle based constructs in use today.

The 2.2% is not a "flipping a coin" style probability. It is a "we lack complete knowledge" style probability. So the odds that it drops to 0 with better observations are 100%-2.2% = 97.8%, which is pretty likely. These odds are the odds systematically incorporating all knowledge.

I think the line about changing probabilities is there because us humans are bad at understanding probability.

The reason linked lists are used is for large enough allocations, there is no overhead. You use the space the application isn't using. In addition, if all allocations are the same size it is O(1), you just look at the head of the list.

More sophisticated strategies bucket allocations by size, this has fixed overhead. You can also use balanced trees for more memory efficiency, but this is slower.

For small allocations (8 bytes) that are too small to contain pointers allocators will allocate a block and use bitsets.

No, officials have closed part of the park but the rest of the island is safe.

There was a narrow window where CPUs were big enough to have circuitry for JVM fast bytecode execution, but too small for strong JIT compilation. ARM deprecated Jazelle as soon as that window passed.

There are different types of standards. Car design teams are big organizations; internal standards can help reduce the development effort. Tesla needs to coordinate with their suppliers, so sharing this helps even if it isn't used by other companies.

I think we should give Tesla the benefit of the doubt for now. Harmful use of patents could cause issues, but this has potential. We will simply see if other companies are interested, and if they are it can go from internal standard to de facto standard to formalized standard.

"Hypersonic" is a misnomer, most long range rockets hit hypersonic speeds. "Hypersonic" refers to steerable hypersonic glide vehicles that can turn to make them harder to intercept. There is no evidence yet that any of them were used in this attack.

I think it's fine. It's analogous to starting induction from 0 over the natural numbers.

It does feel a bit tricky though because there are two nested foralls instead of just one in standard induction. I think to derive it from standard induction you need to perform induction over sets of statements, which takes more power than first order logic. This additional power is generally accepted in math courses. It isn't necessary though, you can prove the irrationality of sqrt 2 using standard induction.

The article discussed how additional techniques can be made rigorous in the opening paragraph. I agree that the author didn't fully justify the assumptions in the proof system used, instead bringing this well ordered induction as an axiom. This is an article, I think a full aximization would have taken too long.

I went to CMU and was in AEPI fraternity with Brandon Wu. Brandon Wu is exceptional when it comes to functional programming. He was head TA of 15150 for a year, I have 100% confidence in him.

He took a break from TAing for some time, and when he returned he decided to have some fun with his application. He wrote a transpiler from a C like syntax to SML the day before his interview, and used it to joke that they should transition to teaching functional programming in C.