notable VS js-framework-benchmark

And I was confusing it with https://notable.app/

I tried many note-taking apps and finally settled on Notable[0]. It's simple and you can point it to a folder with markdown files and attachments. Plus, you can just sync the folder using any syncing service, and use Noteless[1] on Android. And the tagging support is superb.

Because of the simple folder structure, you can also use vim+fzf to search/navigate your notes. The notational-fzf-vim plugin[2] is superb for that.

For web-clipping, I just use the markdownload[3] extension in firefox and save the markdown file in the notes folder.

Why not joplin? Mostly because joplin stores notes in an sqlite database instead of a simple folder structure making it not easily accessible by normal unix tools and editors.

Why not obsidian? Was never able to grok obsidian. In notable, I can tag a note as Books/CS, and CS/Books, and it'll show up in corresponding folder-like structures in the left panel.

0. https://notable.app/

Oh and the dev also did his own comparison table - you might like to compare it to yours!

I use https://notable.app/ for my notes, backup the notes / setup on a private github repo which I share with the Mac / Linux versions I use. Been working really well.

Notable (Mac, Windows, Linux) (flat)

JavaScript benchmarks are instruments for measuring the speed and effectiveness with which a JavaScript engine—such as the ones found in web browsers—can complete particular tasks. Benchmarks are used by developers and browser vendors to evaluate various engines, find places in the code where improvements are needed, and make sure JavaScript standards are being followed.

Strange then that frameworks advertise how fast they are at rendering, mutating, and creating objects in the DOM, and one of the main JS benchmarks everyone likes to measure their performance by is literally a benchmark about DOM manipulation: https://github.com/krausest/js-framework-benchmark

Oh wait. It's not strange. Because state manipulation is a largely solved problem, and even the least performant state manipulation is blazingly fast. However, presenting components in the browser's DOM is tens of magnitudes of orders less performant than anything you can throw at state manipulation.

And every single framework is busy solving one single problem: how do we touch the DOM as little as possible?

It literally says at the bottom "Data from https://krausest.github.io/js-framework-benchmark/"

The standard benchmark for js frameworks would be best: https://github.com/krausest/js-framework-benchmark