A few months ago there was a big thread on documentation and I said I was convinced that markdown files and an SSG was the way to go, with some kind of web CMS that auto gits for the non technical people. It got a huge amount of upvotes but also got quite a few nay sayers some of whom said something along the lines of “businesses don’t care about portability” to which I said “they absolutely will if one day atlassian hikes the prices, gets acquired or the product is discontinued”. Well here we are. Keep it simple and keep it non proprietary wherever possible otherwise you are always running the risk of being held over a barrel.

Use markdown files and a SSG. It is literally free. It makes documentation quick and easy to write which means devs are more likely to actually do it. The “markdown is not very good for tables” issue has been solved long ago with either plugins such as “advanced table plugin” for Obsidian or apps like the £10 one off payment app “TableFlip” by Brett Terpstra.

Have a look at the following stuff:

- AstroJS: SSG that allows you to use any JS framework you want.

- Docusaurus: React SSG designed specifically for documentation

- SSGs in other languages: Hugo(Go), Zola(Rust), Jekyll(Ruby)

Then just Google “git cms” for a list of different options on that front. I believe Netlify cms is probably one of the most popular.

- Alternatively just write, sync and publish all in Obsidian using the Obsidian sync and publish services.

> rainbow palette for use in my data visualisations.

Indeed for her kind of data the rainbow palette works okay. But if you have to visualize more complex / denser data, beware of the pitfalls of the rainbow color palette. It is not always the best choice.

IBM did research back in the 90s on perceptually-based colormaps and how to best represent various types of data within the color dimensions of luminescence, saturation and hue [1]. For example, they found that,

(1) Hue was not a good dimension for encoding magnitude information, i.e. rainbow color maps are bad.

(2) The mechanisms in human vision responsible for high spatial frequency information processing are luminance channels. If the data to be represented have high spatial frequency, use a color map which has a strong luminance variation across the data range.

(3) For interval and ratio data, both luminance- and saturation-varying color maps should produce the effect of having equal steps in data value correspond to equal perceptual steps, but the first will be most effective for high spatial frequency data variations and the second will be most effective for low spatial frequency variations.

===

[1] the original link got removed from IBMs website. Back in the day it was under

https://www.research.ibm.com/people/l/lloydt/color/color.HTM

A pdf copy is here:

https://github.com/frankMilde/interesting-reads/blob/master/...

Still looking for viable replacement:

* Joplin had some issues I've checked year ago.

* Apple notes while I have iPhone there's no Windows app.

* OneNote is just trully horrendous app.

* Obsidian just can't convince myself. I'm forcing myself to use it work, while it works, it's not something I enjoy doing.

* Notion is odd, everything is a block and sometimes formatting is just meh...

* Google keep is just simple note and that's it(unless something has changed).

Any worthy apps to look at besides those?

It's not transformative at all, nor quoted for study/discussion, and that's exactly what makes it a problem.

If the snippets merely had attribution, they'd be both legal and acceptable to most open source authors.

The code is not transformative because the quoted code is not used for some other purpose like as part of an article discussing whatever the code does, it is used to do exactly it's original job.

If you wrote a book by quoting choice paragraphs from other books, without crediting any of them, presenting the new book as simply your pile of deep insights, that is not transformative, even though your book is not the same as any single of the source books. It's also not fair use, even though all the quoted bits are short, both because of the usage and the lack of accreditation.

We could have something like copilot just fine if done above board, but as it is right now github are simply outlaw and with no excuse at all.

I found Bionic 10% slower than Literata.

But I also found I am a verrrry slow reader. My reading speed came to 147 wpm. Any recommendation to improve this?