robjwells

I believe this is just down to USB CDC, where baudrate doesn’t affect the USB transfer speed.

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:

https://github.com/tokio-rs/axum?tab=readme-ov-file#getting-...

https://github.com/tokio-rs/axum/blob/main/ECOSYSTEM.md#tuto...

> Everybody involved in this should get fired.

I don’t disagree but the events in question took place and were discovered over 30 years ago. https://www.upi.com/Archives/1992/01/04/Appeals-court-Sherif...

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.

I imagine on big projects the benefit is clearer.

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.

This is an excerpt (starting part-way through) of this article: https://www.theguardian.com/us-news/2024/nov/07/election-tru...

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.

An AP report on declassified MI5 documents about the 1953 coup: https://www.theguardian.com/world/2011/aug/26/mi5-files-coup...

A good summary of the post-'53 machinations by historian Mark Curtis: https://www.declassifieduk.org/the-sooner-we-get-these-peopl...

One of the revelations over the course of this saga was that WordPress.org != WordPress Foundation. It's under the personal control of Matt Mullenweg.

As an example of the latter, Pimoroni offer an NVMe “base” that would avoid this problem and leave the PoE header free: https://shop.pimoroni.com/products/nvme-base?variant=4121958...

Archive link for Ben Blum’s article: https://archive.ph/kn1Eb

The two scientists who conducted “The BBC Prison Study” in the early 2000s wrote about the revelations in the Zimbardo archive material here: https://www.bps.org.uk/psychologist/time-change-story

Thibault Le Texier, whose book History of a Lie brought this information to light, wrote a summary paper in the American Psychologist: https://letexier.org/IMG/pdf/LeTexier_Debunking-the-SPE_Amer...

Note this “disclaimer” in the guide:

> In recent years, development efforts in the OpenVMM project have primarily focused on OpenHCL (AKA: OpenVMM as a paravisor).

> As a result, not a lot of "polish" has gone into making the experience of running OpenVMM in traditional host contexts particularly "pleasant".

> This lack of polish manifests in several ways, including but not limited to: […]

> • No API or feature-set stability guarantees whatsoever.

https://github.com/microsoft/openvmm/blob/main/Guide/src/use...

> [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

Eric Lichtblau wrote a good book on the resettlement of Nazis in the US, beyond the usual Paperclip names, called The Nazis Next Door.

Here’s a talk he gave at UCSB on the topic in 2015: https://youtu.be/eP3srgksUqU

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).

For more information see eg: https://bicycledutch.wordpress.com/2015/10/13/explaining-the...

(Edit: fixed wrong link)

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).

Here's the ISA summary for Xtensa LX as used by the ESP32: https://www.cadence.com/content/dam/cadence-www/global/en_US...

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/

For those who prefer to read, historian Mark Curtis has published online an excerpt regarding Chagos from his 2003 book Web of Deceit: https://www.markcurtis.info/2007/02/12/the-depopulation-of-t...

Mullenweg has for a little while claimed that WP Engine does not contribute sufficiently to the open-source WordPress project, that its branding causes confusion among users, and that it ships an inferior product that reflects badly on WordPress as a whole.

WP Engine disputes this and sent Mullenweg & Automattic a cease-and-desist letter, intending to stop the disparaging comments.

In reponse, Mullenweg cut off WP Engine customers from the theme and plugin repositories hosted at WordPress.org — which until recently people had believed to be under the control of the WordPress Foundation, but is actually under the personal control of Mullenweg.

Now this lawsuit has been filed.

Edit: Characters for the unaware:

Matt Mullenweg: The "top" person in WordPress in its various forms, including the non-profit WordPress Foundation, and the for-profit company Automattic (whichs runs the for-profit WordPress.com host, among other things).

WP Engine: A separate for-profit WordPress host.

I believe in this instance he’s referring to WP Engine installations of WordPress pulling from the WP.org plugin & theme registries.

There is a longer story in which Mullenweg has claimed that WP Engine does not contribute sufficiently to the WordPress open-source project, and that the use of “WP” in their name supposedly created confusion and infringes the trademarks of the WordPress open-source project. WP Engine disputes this.

Of course the elephant in the room is that Mullenweg is the CEO of a rival for-profit WordPress host (Automattic), but has made his claims against WP Engine from his position in the open-source WordPress project.

Perhaps a board of non-Automattic WordPress project people would come to the same conclusions about WP Engine, but the current situation reeks of conflict of interest.

Ultimately the ones paying the price here are the users of WP Engine-hosted WordPress installations, who have been cut off from plug-in and theme updates with no warning.

Here's Matt Mullenweg's post on Wordpress.org announcing this: https://wordpress.org/news/2024/09/wp-engine-banned/

There is some further discussion in the HN thread on the WP Engine incident: https://news.ycombinator.com/item?id=41655578

I have no dog in this fight, but from the outside this is ludicrous behaviour.

Matt Mullenweg, the CEO of a for-profit WordPress hosting company, should not be using his position in the open-source WordPress project to attack another for-profit WordPress hosting company. Nothing could tank the reputation of the open-source WordPress project faster.

I hid the font names and still ended up with my current go-to font (JetBrains mono). I’m not sure if that’s the effect of familiarity or if we are truly meant for each other.

Yeah this is a baffling decision. I’d like to know what the motivation is. ASCII doesn’t even contain € or £.

> "Oh they wanted to kill OpenSolaris!" No, the lawnmower doesn't care about OpenSolaris, the lawnmower doesn't think about OpenSolaris, the lawnmower _can't_ care about OpenSolaris. The lawnmower can't have empathy.

For those who don’t get the lawnmower reference, take 5 minutes and have a hearty laugh: https://youtube.com/watch?t=1980&v=-zRN7XLCRhc

(Start at the 33 minute mark if it doesn’t jump you there.)

Fortunately in Rust you can have it both ways, as in `Type::Variant` most of the time and `use Type::Variant; … Variant …` in cases where the type name just causes noise.

Example in the playground: https://play.rust-lang.org/?version=stable&mode=debug&editio...

You can install a Swift toolchain on macOS without Xcode, but Xcode is the “blessed” route and listed first on the swift.org getting started instructions. https://www.swift.org/install/macos

However, it can be a bumpy ride. For example: “swift test” (via the CLI) doesn’t work if Xcode is not installed. https://github.com/swiftlang/swift-package-manager/issues/43...

I would just emphasise that the OP was about _convenience_ and Swift-without-Xcode on macOS is not smooth sailing.