Frankly where's the evidence of this? My country of Australia has no fear of being attacked, yet we haven't launched an endeavor of conquest of South East Asia.'
Real life doesn't break down into simple narratives. The facts in the Middle East are that post-October 7 Israel aggressively bombarded Gaza at a scale and intensity where it did not previously, and a substantial chunk of the population supported that. In particular, it felt compelled to significantly escalate kinetic action against Hamas and Iran where it had not previously.
Post 9/11 the US aggressively invaded 2 sovereign nations it otherwise had little interest in and occupied them for 20 years.
These are all scales and levels of military action which were precipitated by successful attacks that killed civilians. If 9/11 hijackers had been stopped in the planning stage, does the US still invade Afgahnistan? Probably not - it wasn't on anyone's cards. Iraq maybe but the conditions were set by that strike hitting the way it did.
> My country of Australia has no fear of being attacked
You should watch some Sky News Australia; at least once a week there is a special report on how to prepare for China's invasion - which is never more than two weeks away.
Otherwise Windows could make WSL (1) faster than Linux, but they can’t because they don’t have the similar enough underlying operating system paradigms.
I could give examples, but I think just comparing native python performance on both platforms is the easiest case I can make without going into details.
WSL 1 was faster and better than WSL 2, but they abandoned it for its technical complexity and switched to containers / virtual machines, which create a slew of Other Problems.
As far as you provide the bindings, you can compile it with an application built in any language. There are in the repo a few examples with C programs.
GitHub - Historically, GitHub reports uptime around 99.95% or higher, which translates to roughly 20–25 minutes of downtime per month. They have a large infrastructure and redundancy, so outages are rare but can happen during major incidents.
GitLab - GitLab also targets 99.95% uptime for its SaaS offering (GitLab.com). However, GitLab has had slightly more frequent service disruptions compared to GitHub in the past, especially during scaling events or major upgrades. For self-hosted GitLab instances, uptime depends heavily on your own infrastructure.
This is exactly what happens when you invest billions and hire the best industry specialists for decades. M-series processors did not magically appear out of nowhere. Apple perfected them for years in iPhones, but people didn't have the ability to compare since Apple doesn't share their processors with anyone.
This, 100%. I forget the specific numbers but regardless, the kinetic energy of a thing with that much mass, even moving at a very slow speed, is off the charts. Designing a bridge or protections for a bridge to survive that would at a minimum be cost prohibitive, if even possible with today’s materials and construction technologies.
> The NTSB found that the Key Bridge, which collapsed after being struck by the containership Dali on March 26, 2024, was almost 30 times above the acceptable risk threshold for critical or essential bridges, according to guidance established by the American Association of State Highway and Transportation Officials, or AASHTO.
> Over the last year, the NTSB identified 68 bridges that were designed before the AASHTO guidance was established — like the Key Bridge — that do not have a current vulnerability assessment. The recommendations are issued to bridge owners to calculate the annual frequency of collapse for their bridges using AASHTO’s Method II calculation.
Energy doesn't mean squat without a time component over which it's dissipated.
Stopping a car normally vs crashing a car. Skydiving with a parachute vs skydiving without a parachute.
For something like ship vs bridge you have to account for the crunch factor. USS Iowa going the same speed probably would've hit way harder despite having ~1/3 the tonnage.
Plan the bridge so any ship big enough to hurt it grounds before it gets that close. Don't put pilings in the channel. It's just money. But it's a lot of money so sometimes it's better to just have shipping not suck.
Alternatively, the Chunnel will almost certainly never get hit with a ship.
Yet another idea: if a ship's motors fail, have a ship ready that can push it in the right direction, in time. Probably need 2x the amount of horsepowers to make up for lost time, but it's not impossible.
Yes, that's called a tug and in plenty of harbors a vessel of this size would not be permitted to do close quarters maneuvers without the mandatory assistance of one, or in this case more likely two, tug boats of a certain minimum size relative to the size of the vessel.
I think the question is, what use is adding a CLA if the core functionality was under (A)GPL? Unless you go back and get all the OG contributors to sign over their rights, how can you relicense?
Yeah, exactly that's my point. The role of Arduino is like that of a Distro, they own the packet repository and the packet manager, and maintain a build-system and an IDE. They aren't the initial copyright holder to basically any library. The only thing they really own is the Arduino API, but this is an API not an implementation. The compiler is GCC, the board specific methods come from the hardware vendor, the C lib is newlib or comes also from the hardware vendor. The flasher software comes from a different company.
I don't really understand how what they try to achieve with these new "terms and conditions" is legally possible. (https://news.ycombinator.com/item?id=45978802) They could release new software with different licenses, but they would need to rewrite most of the ecosystem to do that. Neither MIT, nor LGPL, nor GPL nor AGPL contain any reference to "terms and conditions" of one of the copyright holders, which should be followed on top of the license.
This is probably just an acquihire.