Launched this week
TCalc.it
The calculator that actually understands time
10 followers
The calculator that actually understands time
10 followers
TCalc.it parses almost any time format — just type how you think about time: "2h 30m + 45m" → 3h 15m · "14:30 to 16:45" → 2h 15m · "22:00 to 6:00" → 8h (overnight) · "NOW + 90d" → deadline date · "01:00:00:12f24" → SMPTE timecode · "1737100000UNIX" → readable date. Type-safe: knows durations vs dates, so you never get nonsense. 15+ formats: decimal hours, FPS timecodes, ISO 8601. 6 modes for HR, film, dev, logistics & accounting. PWA with cloud sync. Android out now, iOS soon.
PreFlight
The natural language parsing is genuinely impressive, especially picking up on stuff like "2h 30m" and SMPTE timecodes without me having to pick a mode first. One thing I'd love is a quick "difference between two times" calc built right in, so I could type something like "14:30 to 16:45" and just get the duration without doing the mental math or switching modes.
PreFlight
@mira146251 Thank you, that's exactly the reaction I was hoping for when building the parser! 🙌
You can actually get the duration today — just type it as a subtraction: 16:45 - 14:30 and you'll get 2h 15m back, no mode switching needed. The calculator figures out that subtracting two times should give a duration.
That said, I really like the idea of parsing 14:30 to 16:45, it reads much more naturally than subtraction, so I'm adding it to the parser.
Thanks for the great suggestion!
PreFlight
@mira146251 Update: it's live! 🚀 14:30 to 16:45 now works exactly as you suggested.
the SMPTE timecode parsing is a really thoughtful detail, most tools just ignore anyone working in film or broadcast frames. love that it can tell a duration from a date without making you pick first.
PreFlight
Thanks @kamilsatlkebkj! Film and broadcast folks were a big reason I built this - timecodes usually get treated as an afterthought, so I wanted them to be first-class: 24/30fps, a configurable default fps, and full timecode math ("01:23:45:12f24 + 250f" just works).
The type-safe approach to distinguishing durations from dates is a smart call, saves people from those "wait, why is it giving me a year" moments. Really clean way to handle something most time tools mangle.
PreFlight
Thanks @pekxyi5! The type system was one of the first design decisions. Under the hood, every value is either a duration, a date, or a number, so adding two dates just errors out instead of spitting nonsense. Took a while to get right, but I think it pays off.
honestly the SMPTE and FPS timecode support is what got me, super useful for video work. typing "1.5 hours" and just getting the decimal hour output feels way faster than doing the math myself.
PreFlight
@bulemgggg Thank you! Video work was a huge motivator for the SMPTE support, so this is exactly what I hoped to hear. 🎬