Sunday, May 10, 2020

Response to George Will, part 2

Let's step back and look at the overall effect of Will's opinion piece.

Does any knowledgeable historian seriously doubt the following facts?

1. That slavery existed in the American colonies from 1619 and continued until the end of the Civil War.

2. That non-plantation slavery started during reconstruction and continued in various forms into the 20th century.

From the Wikipedia: "[The book, Slavery by Another Name] explores the forced labor, of prisoners, overwhelmingly African American men, through the convict lease system used by states, local governments, white farmers, and corporations after the American Civil War until World War II in the southern United States."

3 That the 1619 project accurately describes the effects of both forms of slavery. These effects continue to this day:

- Innocent non-whites such as Ahmaud Arbery continue to be murdered on a regular basis.
- The rights of non-whites to vote are under continual attack, as illustrated by the debacle of the recent elections in Wisconsin.

These are the inconvenient truths Will seeks to discredit. He does so in the usual way:

An accurate title would be, "Some statements of the 1619 project are debatable." Instead, Will smears the entire project. 

Alas, those who want to discredit the 1619 project can now just say, "George Will, writing in the Washington Post, demonstrates that the 1619 project has an ax to grind". The actual content of this article hardly matters. The smear will make the usual rounds, reinforced by those who never read the original. In the process, it will likely morph into "Everyone knows the 1619 project fake news."

In short, it is regrettable that the editors of the Washington Post have chosen to publish this piece. It would be more appropriate in the New York Post :-)

Friday, May 8, 2020

Response to George Will re the 1619 project

 In an opinion piece in the Washington Post, George Will professes to have a problem with The 1619 project. Here is my response to his nonsense, first published as a comment:

The 2020 Pulitzer Prize for Commentary cited Nikole Hanna-Jones of the New York Times as follows:

"For a sweeping, deeply reported and personal essay for the ground-breaking 1619 Project, which seeks to place the enslavement of Africans at the center of America's story, prompting public conversation about the nation's founding and evolution."

When I first read the articles of the 1619 project, I kept exclaiming, "Wow." I consider myself an educated person, but I simply had no idea that the effects of slavery are still so widespread and pernicious.

Here are some titles from the 1619 project:

- If you want to understand the brutality of American capitalism, you have to start on the plantation.

- Myths about physical and racial differences were used to justify slavery—and are still believed by doctors today.

- America holds onto an undemocratic assumption, that some people deserve more power than others.

- Why doesn't the United States have universal health care? The answer has to do with policies enacted after the Civil War.

- Slavery gave America a fear of black people and a taste for violent punishment. Both still define our prison system.

- The sugar that saturates the American diet has a barbaric history as the 'black gold' that fueled slavery.

- A vast wealth gap, driven by segregation, redlining and evictions and exclusions, separates black and white America.

- Most Americans still don't know the full story of slavery.

And there's more, including poetry and photography.

Against all this, Will desperately tries to change the subject, objecting to quotations out of context. He simply ignores the respected historians who consulted on the project.

Indeed, when I first read Will's "critique," my first reaction was "Huh?" Is he talking about the same nuanced, graceful, powerful history that won the Pulitzer Prize?

In short, Mr. Will's essay is itself ideological, slovenly, and dishonest.

Thursday, April 30, 2020

Wednesday, April 1, 2020

Leo 6.2 and 6.2.1 released

Leo 6.2/6.2.1, http://leoeditor.com, are now available on GitHub.

Leo 6.2.1 adds the manifest needed to do pip install leo. Otherwise 6.2.1 is identical to 6.2.

Leo is an IDE, outliner and PIM.

The highlights of Leo 6.2
  • Added the fstringify-files and diff-fstringify-files commands.
  • Improved the beautify-files command. Added the diff-beautify-files commands.
  • Added the TokenOrderGenerator and TokenOrderTraverser classes in leoAst.py.
    Leo's fstringify and beautify commands use these classes.
  • Added importers for the rust language and todo.txt files.
  • Added the viewrendered3 plugin.
  • Leo's legacy layout is now the default.
  • Fixed all known bugs, including some notable, long-standing bugs.
  • Fixed several "fit and finish" issues.
  • Removed unused settings from leoSettings.leo.
Links

Tuesday, March 31, 2020

US President fails to meet minimal standards of community conduct

In a Leo post I said, "Imo, [Leo's] leaders should focus first and always on maintaining respectful communications. Something like the Python code of conduct or Apache code of conduct should always be on your minds. The goal should be to encourage others, not to show how dashed smart you are."

I wasn't thinking about the US President when I wrote this. Really. It was only later that I saw how comprehensively he fails to meet these guidelines.

Thursday, March 19, 2020

Leo 6.2 b1 released

Leo 6.2-b1, http://leoeditor.com, is now available on GitHub.
Leo is an IDE, outliner and PIM.
The highlights of Leo 6.2
  • Added the fstringify-files and diff-fstringify-files commands.
  • Improved the beautify-files command. Added the diff-beautify-files commands.
  • Added the TokenOrderGenerator and TokenOrderTraverser classes in leoAst.py.
    Leo's fstringify and beautify commands use these classes.
  • Added importers for the rust language and todo.txt files.
  • Added the viewrendered3 plugin.
  • Leo's legacy layout is now the default.
  • Fixed all known bugs, including some notable, long-standing bugs.
  • Fixed several "fit and finish" issues.
  • Removed unused settings from leoSettings.leo.
Links

Tuesday, November 12, 2019

Leo 6.1 final released

Leo 6.1, http://leoeditor.com, is now available on GitHub.

Leo is an IDE, outliner and PIM, as described here.

The highlights of Leo 6.1
  • Pyzo in Leo: Pyzo can optionally run within Leo.
  • Added support for asciidoc and asciidoctor.
  • Added support for pandoc and sphinx.
  • Added support for black.
  • The history_tracer plugin animates git commits.
  • Integration of Leo with VS code.
  • New command-line arguments: --global-docks and --window-spot.
  • New cursor-movement commands.
Special thanks to Vitalije Milosevic, Brian Theado, and Matt Wilkie for their contributions to Leo 6.1.

Links