because you people made it illegal for teachers to live in your area
Strawman. No one made it illegal to be a teacher (or fireman or whatever), and no one made anyone take that job either. If it's too expensive to live in SF as a teacher or fireman, then teachers and firemen start to disappear. If they are important, then their local salaries will get raised until they stop disappearing. That's how economics works.
Now clearly this causes lots of undesirable dislocations. But the fundamental problem here, as far as I can tell, is that SF's government appears to have discouraged building new housing, and been depending on mechanisms like rent controls which have KNOWN serious problems. You can pretend economics doesn't matter, but it does, and it causes lots of easily predictable effects. The SF city government appears to have let a problem fester, with (again) predictable consequences. It is entirely appropriate to be sympathetic to the many people harmed by the SF government's bad policies. Yes, they need help, and I think they SHOULD get help. But part of that help needs to be acknowledging that ignoring economics doesn't work.
My heart goes out to those evicted, or fearing eviction. To my untrained eye, the problems seem like an obvious result of supply-and-demand. SF has limited land, hasn't built much in the way of housing for a long time, and is in high demand. Of course the housing prices will go way up. The only solutions are to make it less desirable (lower demand), or increase housing (increase supply). Here's an interesting article: https://medium.com/@Scott_Wien...
Other cities have done this, e.g., DC has aggressively added new units.
I think a key part is simple: good story quality. Key steps:
The discussions are sometimes interesting - and sometimes not. But I think if the stories start higher-quality, the follow-up discussion is more likely to be better.
In the longer term, the system for entering text is... quirky. Has someone considered using Markdown? Yeah, Markdown processors vary, but lots of people know Markdown (e.g., via GitHub), and specs like CommonMark and libraries like Red Carpet make it fairly painless.
The point of the article How are students learning programming in a post-Basic world? isn't that we should all use Basic. The point is that there's a need for a single 'starter' language so that people who have no experience can get started using something. That language should come with practically all computers, should be portable enough so that you can write programs that port to many computers, should be immediately accessible so beginners can quickly learn some basics, and should be useful enough so that beginners can create useful programs.
There are a number of reasonable contenders, including Python, Ruby, and Java. A version of Ruby comes with MacOS, but none of these 'just comes' with the computer regardless of what OS you run - so in most cases, before you even get started, you have to explain how to download and install something. Not ideal. Java is what a lot of people use professionally, but it does take more time to get started when you know nothing. Python has many advantages for simplicity, but you need to install it in many cases.
We have a equal opportunity Calculus class -- it's fully integrated.