Top all-time · #10406
Fullstory Blog
Company blog · bionic.fullstory.comprogrammingsystems
Fullstory Blog is the company blog at bionic.fullstory.com, writing about programming and systems. Since 2020, 7 different Hacker News readers have linked it 14 times, most often “Rust at Fullstory”. It is still writing: the last post was on 2026-09-29, and you can follow it by feed.
Too few sampled comments (3) to say how often HN recommends it.?
Why HN links it
Linked on HN for its series on how the company uses Rust in its mobile SDK, including its language evaluation. Commenters cite the series and the product, with no judgement of the writing.
Summarised by Claude from a sample of 3 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Fullstory is your digital experience analytics platform for on-the-fly funnels, pixel-perfect replay, custom events, heat maps, advanced search, Dev Tools, and more.
Most-linked posts?
- Rust at Fullstory3 people · 3 mentions · first linked 2020-04-14
- Show HN: FullStory – Private-by-Default Mobile Analytics2 people · 2 mentions · first linked 2020-03-31
What Hacker News says?
Thanks for the feedback! You're right that describing our usage a bit better might have helped clarify our thinking. For the record: the FullStory product is a session record and replay tool for both web and mobile. We record details about how your users interact with your site or app and you can watch replays of them as well as get analytics across sessions. Privacy is important to us, which you can read about here…
Comment linking /private-by-default-mobile-analytics/
on “How we use Rust in our mobile SDK”Submitted How we use Rust in our mobile SDK as a story · 204 points
HN discussionFrom the previous article in the series: > Our problem is further complicated by the fact that we’re not shipping an app but a framework for others to use in their own apps. We have to be mindful of the impact our technology choices have on our customers, such as the potential for harmful interactions with their code, and user-visible performance impact in terms of CPU and memory usage. https://bionic.fullstory.com/…
Comment linking /rust-at-fullstory-part-1/
on “How we use Rust in our mobile SDK”Submitted Is Go Duck-Typed? as a story · 110 points
HN discussion> Sounds like they could have had the same things with a much easier language like Nim. Unless they are using a lot of Rust exclusive features? We didn't consider Nim in our language eval ( https://bionic.fullstory.com/rust-at-fullstory-part-1/ ), but you could insert it into the scoring sheet to see how it might fare if we were evaluating it ( https://language-compare.glitch.me/ ). I would be very interested in see…
Comment linking /rust-at-fullstory-part-1/
on “How we use Rust in our mobile SDK”Submitted Show HN: FullStory – Private-by-Default Mobile Analytics as a story · 74 points
HN discussionSubmitted Rust at Fullstory as a story · 14 points
HN discussionSubmitted How We Tamed GitHub Codeowners with Bots as a story · 4 points
HN discussionSubmitted Why You Should Be Using Errgroup.WithContext() in Your Golang Server Handlers as a story · 4 points
HN discussionSubmitted GRPCui: Don’t gRPC Without It as a story · 3 points
HN discussionSubmitted Writing a Filebeat Plugin as a story · 2 points
HN discussionSubmitted The Power of Discriminated Unions and Exhaustiveness Checking in Typescript as a story · 1 points
HN discussionSubmitted Fighting the Long Tail: Improving Latencies for the Queries That Matter the Most as a story · 1 points
HN discussionSubmitted App Frameworks: A Story of Transparency and Time Travel as a story · 1 points
HN discussion