colexdev: DuckDuckGo is good at finding a quick, simple answer. It's mostly Bing. https://duckduckgo.com/duckduckgo-help-pages/results/sources/ Mojeek is a janky, small project that's been ongoing for several years. It's a genuinely unique search index. It's bad at giving simple answers, and good at sharing obscure ones.
You may have your big file split into separate files every now and again automatically. Guessing that you continue your file at the top, you may have a shell script such as: "limit=9999; lines=$(wc -l mybigfile); if [ $lines -gt $limit ]; then head -$(($lines / 2)) mybigfile > 2024-04-23.chunk; tail -$(($lines / 2)) > /tmp/a; mv /tmp/a mybigfile; fi"
I hear what you're saying, but in practical terms my "big" text file isn't nearly big enough for that to be an issue (it's still under a MB). Thanks to wear-leveling, you would have to seriously stress-test a drive for that to become an issue, though I always back-up and would split up a file if it ever got really big.
On the anecdotal side, I've known people who have used larger OBTFs for years with zero issue. Plenty of notetaking software programs like JRNL use single text files too w/o problems, so I'm not too worried tbh. Thanks anyway, though.
Forgotten drawings.