#important-announcements

YouTube Interview Discussion and Q&A on Typesense

TLDR Jason thanks Zaiste for a YouTube interview. Martin commends them and asks about potential use of Rust for Typesense. Jason explains why they choose C/C++ over Rust.

Powered by Struct AI
+13
grinning2
heart1
8
22mo
Solved
Join the chat
Nov 23, 2021 (22 months ago)
Jason
Photo of md5-8813087cccc512313602b6d9f9ece19f
Jason
07:47 PM
Zaiste Thank you for having me on your YouTube channel! This was a fun conversation! https://www.youtube.com/watch?v=QNLA8RCrYwk

We talked about Typesense, the state of search, our bootstrapped journey and my personal journey leading up to Typesense.
+12
heart1
Zaiste
Photo of md5-b12c0749a9dbaefc03cb5817250a595d
Zaiste
08:19 PM
The pleasure is mine! My head is spinning with ideas 🙂
grinning1
Nov 26, 2021 (22 months ago)
Martin
Photo of md5-4c44d17869045701f2ca4035972ad4c5
Martin
03:02 PM
Thanks Jason and Zaiste for a super interesting interview touching on many topics. I liked for example the part about open core, bootstrapping and VC funding.
+11
03:05
Martin
03:05 PM
Jason if you allow one follow up question: you talked a lot about languages, and your pragmatic approach to them. Would Rust also be a possibility for Typesense?
Jason
Photo of md5-8813087cccc512313602b6d9f9ece19f
Jason
05:37 PM
Martin Great question! Rust wasn’t too popular back in 2015 when we started on Typesense. But even if it was or even today, I’d say the lack of enough battle-tested community libraries would have caused us to build our own and with that comes long development cycles, and long lead times for those pieces to mature.

For eg: we would have had to write our own Raft library which is one thing to build but a whole other thing to run at scale, debug and ensure correctness of distributed systems. In the C/C++ ecosystem in contrast, teams have already built, battle tested and opensourced libraries for Raft, http, etc. So we’re able to stand on the shoulders of giants and we get to focus on the key pieces pieces for Typesense which is search.
Martin
Photo of md5-4c44d17869045701f2ca4035972ad4c5
Martin
05:43 PM
Thanks a lot for the answer Jason, makes a lot of sense. I also sensed from the interview that you don’t mind working “close to metal” to squeeze optimal performance out of Typesense. And nice contrast to many things you frequently hear in today’s world of “buzzword driven development”.
grinning1
05:43
Martin
05:43 PM
Happy Thanksgiving.
Jason
Photo of md5-8813087cccc512313602b6d9f9ece19f
Jason
05:45 PM
Happy Thanksgiving!