Purism have disabled the Intel Management Engine in their laptops, so the only software you are running is what you installed.

If you switch to this design I will stop reading Slashdot.

It is unusable. Too much vertical space is wasted. Layout does not scale up with font size. Default font size is miniscule. The top three stories are squished together, and I cannot distinguish between them. Story text is truncated too short, so I have to click on *every* *single* *story* just to get the gist, which takes too long.

Please define the layout in units of ems not pixels.

Some of us have hi-res displays and need to crank up the font size for readability. We do not appreciate our content being squeezed into a rigidly fixed-width column, nor do we enjoy the associated wrapping and overflow effects that result.

See http://developer.servalproject.org/dokuwiki/doku.php?id=content:servalmesh:main_page

1. Sit non-techie in front of Wikipedia and navigate to a page of their choice.
2. Click the "Edit" tab and show how easy it is for anyone to modify the article.
3. Explain the productivity benefits of low barriers to entry -- no locks, no approval process.
4. Ask what the downside would be. Hope for an answer about dangers of vandalism or poor-quality contributions by unqualified people.
5. Click the "View history" tab and show how all edits are visible and never lost.
6. Show how easy it is to "rewind" to an earlier version of the article. At this point, the non-techie should start to understand why Wikipedia works and is not just a mess of low-quality, vandalised articles.
7. Help by pointing out how every edit identifies the contributor, or at least their computer (IP address) so they can be blocked.
8. Explain that source code control is like Wikipedia but for computer programming -- nobody's work is ever lost, all contributions are identifiable and traceable, rewinding is easy, and people can build on each other's work quickly and easily.
9. Explain that modern (distributed) SCC systems are much more powerful than Wikipedia in terms of what programmers can do to organise their work and their teams.