4 ms·
Lol I thought the appeal of rails was that it is “simple and boring”! Congrats on having the gumption to do a rewrite. I’m curious what are the more detailed
by binarymax 4y ago
Lol I thought the appeal of rails was that it is “simple and boring”!
Congrats on having the gumption to do a rewrite. I’m curious what are the more detailed decisions you took to better future proof?
Given how often things shift in our world, I feel like anything I choose now will just end up being obsolete and annoying to maintain in a 5+ year timeframe.
- nullbytesmatter 4y agoGreat question-- and may be worth a detailed/thought out blog post some day! To future proof the service I wanted to use tech that was based on the fundamentals. This boiled down to no special tooling, no special build process, etc. Furthermore I cut out all dependencies I could. I got my third party dependencies down to two (postgres + nginx). Practically speaking this meant: no node, no yarn, no ruby, no webpack, no sidekiq, no redis, etc. The entire service is now Nginx, Postgres and a single binary that has html/css/js/assets embedded inside of it. The entire product is a single Go binary that connects to postgres-- that's it. I could probably do without Nginx, but it has been nice for a variety of reasons and has never given me a headache. My tech/decisions may not be for everyone (that is why I didn't share them initially) but it works incredibly well for me and most products I build.
- binarymax 4y agoThanks for the reply! Would enjoy a blog post. I'm guilty of embedding HTML inside of a Rust binary, but it was more do fix an immediate dependency hassle and never thought about it as a long term solution...but maybe it's not such a crazy idea after all.