291 karma · joined August 30, 2020
It calculates optimal ways to load boxes into trucks or containers, considering stacking rules, fragility, and real-world constraints. You can drag boxes like 3D Tetris or upload photos to auto-estimate item dimensions. Recently added: batch-wise guided loading for warehouse use cases.
We're at ~$400 MRR and just opened up a 14-day free trial. Feedback, trials, and intros to logistics folks welcome.
Scrolling is about scroll snapping feature.
The API came about the same way. Currently, there’s just one active API user: a company from Sri Lanka that built a Unity WASM interface on top of it.
I coded the algorithm completely from scratch, with no external inspiration and fun fact, it’s written in F# using functional programming. There are a lot of immutable lists floating around. Honestly, I probably wouldn’t have been able to write it without functional programming (even though it’s notoriously slow for this kind of problem). The immutability allowed me to focus on individual parts of the app without worrying about side effects.
That said, how it works and how fast it works still feels like magic to me, just like any meta-heuristic algorithm applied to combinatorial problems.
And thanks for the feedback! I knew the Blog link was broken after I redid the landing page, but I didn’t notice the duplicated API Response Structure section. I’ll definitely fix that. Though part of me thinks, “Should I really bother?”
Also, thanks for catching the audio/subtitle issues. I was aware of both, but I figured it wouldn’t make much difference at this stage. Maybe that attitude explains my low traction… who knows? Either way, I appreciate you taking the time to point these out!
I have spent countless months on the algorithm earlier. It improved from trash to something commercially reasonable gradually, it was more like getting stuck for a while then getting small break throughs.
My biggest mistake was changing my domain perhaps. Earlier it was bindrake.com Then I added 3d pack.ing and due to complexity of canonical pages google kicked me out.
Ironically recently I get contacted by a client and they said “you don’t exist on google but we found you from ChatGPT”
Here's a rust ray tracer compiled to web assembly written in F#
https://ncave.github.io/fable-raytracer/
source: https://github.com/ncave/fable-raytracer?tab=readme-ov-file
LLM driven 3d packing written in F#
- There is a certain level uncertainty about where these pcs will land. Yes perhaps stockfish could try to add all possible future placements but I expect that would significantly hinder stockfish as the the number of possibilities grow hundreds of times.
Your opponent doesn’t know which piece will be where until you reveal it. Therefore can’t attack a non defended pawn on b column because you may reveal a castle on next turn.
On the overall it mitigates problems of weird openings in regular chess 960 but End game stays the same.
Because of the hidden information and forced reveals, computer algorithms struggle with planning moves, making the game a true test of human intuition. Give it a try