You want to find your "tax" related things. Each time you create something, you put it in the "tax" directory. The same with photos: you organize them once in the input stage or periodically, and then you can search for them easily later on.
For text, if the content of the file is what is relevant, grep/ripgrep are your friends.
File type/name, find/fd are your friends.
Date of creation? A combination of ls and find.
For image, video and sound it is more difficult (impossible?) to search by content.
File names and directories are simple, and it works as well as you make it work; it does not matter the type or content of the file.
Something that comes to mind as a "problem" is that popular DBs are not designed to manage this (at least I do not think so), so you can have a DB and violate the principle of only appending, and the DB will let you.
And how difficult is it to migrate to this model or away? Although this is the same "problem" with any model, I suppose.
> Notice that in all cases time spent sleeping or otherwise waiting shouldn’t be counted, though you probably shouldn’t do that in your code in the first place.
I thought the time your CPU waits around doing nothing is something you want to measure.
If your algorithm has better "mathematical" scaling with big N but is worse in real world scenarios, it "failed".
Why are all images just wrong? Text superimposed with shapes, random shapes in random places, and a clock with the 12 in the center instead of in the 12 position.
You see the complaints; people rarely praise a product; they just use it.
An IDE is a tool. What do you want to use the tool for? Put that as a priority and say no to everything else.
If the IDE is for you, look at the other editors and pick and choose each thing they do and decide how (or if) you want to do it. Are you happy with the result? That is a win. If somebody comes along with ideas/complaints, tell them no.
I pity people that pay for a service and get ads anyway.
I do not know what is wrong with ads; only two or three times ever did I saw an ad and though "uh that is nice" and went to search for the product, mostly they all look like scams.
But since so much money moves through it, I suppose they work.
From the outside I see (do not write manually managed memory).
C/C++, you SHOULD do X to prevent certain bugs.
Rust, you MUST do X to prevent certain bugs.
Humans are lazy, error-prone, unskilled, etc. When I decide to get to a more low-level language, I will choose the language that forces me to good behavior.
You want to find your "tax" related things. Each time you create something, you put it in the "tax" directory. The same with photos: you organize them once in the input stage or periodically, and then you can search for them easily later on.
For text, if the content of the file is what is relevant, grep/ripgrep are your friends.
File type/name, find/fd are your friends.
Date of creation? A combination of ls and find.
For image, video and sound it is more difficult (impossible?) to search by content.
File names and directories are simple, and it works as well as you make it work; it does not matter the type or content of the file.