So it looks like I've managed to free myself from eXtwitter.

So it looks like I've managed to free myself from eXtwitter.

From their point of view, I suppose, I've managed to get my self in eXtwitter jail.

Some joker was handing out a lot of inane insults to anyone who disagreed with him, and his "friend" congratulated him. And he bragged that it was "fish in a barrel".

Really inane insults. Like 

We say it's so, and we are always right, so you're dumb!!!!

level inane.

Just to remind anyone who reads this, "fish in a barrel" is short for something along the lines of 

It's as easy as for me as shooting fish in a barrel.

 So I responded with 

So you think it's as easy as shooting fish in a barrel, do you?

Well, you just shot yourself in the face.

Good thing your ammunition was only paintballs.

Except I abbreviated a bit:

"fish in a barrel".

Shot yourself in the face.

Good thing it was a "paintball"

Even in full grammar, yeah, it's pretty savage criticism. I acknowledge that. 

And apparently eXTwitter has some automatic bad language recognizer that can't parse English tenses and (not surprisingly) can't parse metaphors, and flagged it, automatically freezing my account. Said it was violent and abusive.

What?

If I had said

Go shoot yourself in the face!

that would be violent and abusive. But you have to be unable to parse past tense to read it that way.

I suppose the very topic of "shooting" is a dangerous topic, but, if that's the case, how is "fish in a barrel" allowed? Unless the bot is so illiterate as to not know where the expression "fish in a barrel" comes from. Maybe it associates the phrase with fesikh, or maybe with kingyo sukui. Or maybe it just has no semantic linkage for phrases at all.

Then it sent me an automated email telling me that, if I wanted to be a good little eXtwitterer and get my account back, I could delete the offending post.

Or I could appeal, but the language style (I fun my computer in Japanese.) indicated that appeals are frowned upon.

So I tried an appeal, but the whole process was in Japanese, leaving me unclear as to whether to use English or Japanese, and the appeal itself is length-limited like eXtwitter is, and whatever human examined my appeal apparently had just as much problem parsing English grammar and metagrammar as the automated gadget, or maybe just decided she (or he) didn't like my point of view.

So my first appeal was rejected.

Now, I will acknowledge, when people make inane comments at the level I am describing here, it's probably wisest to assume they can't parse abbreviated grammar, can't deal with strong metaphors, etc.

And since eXtwitter conversations tend to descend quickly to that level of inanity, I should not use abbreviated grammar, and I should choose less strong metaphors, unabbreviated, like 

You just shot yourself in the foot.

Although I'm not sure I want to hope eXtwitter's auto-nanny 'bot is capable of recognizing that's a metaphor, either. How do you teach a 'bot what metaphors mean?

But, as a metaphor, the problem with this hypothetically easy target game is 

• one, it destroys barrels of fish;
• two, salt water and fish fragments and possibly barrel fragments tend to splash back at the wielder of the gun;
• and, three, if there's enough water, the fish are swimming and the water gets in the way. You're not really guaranteed to hit the fish unless they are dead and packed fairly tightly, and, if they are packed tightly, fish fragments really splash all over.

And fish fragments turn smelly really quickly.

So, you get wet, covered with fish guts, and quite possibly injure yourself from barrel flack. 

And your face is the part of you that is most likely to get the splashback.

So,if you make a habit of shooting fish in a barrel, you're quite likely to shoot yourself in the face.

And if you make a habit of confusing paintballs with bullets -- or with fish, well, ...

Anyway, ...

Yeah, if I value my eXtwitter account, I would swallow my pride and say, all the above is not a reason to have to have my account frozen. 

Even if it amounts to teaching the eXtwitter nannies that they do really have to think to do their jobs.

But, you see, it's been about a week, they haven't replied to my second appeal, and my account is still frozen, and ...

I've been significantly more productive and happier with life over this past week.

No useless arguing with people who aren't interested so much in arguing as asserting that they, themselves, are the rightest of the right. Or the baddest of the bad or whatever. Much more effective use of my time, and much less need to be exasperated with how so many people seem to be satisfied with living uninspired and uninspiring lives.

I'm not sure I want back on eXtwitter.

If I do, though, I need to commit myself to a different approach. Telling people how wrong they are is a fool's game.

Edit [JMR202410040632] 

I'm inclined to delete the post, and get back on just long enough post the above as my final post, and turn my back to eXtwitter permanently.

Microblogging really isn't appropriate for anything but headlines and vanity. 

People try to use it for 'blogging, dialog, and such, but the format is too short, and the threading is too opaque. 

You really can't have a conversation, much less follow it. The most you can do is pretend to argue, but since it's about making short vanity pronouncements. It's all one-way.

And the moderation is the same -- their way or the highway. That's the archetype of abusive relationships.

It's not unreasonable to assert that eXtwitter is one of the root causes of the current fractious and tendentious political climate.

