Maybe the result of some short sighted AB testing. I hate that to but I have to admit that I tend to close the tab as fast as possible seeing some prices that don’t correlate with the „amount of benefits“ at that concrete moment. So they try to bind you as long as possible to raise that amount through the „good price“ threshold.
Pricing information is the first thing I look for, and if I don't find it I assume it's nowhere near reasonable and close the tab.
Back to the topic of the post, I like the idea and it's definitely a good addition to the standard sqlite docs which can be a little dry/dense in places. It'd be nice if we had some sort of inline DB-browser type view too so we could see what the commands we run actually did without resorting to writing select statements before and after the example. Also not sure why I have to click 'show' to see the command syntax.
