Battle of Vaal Krantz

The Battle of Vaal Krantz (5 February to 7 February 1900) was the third failed attempt by General Redvers Buller's British army to fight its way past Louis Botha's army of Boer irregulars and lift the Siege of Ladysmith. The battle occurred during the Second Boer War.

Background

In the first and second attempts at relieving Ladysmith, Buller's army was defeated by Botha and his Boer army at the battles of Colenso and Spion Kop. British casualties soared to 3,000 men, while the Boers lost only a few hundred.

Battle

British naval guns in action at the Battle of Vaal Krantz

Vaal Krantz was a ridge of kopjes (small hills) a few miles east of Spion Kop. Buller tried to force a bridgehead across the Tugela River with the Rifle Brigade and Durham Light Infantry prominent amongst his troops. After three days of skirmishing, the British general found that his position was so cramped that there was no room to drag his superior artillery up to support the British infantry attacks. Buller called a council of war and, "All his generals agreed that there was nothing for it except to try a new attempt elsewhere."[1] Pakenham wrote that the British suffered 333 casualties,[2] but Symonds put the British casualties at 30 dead and 350 wounded with Boers casualties were 30 dead and 50 wounded.[3] Vaal Krantz was a minor defeat. On 14 February, Buller launched his fourth attempt at the Relief of Ladysmith and finally succeeded.

Further reading

  • Pakenham, Thomas. The Boer War. New York: Avon Books, 1979. ISBN 0-380-72001-9

Notes

  1. Pakenham, p 361
  2. Pakenham, p 322
  3. Symons, Julian (1963). Buller's Campaign. The Cresset Press. p. 257.
gollark: > yes, but sql queries are very fast and well-optimised for that reasonIt's quite easy to foolishly run them sequentially, and then you have to deal with a ton of latency from connecting to your database.
gollark: Although what you can do nowadays is package it as a webview thing (not electron, there are saner things to use the system webview like this: https://crates.io/crates/web_view) and have a bit of native code for the out-of-sandbox parts. Although you drop some nice things that way.
gollark: Also, the sandboxing *can* make it not work for some applications.
gollark: There are obviously problems like compatibility across browsers, having to write typically nonzero amounts of JS, and some amount of weirdness.
gollark: You can load and run your applications on basically any modern platform with no install step, they can easily connect to your backend, webapps are well-sandboxed, it has *very* nice rendering/UI capabilities, and you can run code in basically whatever language you want via WASM (although it may be slow).
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.