Yes, the dynamic parts of the Tarsnap website are written in C.
Ask HN: Which stack do you use at your startup?
11–20 of 128 posts
Re: Ask HN: Which stack do you use at your startup?
#12We use Elixir, Go, C++ for backend and JS, Java / Kotlin, C# for frontend. We also use Postgresql, Rabbitmq and Redis.
Re: Ask HN: Which stack do you use at your startup?
#13Nothing special, but it gets the job done.
Re: Ask HN: Which stack do you use at your startup?
#14C on FreeBSD on EC2. Yes, the dynamic parts of the Tarsnap website are written in C.
Re: Ask HN: Which stack do you use at your startup?
#15Rails monolith, jQuery for some user interaction (new features are starting to use Vue.js). Hosting on Linode. Capistrano for deployments. Nothing special, but it gets the job done.
Re: Ask HN: Which stack do you use at your startup?
#16C on FreeBSD on EC2. Yes, the dynamic parts of the Tarsnap website are written in C.
Just deployed a lambda script that spins up a FreeBSD ec2 image that checks out, compiles, and runs the contents of a dynamically provided git url, with dynamically specified pkg and pip dependencies to make my own long-running FreeBSD-based lambda-esque service for some continuous deployment.
Wouldn’t have been possible without the ec2 images and the configinit magic.
-mqudsi@neosmart
Re: Ask HN: Which stack do you use at your startup?
#17Re: Ask HN: Which stack do you use at your startup?
#18Re: Ask HN: Which stack do you use at your startup?
#19Re: Ask HN: Which stack do you use at your startup?
#20C on FreeBSD on EC2. Yes, the dynamic parts of the Tarsnap website are written in C.
Thanks for your work on the ec2 AMIs. Just deployed a lambda script that spins up a FreeBSD ec2 image that checks out, compiles, and runs the contents of a dynamically provided git url, with dynamically specified pkg and pip dependencies to make my own long-running FreeBSD-based lambda-esque service for some continuous deployment. Wouldn’t have been possible without the ec2 images and the configinit magic. -mqudsi@ne…