Yes, where would we be without the rules-based international order? Perhaps we would be watching videos every day of children blown apart by weapons of war.
I really hope guide-level docs are on the roadmap for Axum. The current situation of "here are some (third-party) blog posts and YouTube videos" is not greatly encouraging. For reference:
Yeah, I think this may be a good option when actively working on a project. Sadly at the moment, it's mostly a case of "I just need to make a couple of bug fixes in this old project, why is my editor shouting at me?"
It's only a personal side project and I have a good handle on the untyped modules in question, so in the end I suppressed most of the errors with `# type:ignore` and friends.
I'd reconsider that if I was doing more than the odd bug fix on the project. I still like Python, and started using type hints early, but there's enough added friction to make me question using them in the future.
Worst of both worlds is right. I came back to a Python project with a couple of critical but untyped dependencies recently after writing mostly Rust, and to clear up a large number of these (particularly “type is partially unknown”) I had the choice between lots of purely type-checking ceremony (`typing.cast`) or going without.
Comparing Jagan and Burnham to (respectively) Trotsky and Stalin is extremely strange. Jagan was perceived as a threat to British interests in Guyana, Burnham was deemed acceptable if unreliable.
Britain sent warships and 700 troops to oust Jagan in 1953, suspending the constitution, and later worked (with the US) to ensure Jagan could not reach the top job again. To be clear, Jagan’s PPP had won 75% of the seats in a democratic election.
> [This post] (and many others) have done a much better job than I could, explaining from a reader’s perspective why Fandom is bad place to host a wiki,
The linked post (at j3s.sh) appears blank to me, so if others have the same problem here’s an archive link: https://archive.ph/kwt1b
It may not even be that nefarious — perhaps they did the hack “for the lulz” then had pangs of conscience afterward and scrabbled around for a (false) excuse.
In any case, the IA was in some cases the only public host of important documents about Palestinian history, which are currently inaccessible, to say nothing about how important the Wayback Machine has been over the past year.
The note currently displayed to my account disputes the claims made in the linked tweet (that the Internet Archive is run by the US government(???)), not the supposed motivation of the attackers.
That said, this just seems to me like the attackers are trying to come up with some justification after the fact to explain why they would go after something as universally beloved as the Internet Archive. Actual pro-Palestine activists are not happy, eg (strong language): https://x.com/Aldanmarki/status/1844155616199413969
This is only true of typical UK-style roundabouts which are designed for motor vehicle throughput.
It’s extremely common in the Netherlands to replace crossroads and T-junctions with roundabouts to improve safety, but Dutch urban roundabouts are designed with safety as the main priority. This is achieved through single lanes, sharp entries, limiting forward visibility, and pedestrian and cyclist priority (via what are effective zebras).
Xtensa is from Tensilica (now Cadence) but, as sibling comments point out, new Espressif designs use RISC-V. There's a bit of an overlap point: the ESP32-S2 and ESP32-S3 are recent designs that use Xtensa, and they were released at roughly the same time as the ESP32-C3 (I believe the first Espressif RISC-V part).
The S2 & S3 are more powerful and capable than the currently available Espressif RISC-V microcontrollers. Perhaps it's best to think of them marking the summit or climax of Espressif's Xtensa parts. But the future clearly lies with RISC-V.
The Xtensa support in LLVM/Clang appears to have resulted (at least in part) from Espressif's active support for Rust on their microcontrollers. The recent Rust 1.81 release merged support for the ESP32, ESP32-S2 and ESP32-S3 into upstream rustc. It's great to see a microcontroller vendor directly support the use of Rust on its parts, and not just its "new" parts.
Edit: To be clear, the ESP-IDF framework is a huge C project, so Espressif working on LLVM support for Xtensa is clearly _not just_ for Rust. And "easy mode" Rust-on-Espressif (std support!) relies on the ESP-IDF so merging their patches into LLVM is beneficial all-round.
For those curious about this history, you can watch John Pilger’s 2004 documentary Stealing a Nation for free on his website: https://johnpilger.com/stealing-a-nation/