Could Elon fix eXtwitter? Could he make it a medium of actual eXchange?

Hard to say. Make microblogging an index to other services? 

Maybe have it offer to switch to a full blogging platform (WordPress?) when a replies start exceeding the microblogging limit? 

Maybe let it index out to a dialog platform (something like slashdot) when the thread gets longer than five replies?

Definitely get the moderators learn how to parse and communicate in English and the language they are supposed to be supporting. Arrange for on-the-job training, if necessary. Management probably needs to have the same kind of training, though, is my guess.

in it's present form, it just needs to go away.

You Don't Have to be a Sexpert to Think Meaningfully about Sex

You don't have to try every kind of alcoholic beverage to know that people who drive under the influence tend to cause accidents in which other people die.

You don't have to try every kind of tobacco to understand that second-hand smoke is harmful to yourself. Nor do you have to have first-hand smoking experience to watch the effects of tobacco on your coworkers.

I personally can tell you a lot about that. It's one of the reasons I left the software industry. Watched too many companies get dragged to the ground because management and the board of directors had the engineers so focused on getting the job done that they failed to make sure that the job should even be done, much less that it was being done correctly. (Witness Bruce Schneier waxing eloquent on Crowdstrike.) 

And one of the tools engineers use to focus themselves on deadlines instead of safety is tobacco. Coffee is another. And pornography.

You don't have to experience every possible sexual position to understand that sexual position is not what sex is all about.

And you don't have to have sex with every person on the planet, or even just every attractive person you meet, to understand that quantity is not better than quality. Neither do you need to have sex with a whole lot of people to understand that carefully sculpted and painted-on beauty can hide some serious hideousness behind the endomorphin-induced haze.

Sometimes it's easy to see a whole lot of trees and miss the forest.

I'm not an expert on sex like Masters, Johnson, and Kolodny. But I have observed people getting hung up on sex and gender for over half a century, and with so much public focus on the topic these days, I'm re-exploring my previous analysis and understanding of sex.

Sex is an especially difficult topic, since even talking about it seems to make those endogenous (naturally-produced) opiates flow, and the flow alters the brain processes.

Even a single can of beer is said to be enough to cause professional drivers to become sloppy in the places they need to be not sloppy, and yet make them feel that their driving improves under the influence of just that little beer.

In much the same way that it's probably not wise to try to evaluate your ability to drive under the influence when you are under the influence, it's probably not wise to evaluate the effects of sex on you while you are under the influence of those natural peptides.

Unfortunately, being human, living in bodies that naturally produce those peptides, it can be nigh impossible to escape their influence.

Maybe it's best to admit up front that our perceptions on sex are going to be bent.

Since it's probable that the cold light of morning never really comes, maybe it's best to try to reexamine our impressions, logic, and conclusions under the influence of different groups of those naturally produced peptides.

This may turn into a short series of blog entries behind my modesty barrier. If so, I'm inviting everyone along for the ride.

Kakaa Denka （かかあ天下）Wikipedia Page Translated with Google's Help

Feeding the Japanese Wikipedia page on かかあ天下 (Kakaa Denka) through Google Translate produced a remarkably readable translation, if you interpolate some of the weirder translation artifacts. ("We", for some definition of "we", used to talk about "translationisms", but that bit of coinage has been usurped by some weirdness of its own, so I'll use the term "translation artifacts" here. It's probably more technically accurate anyway.)

Note that the Japanese Wikipedia page is flagged as having problems due to lack of reference material and evidence of personal research, or whatever that is in English.

Note also that this is the translation of the page as I am reading it now, and if the page itself is later edited, those edits will not be reflected here. 

(If someone else doesn't beat me to it, I guess I'll clean the translation up eventually and eventually add an English page for it myself. I wish I had more time to participate on Wikipedia.) (Cleaned-up translation below the results of Google Translate.)

Again, the Wikipedia page in question: 嬶天下 (Kakaa Denka)

Original output:

---

Kakaa denka refers to a family where the wife's authority, power, and dignity exceed that of her husband.  

It is said to be a specialty of Joshu, along with ``Karakkaze.''  This is because the area once known as Joshu (Gunma Prefecture) had a thriving sericulture industry, and there were many households where the wife had higher economic power than the husband. On April 24, 2015, the Agency for Cultural Affairs announced that ``Kakaa Tenka - Gunma's Silk Story'' was selected as one of the first 18 Japanese heritage sites.

overview  

Originally, it meant ``a strong wife who protects the house (from winds, etc.) while her husband is away'' or ``My mother is the best in the world (hardworking)'', but it also means ``to protect my husband from the wind.'' It is most often used to mean ``strong wife'' and is sometimes used as an antonym for ``hushu kanpaku''.

Kakaa Tenka in Joshu  

