Same story as the others: I happened to be looking at my oc tags and wonder “owo what’s this?”
And hey-ho there I am!
Doing searches like this seems very performant (not that derpi isn’t already pretty quick). What is the cost of having to send the index for this with the page load to the browser, though?
@byte[]
Honestly I wasn’t considering porting a/part db engine/lookup system using Clang or Emscriptem. I stand corrected, and I tip my hat in non lazy porting considering a few tags deep would be good enough for most I think.
Nice to see this, if this is a local index that s can use, that would be really cool and save some server processing I would hazard.
I would hope an optimized local build script would come, but alas, everything must be web based saddness.
Also comment on the performance – only two dictionary filter steps and it’s all computed dictionary lookup which is what V8 optimizes on. Not really an issue. Plus, javascript is trying to be a system language – if it couldn’t handle the best case scenario for data >>2635299, I don’t think node.js would be as prevalent as it is right now
Lol i was looking at my artist tag too find some of my art i needed and was like “What’s this?” lol
It’s pretty cool! I liked watching to see which of my things were in there. Honestly, it ended up being a design I’m really proud of. Cool that it’s in there.
Delivering the index is too much, which is why this is impractical. Would be great for server side usage though.
Derpi had me logged out… Oops.
Honestly I wasn’t considering porting a/part db engine/lookup system using Clang or Emscriptem. I stand corrected, and I tip my hat in non lazy porting considering a few tags deep would be good enough for most I think.
There is some more commentary here, as well as a link to the demonstration: https://liamwhite.github.io/cbtree.html
Edited
your current filter.