The reason Kakaa Tenka is considered a specialty of Joshu (Gunma Prefecture) is that women in Joshu were responsible for the silk industry, including sericulture, silk spinning, and weaving, and had higher economic power than men. The word is used to describe active and hard-working Joshu women, based on impressions of Joshu's harsh weather environment, such as thunder and wind, and Joshu's harsh temperament (specific examples of prefectural characteristics #prefectural characteristics). .  

Kakaa Tenka as seen in ancient tales  

In archeology, the wife of Kamitsuke no Kimi Kanojo Katana (Kamitsuke no Kimi Kanojo Katana) is mentioned in relation to Kakaa Tenka. Cornered by the Tohoku Ezo, Katana is now weak, so they give him a drink and give him encouragement, while at the same time holding a bow and making a sound on the string, they use their wit to give the opponent the illusion that a large army has arrived. I helped. Judging from the custom of tooth extraction during the Kofun period, it is thought that women could become the head of a household until the 5th century, and the strong position of women is thought to be a vestige of this.

---

First pass cleanup, with original Japanese for reference:

---

かかあ天下（嬶天下）（かかあでんか）とは、妻の権威・権力・威厳が夫を上回っている家庭を指す。
Kakaa denka (かかあ天下・嬶天下) is a term in para-colloquial Japanese for family structure in which the wife's authority, power, and dignity exceed that of her husband. 

[I'll note here that, in my understanding, it's broader than just family-specific structure, and should be legitimately considered a local social structure in which the women's authority, power, and dignity exceed that of the men.]

「からっ風」と並んで、上州名物と言われる。かつて上州と呼ばれた地域（群馬県）は養蚕業が盛んであり、妻の経済力が夫より高い家庭が多かったことによる。2015年（平成27年）4月24日、文化庁は日本遺産の最初の18件の一つとして「かかあ天下 ―ぐんまの絹物語―」を選んだと発表した。
It is said to be a special characteristic of the Jōshū (上州) area, in association with karakkaze (からっ風 [extreme drying/freezing, downburst leeside winds from the nearby Jōetsu region mountains]). This is because the area once known as Jōshū (primarily Gunma Prefecture) had a thriving sericulture industry, and there were many households where the wife had greater economic power than the husband. On April 24, 2015 (Heisei 27), the Agency for Cultural Affairs announced that Kakaa Denka - Gunma's Silk Story was selected as one of the Eighteen Primary Cultural Properties of Japanese Heritage [English page here].

概要 Overview

本来は「夫が出かけている間の家を（からっ風などから）守る強い妻」や「うちのかかあは（働き者で）天下一」の意味であるが、「夫を尻に敷く強い妻」という意味で使われることがほとんどで、亭主関白の対義語として用いられることがある。
Basically, kakaa denka indicates "a strong wife who protects the household (from the strong karakkaze downburst winds, etc.) while her husband is away", or means "the lady of our house is the best (most hardworking) in the world''. But it also generally carries the semantic of "a strong woman who takes the lead" [or, literally (but politely), "... who positions her husband behind her backside", thus, taking the brunt of the wind], and is sometimes used as an antonym for teishu kanpaku [loosely, Japanese version patriarchy, or the tradition that "the lord of our house is the emperor's representative"]. 

上州のかかあ天下 Kakaa Denka in Jōshū

かかあ天下が上州（群馬県）の名物とされる理由として、上州の女性は養蚕・製糸・織物といった絹産業の担い手であり、男性よりも高い経済力があったことがあげられる。雷や空っ風といった上州の厳しい気象環境や、気性の荒い上州人気質（県民性#県民性とされる具体的な例）に対する印象から、活発で働き者の上州女性を表す言葉として用いられる。
A reason given for considering kakaa denka a special characteristic of Jōshū (Gunma Prefecture) culture is that the women in Jōshū took the lead in the silk industry, from sericulture to silk spinning and weaving, and had greater economic power than the men. From impressions of the thunder and karakkaze winds typical of the harsh climate of the Jōshū area, and from the rugged disposition of the people of Jōshū (see Specific Examples of Personality Characteristics Considered Typical of the Various Prefectures -- 県民性#県民性とされる具体的な例), kakaa denka is used to describe the energetic and hard-working women of Jōshū.

古代説話に見られるかかあ天下 Kakaa Denka as seen in tradition

考古学では、上毛野君形名（かみつけのきみ かたな）の妻が、かかあ天下との関連で引きあいに出される。東北蝦夷に追い詰められ、弱腰になっている形名に対し、酒を飲ませ、叱咤激励すると共に自分達は弓を持ち、弦を鳴らすことで、相手に大軍が来たと錯覚させる機知を行い、手助けをした。古墳時代における抜歯の風習からも、女性が家長と成りえたのは、5世紀までと考えられており、女性の立場が強いのはその名残とも考えられる。
In Japanese archeology, the wife of Kamitsuke no Kimi Katana (上毛野君形名) is brought up as an example of kakaa denka. When Katana is weakened and cornered by the Tohoku Ezo armies, she gives him sake for drink and a scolding for encouragment [and gathers and arms the women]. Using their wits, they help [turn the tide] by noisily lifting their bows and strumming the bowstrings to give the enemy the illusion that a great army has arrived. Also, based on customs of tooth extraction [dental work] during the Kofun period, it is thought that women could become heads of families through the 5th century [CE], and the tradition of strong women [in the Jōshū/Gunma area] is thought to be [corroborating] evidence of this.

---

First clean-up pass complete.

Correlation between IQ and ...

I'm being stupid enough to argue with someone who claims a positive correlation between intelligence and all sorts of theoretical "good" things, like longevity and not doing criminal things and wealth and health and ...

One problem with trying to measure intelligence is that there are many kinds of intelligence -- many kinds of smarts.

One kind of smarts is when someone leaves a chair in the middle of the kitchen and you stub your toe and say, quite calmly, "My goodness, that smarts."

Another kind of smarts is when you decide you're going to avoid walking too close to chairs from now on.

Yet another kind of smarts is when you start planning a campaign to outlaw chairs.

And then there is the smarts that just decides to get rid of chairs in your own home and start sitting on the floor like certain Asian traditions have it.

Another kind of smarts redesigns the chair with a circular base and a single supporting leg in the middle where you would have to try pretty hard to stub your toe.

And then there is the smarts that finds out who left the chair there and fines or sues that person for endangerment.

And then there is the kind of smarts that just grabs the chair and sits down and rubs the toe until the circulation returns, then pushes the chair back under the table, out of the way.

I know which smarts I would prefer to exercise, if I am fully in control of myself.

But it takes all these kinds of smarts to make up a world. Yeah, I suppose even the smarts to sue and/or outlaw chairs.

Which of these smarts are tested on IQ tests?

Why I Haven't Returned to Teaching English

I really don't have time to be writing this, and I'm sure friends will just roll their eyes and say I'm using avoidance tactics again. And they probably wouldn't exactly be wrong.

But there's something that seems to really need to be said.

I apologize for the length of this, and for not doing the expository thing where I tell you up front and then tell you in detail, and then tell you again. If I approach it directly, most people's immediate reaction will be to argue with me.

Yes, I am a good teacher. Yes, I have the skills teach English, certain science fields (particularly computer science), and math, among other things.

Japan, just like the US, just like much of the rest of the world, needs good teachers -- I mean, really, really needs good teachers, in all subjects -- except the current most popular subjects. (Actually, that's, except the subjects that were most popular two-to-six years ago. There's a delay between demand and supply called getting the degrees.) 

Why? Where are the good teachers and why aren't they teaching?

There are three parts to answering that question, and I'll start with the easiest one first.

There are a lot of mediocre and bad teachers in the education industry. (Don't argue with me on this, education has become an industry.)

And when they see a good teacher at work, they become jealous, and fearful for their jobs. And they start resorting to defense tactics -- mostly subconsciously, I think. I hope.

What defense tactics?

• Reports and other paperwork are not inherently evil. But they can easily be overdone in volume and style, and other aspects. Overdoing such things eats away at preparation time and other important resources.
• Likewise, meetings and evaluations are not inherently evil. Likewise about volume, structure, and goals, and about eating resources.
  
• Inventing new approaches is a good thing. Trying to enforce them on everyone else is pure evil.
  
• Praise and critique are important and good. Faint/false praise and hidden sniping are evil.
  

For some reason, mediocre and bad teachers are very good at turning attempts to improve things into defense tactics.

And, truth be told, the mediocre and bad teachers could be good teachers if they would actually engage with their subject matter while engaging in defense tactics, and if they would actually dare to engage with their students in meaningful ways (and not just in discussing whatever the currently popular topics are and otherwise currying student favor and encouraging teacher's pets).

Why are so many teachers willing to undermine the education systems?

Here's where I really get into controversial stuff.

I think it was Thomas Jefferson who said it. I'm not sure. It was one of those guys who worked on the US Constitution and played an important part in the birth of the US of A.

Public education should be for children who don't have family who can pay for their private education, was part of the idea. And it should be limited to three years, just enough to get the basics of reading, writing, and arithmetic. From there, from about the age of nine, ten, or eleven, education should be primarily the responsibility of the individual, initially guided by parents or legal guardians -- individual students, individual children choosing their own courses through the school of life.

I may be remembering that wrong, as well, but I think that's the gist of it.

Education is a lifelong process, and there is nothing more suppressive to education than to force people to study what they have no preparation for and to delay them unreasonably from studying what they are already prepared for. Public education programs can't avoid both pushing students too far ahead and holding them too far back. It's simply in the nature of systems.

The education industry itself engages in defense tactics. Schools are by no means the only source of what they advertise as their main products -- knowledge and education. And I'm going to refrain from repeating myself in analyzing what the industry does, by means of those who run it. 

Wait. If it's true of public education, why isn't it true of private education?

In Japan, Juku has this problem in spades. The Ministry of Education has been trying to reform the entrance examination systems for several decades, but teaching for the tests is viewed as the lifeblood of the juku. 

Teachers who have not yet obtained tenure do not want to risk their safety net if the don't get re-hired next year, any more than those juku teachers who have not had public education experience. Nor do tenured teachers want to risk their post-retirement options.

Thus, teaching the tests has become entrenched in private education.

Teaching the tests is not education. Can't we finally get past that?

Tests are supposed to be opportunities for the students to stretch and evaluate their mental muscles, but they have primarily been perverted to gate-keeper roles where there should be no gate-keepers -- or, rather, where gate-keepers should be there to help, not prevent.

Tests are being used as tools of exclusion, which is in direct opposition to the only valid purpose of both private and public education.

In Japan, three years is not really enough to master reading and writing.

In the modern world, addition, subtraction, multiplication, and division are no longer enough.

But we wouldn't be asking them to master anything at school. Mastering things would be done in real world. 

If we want to solve the teacher shortage, we need to integrate the education industry with the real world.

Anyway, since the bike-car accident I had about five years ago, I just don't have the energy to engage in the constant battles that go on between what should be and what is in the education industry.

If I Won the Lottery --

I don't play the lottery, as a matter of principle. But if someone I trusted bought me a lottery ticket --

It would have to be someone I trusted who bought me the ticket, because "free" money does things to people. 

If it were someone I didn't trust, I would have to waste a lot of time and probably most of the winnings buying off the interest of the giver of the ticket.

Money always comes with obligations. It's an economic principle. It's in the nature of what money is. 

You can never really have "free" value. Value must be generated, and generating value incurs obligations. 

Rich people simply ignore the obligations, saying they know better what to do with it, burning their charisma to get room to exercise their own will on the value.

And money is a (poor) proxy for value.

And I have never been able to simply ignore obligations when I had any means to respond to them.

-- So, if someone I trusted bought me a lottery ticket, and it hit a jackpot, what would I do with it? 

(This is hypothesis contrary to fact. It ain't gonna happen. But what you do with your free time, what you do with your excess, that's what defines you as a person. That's what demonstrates your true priorities. So what I'm doing here is thinking about what I'd do if I had excess. I'm trying to figure out my current priorities.)

First, I'd make sure my taxes and national retirement/social security obligations would get taken care of. Then I'd pay into as much retirement funds as the tax laws allow, both for myself and for my wife. Then I think I'd pay off my children's school loans. Maybe I'd have enough to fund them in going back for advanced degrees. Maybe I'd invest some in the companies they work for. Maybe I'd send my wife to Europe to study nutrition and cuisine. Family obligations.

But that is not what this is about.

If I had a lot of wealth to use as I saw fit (hypothesis contrary to fact in so many ways), I would use it where I think some gaping holes in our society exist, where I think I could apply myself in meaningful ways. 

It would be tempting to provide extra funding for various Free/Libre software: 

• Gramps, 
• the GIMP, 
• Inkscape, 
• gnu compiler collection and Clang/LLVM, etc. 
• and more niche software, like CAD, circuit design and such
  
• etc. 

But even just ten thousand here, a hundred thousand there, and a million over there would tend to fritter the money away, so that would not be the first thing I'd do.

It would be tempting, and useful, to start my own distributions of Linux and *BSD operating systems. But, again, it would be easy to try to set up a competitor to Ubuntu and Apple, and that would definitely be an easy way to fritter money away.

It would be tempting to start an English as-a-foreign-language company doing it the right way. So many ways the current approach to teaching English as a foreign language are just fundamentally wrong. But it would be a hard sell, and if I succeeded in the sell, Japanese copycats would spring up all over. That might not be a bad thing, but it would burn money.

It would be more than tempting to start my own social media service, with a fundamentally different business model. Or perhaps buy OSDN for the infrastructure. But focus on making it reasonable for the customer to own their own

• domains
• servers, including mail, authoring, financial transaction, etc.
  
• authoring and archiving tools
• publishing
  

and to provide a base community for the customers to reach out from. But I'd basically be trying to take on Google, even if I'd be doing it right as opposed to them. And if I succeeded, I'd have to fight off Microsoft's attempts to buy me out and/or to embrace and extend me.

I'm getting old. I don't have time for all of that.

I have lots of novels I'd really like to finish and publish. That would not take nearly as much money.

And one thing I'd like to do before I die, if I could somehow arrange the money and time, is to define extensions and revisions to my four favorite CPUs

• 6805
  
• 6801 
• 6809
  
• 68000
  
• 6847

Wait. Why is the 6847 in this list? It's not a CPU. It's a video display generator -- a VDG. (I will explain.)

But, why? you ask. You think you understand why I want to avoid Intel x86 and AMD64, but we have ATmega and ARM. They're cheap, can be had in a variety of small, medium, and large packages, and they can be programmed in C and other high-level languages.

But you need the high-level languages. ATmega, ARM, RISC-V, and other modern CPUs are hard to work with at the assembly language level. Sure, they have a lot of development tools to help, but you don't want to work on them without the tools. That means you really don't understand what's happening at the low level. You only think you do, and I don't think that's a good thing.

Motorola's CPUs were easy to work with at the assembly language level. Maybe too easy. But it is actually possible for ordinary people, with a little coaching, to read the assembly language source code and get an idea of what's happening in the code. Other CPUs, especially modern CPUs, not so much.

The one problem with Motorola CPUs is that they each had small design flaws that meant that, as you extended and redesigned your product, you eventually hit walls. And getting past those walls meant using programming techniques that made it hard, again, to understand what was going on.

The 6847 VDG was similar. it was really simple to design display controllers with it and it was really simple to program. It was great for getting output on an ordinary TV (back when more homes had TVs than telephones). Which meant you didn't have to buy an expensive monitor to get output from a computer that used one. 

But the display window was small, barely large enough to display even a small paragraph of text. And Motorola never extended the design. (Radio Shack/Tandy did, but that was too many years down the road.) (Oh, well, actually, Motorola did do some design work to extend the 6847 design, a couple of years after they should have, and in the process of trying to play catch-up, the design ended up overkill, too expensive, and too hard to design for and to test. I'll have to try to remember to link something about that here, next time I see the relevant pages out there on the web somewhere.)

  |12345678901234567890123456789012|
  +--------------------------------+
 1| HOW SMALL WAS THE DISPLAY      |
 2|WINDOW ON 6847-BASED DESIGNS?   | 
 3|THE ABOVE PARAGRAPH WOULD NOT   |
 4|FIT IN A SINGLE SCREEN. AND THIS|
 5|PARAGRAPH ALONE WOULD TAKE      |
 6|ALMOST HALF THE SCREEN.         |
 8|                                |
 9| THE SCREEN SHOWED EXACTLY 512  |
10|8-BIT CHARACTERS. THAT'S 16     |
11|LINES, EACH 32 CHARACTERS WIDE. |
12|THE ASPECT RATIO WAS BETTER THAN|
13|WHAT YOU SEE HERE, SINCE THE 32 |
14|CHARACTER WIDTH SPREAD ACROSS   |
15|MOST OF THE TV SCREEN, GIVING   |
16|CLOSE TO 4:3 WIDTH-TO-HEIGHT.   |
  +--------------------------------+
  |12345678901234567890123456789012|

That's a tight screen. 

And lower-case characters were not available in most 6847 designs until about 1985, unless the design included an external character ROM, or unless you switched to graphics mode and wrote all the bits for each character to the screen yourself.

The 6847 was great in 1979 or even 1981. Not so great in 1985.

This is really what I mean by flaws and hitting walls. Motorola could have extended each of these, so that the walls could be easily gotten past by the time the average user was hitting them. 

Wait. If you are familiar with the 68HC- and later series processors, you are saying, but Motorola did exactly that.

Well, yes and no. Except for the 6805 series, Motorola was always on the trailing edge of the market window. They were too slow in extending the designs. And when the entire industry took a hard right turn and ran off into the weeds on the question of where to store parameters, Motorola just ended up following, in spite of the fact that the designs of the 6809 and 68000 were such that it didn't need to happen.

Which is where I want to focus on in my attempts to redesign these.

6805:

The original 6805 could only use the hardware stack to keep return addresses. If you wanted a parameter stack, you had to do that as a software stack, and that meant juggling the software stack pointer with whatever you might have in the X register. Used time and code, and required you to be really careful about interrupts.

So I want to give the 6805 an additional stack, moving the return address stack out of the direct page (the first 256 addresses) and replacing it there with the parameter stack.

Motorola sort-of fixed this in upgrades to the 6805, the 146805 series and the 68HC05 and 68HC08 series and beyond, but what they did was just allow parameters and temporaries to be mixed with return addresses on the return stack, which is exactly where the entire industry veered hard right. It's a dangerous practice. (You can easily end up trying to store return values on top of return addresses and trying to return to data instead of code, and this is exactly one of the easiest places for bad actors to hack their unauthorized way into your system.) And it ends up a bottle-neck in code, since the code has to continually tip-toe around the return address.

Other obvious extensions -- 

Extending the X register, as is done in the 68HC08, is useful, but not the first lack I'd address. 

Also, adding the ability to index off the stack pointer, as is done on the 68HCS08, is very useful, but I'd do that to the parameter stack, which means the parameter stack comes first.

6801:

The 6801 inherited its pushes, pops, and so forth from the 6800, with which it is object-code compatible, which means a single mixed stack unless you want to synthesize a software stack. Being able to push the X register on the return stack helped a little when using software stacks, but it really needs a separate parameter stack as well.

In addition, the 6801 has an add B to X (ABX) instruction which is sort-of useful for accessing fields in records and such, and for deallocating large stack frames, but it doesn't have the matching subtract B from X (SBX), which would have been useful for allocating stack frames.

Furthermore, the unary instructions on the 6801 (like the 6800) do not have direct-page address mode opcodes. If you want to increment or decrement a counter in the direct page, you have to settle for using extended (or absolute) mode, which takes six cycles instead of four, so you end up preferring to pull counters into X or an accumulator instead of fully utilizing the instruction set.

These are the three flaws in the 6801 that I want to fix. They are not even addressed in the 68HC11.

Giving the 6801 wider addressing is definitely a useful feature. This is addressed in the 68HC16, and I think I might address it in my upgrade to the 6801, but, where the 68HC16 gets only four extra bits of indexing (for each of its index registers) and four bits to extend the extended (absolute mode), I'd tend to add an eight-bit extension register for the X register and for the extended addressing mode. I'm not sure whether I'd add eight bits to either stack register, since it doesn't seem too unreasonable to keep both stacks within the first 64K of address space.

 

6809:

The 6809 has direct-mode unaries and two stacks. It's almost perfect. But it has a funny omission in the indexed-mode addressing modes. Where it is able to use an indexed mode to do memory indirect addressing on extended (absolute) mode addresses, there is no such indexed mode for the direct page. That means that indirection through pointers saved in the direct page must be done by explicitly loading the variable into a precious index register. It also means that taking the address of a direct-page variable can't be done with just a LEA instruction. You have to use three instructions, to bring the DP register into the A accumulator, move the offset into the direct page into the B register, and use LEAX D,X or likewise the Y index. 

This severely limits the use of the direct page register as a base for per-process static variables, which is something you really want in processors as capable as the 6809.

I'd definitely widen addressing on the 6809 by 16 bits, either by 32-bit segment registers (similar to the 8086's segment registers, but done right from the outset) or by simply adding 16-bit extension registers similar to the 68HC16's four-bit extension registers. But that's less a design flaw and more an extension feature.

I could then create a true 16-bit version of the 6809 as a follow-up, but not the way it's done in Hitachi's unofficial 63C09 extensions. Those are rather haphazard, and ignore the design of the 6809, tending, rather, to make it look more like the 8086.

68000:

One flaw in the 68000 is in the exception stack frames. This is fixed in the 68010. 

But another flaw in the 68000 is that constant offsets in indexing are limited to 16 bits. This means that relative branches and module tables have a natural limit of plus/minus 32K addresses, which becomes too tight when modules exceed 32K in size. Getting around that requires using an address register, which is not completely bad, but it does tend to discourage good programming practices. This flaw is not addressed until the CPU32.

The flaw in the 68020 is excessive complexity, which is why I would not go that direction. Actually, the CPU32 might be sufficient, by which I mean I would not really need to do anything in particular about the 68000.

6847:

Extensions to the 6847 include gradually more capable versions. Sprites are not necessary for every application that wants 64 characters or more per line or 512 by 384 graphics modes, more colors, lower-case characters, etc.

Also, since I'd want to use these in modern devices, I'd want to add circuitry to directly control LCD or OLED displays.

Tools:

All of these need developer tools -- assemblers, compilers, debuggers, emulators, hardware design tools, and such. Tools also take money to develop.

Conclusion:

If I were making enough at my current job, and had the energy left over at the end of the day, I could work on my novels, or work on a 6805 emulator. I shouldn't really need to win the lottery to do that. If I had the energy. If I were making enough at my current job.

What I probably need to do instead of daydreaming about this kind of stuff is figure out how I can teach private English classes during my days off.

Examining Japanese Semantics: ゆるす (yurusu -- to permit or forgive) -- 日本語の意味を探る〜「ゆるす」(permit もしくは forgive)

Japanese has several words pronounced 「ゆるす」 (yurusu), and, together, they present an interesting take on the concept of forgiveness.
日本語には「ゆるす」と発音される語彙は複数あります。併せて考えれば、（英語の) forgiveness について面白く語るのです。

* The first set of semantics I offer, sometimes written with Kanji as 緩す、 means to loosen (transitive), as in loosening a pet's collar. It is of course related to 緩める (yurumeru), which is a more general word meaning to loosen.
最初に取り上げたい意味としては漢字では「緩す」とよく書かれるのです。これはペットの首輪のようなきついものを緩めるのようなことですね。「緩める」という方が一般的と思います。

* The second, which is the more generally referenced meaning, is usually written as 許す、 or sometimes as 聴す、 when using Kanji. The latter writing refers particularly to 聴く (きく - kiku)、 which means to listen carefully, as you might listen to the music in a performance, or to a defendant's testimony at trial.
その次に取り上げるのは漢字では「許す」もしくは「聴す」と書かれるのです。後者の字は特に注意深く聴くことに関連し、演奏の音楽や裁判の被告人の証言にじっくりと耳を向けることを参照するいみです。

In this set of semantics, ゆるす (許す or 聴す) means
この意味の場合の「ゆるす」（許す・聴す）の意味は次のようなものです。

• to hear, recognize, and accept a person's requests, desires, requirements, etc.,
  人の願いやら希望やら要求などを聴き、認めて良しとする、
• to adjust things or allow them to be adjusted so as not to inconvenience said person,
  不都合がないように物事をその人に併せるか、その人に合うようにしておく、
• to allow said person to do as he or she pleases or thinks, to give license or permission,
  その人の趣味通り、思い通りやっても良いように許可を与える、
• to put a captive at liberty,
  捕らえ人を開放させる、
  
• or to give a degree of freedom to. (This meaning can also be used in engineering and physics when talking about the degrees of freedom an element of a machine has an a particular axis.)
  自由度を与える。（この意味は工学や物理学に使用される意味です。特に、ある機械の一部がその機械の中で特定の軸に対しての自由度です。）

This is the semantic referenced in the word 許可 (きょか - kyoka)、 which is permission, often formal permission. For example, when I need to deliver mail to the huge apartment blocks around the train station, I must go to the police station and get a 駐車許可書 (ちゅうしゃきょかしょ - chūsha kyokasho) -- a parking permit.
つまり、許可そのものです。正式・公式許可も暗黙の許可です。例としてあげれば、駅周辺の大きいマンションに郵便配達に行く前に、警察署に行って仮駐車許可書 (temporary parking permit) をもらっておかないと行けないのです。

The key meaning here is that permission is given or recognized in advance.
「事前の許可」が決め手の意味です。

* The third set of semantics I offer is related to relaxing one's guard, to allow oneself to be set at ease, to open up.
三目のその意味合いは気をゆるす意味、警戒感・緊張感などを緩めることです。落ち溶けることも。

* The fourth is to extend recognition, including in some senses, recognition of value.
四つ目は、受け入れる、認める意味です。場合によってはものの価値を認めるのです。

* The fifth, usually written as 赦す、 generally refers to things which have already happened. The meaning here is to allow one to be forgiven of sins, mistakes, offenses, crimes, etc., which are in the past -- to agree not to seek revenge or further recompense or punishment.
５番目の意味合いは普通は「赦す」で表すのですが、できてしまっているもの、つまり、過去の出来事に対して言うのです。これの意味は過去にある罪、過ち、侵害、犯罪などを赦すのです。つまり、赦す時点よりはもう、報復、賠償（及び返礼）、処罰（または処置）などを求めるのをやめるように承知する。

* The sixth, also usually written as 赦す、 is the resolution, removal, or dismissal of existing responsibilities and/or duties, and the forgiveness of debt.
六番目も「赦す」と書き、既存の責任や義務を解除もしくは解消することも、負債も借金も借りも取り消すことです。

Speaking broadly, we can say that
一般的にまとめると、次の通りに説明できます。

• 許す has more to do with permission and license on an on-going basis,
  「許す」はこれから先（将来的に）許可や免除を与える意味ですが、
• where 赦す has more to do with forgiving things that have been done and putting them in the past.
  「赦す」とは過去に在ったものを、終わっているものとし、赦して、これ以上の償いを求めないことです。

I'll note here, that English has parallels in common usage. Informal dialog often fails to distinguish between forgiving things which have happened in the past and giving permission for them to continue in the future.
ここに云っておくけど、英語の普通会話の言葉遣いにすると、似た作用があります。一般的に喋っていると過去に在ったものを赦すことと、諸らいにできるかも知れないものを許すことの区別はしないのがよくあります。

Sometimes, the distinction is not necessary. Every now and then, the ambiguity can defuse a dangerous situation.
場合によっては区別しなくてもいいです。稀にその曖昧性で緊急な危険状況を和らげることもあります。

But making a habit of allowing serious abuse in the name of forgiveness really is not forgiveness at all, even if there seems to be a similarity. There is nothing redemptive in doing so.
但し、赦しを唱えて、習慣的に虐待や不当扱いを良しとするのが、赦しに見えても全く赦しではありません。贖罪と関係ありません。

It's a false similarity. (And I suppose, having said this much, I should write further on how such permission to do evil is actually the opposite of forgiveness, but I'm out of time tonight.)
偽類似です。（ここまでこの話を進めれば、悪を行うようことを良しとするのが赦しの真反対になることを説くべきですが、今晩にしては時間がゆるしません。）

(Erm, actually, last night. Translation took until this morning, and I am really out of time, now. ええっ、実は昨晩でした。訳すのを今朝にかけておわり、今はもう、本当に時間がゆるしません。 I did get some sleep, though. と言ってもある程度の睡眠ができまして、ご心配不要。)