3 ms·
We’ve been a pretty solid TS, C#, C and C# shop which was in the process of moving some TS and all of our C# to Go to make our language package smaller. Go was
by devjab 2y ago
We’ve been a pretty solid TS, C#, C and C# shop which was in the process of moving some TS and all of our C# to Go to make our language package smaller. Go was a good choice for us, it’s not better than C# in any way. Then we had some organisation wise changes in strategy, and now Python is our strategy. (Still with C (sometimes Zig), and TS in our single frontend. Anyway this meant I recently had to do my first work with Django and boy was that… well I guess it was my Ruby on Rails moment? It’s so productive… Sure, it’s setup like a Go project more than a Django project, we use Django apps more like Go modules and we’ve opted for ninja-Django for the API, so it’s not exactly Django. It’s still really easy to be productive with, however, and now I’m not sure why I haven’t crossed paths with it before.
That being said, it’s very easy to get into Go if you know Python. Especially coming from an opinionated framework like Django. In my experience the people who have the hardest time getting into go are Java/C# developers who don’t appreciate the core Go focus on simplicity and having absolutely no “magic”. Which is understandable. Getting into Go from Python is different because Python is terrible, so a lot of the opinionated simplicity will most likely make you wish Python had parts of it.
We did some PoCs with Rust to see if it was worth adopting instead of C. We found it wasn’t for us. I mentioned Zig, that is because of the interoperability with C, it’s not something we plan on fully adopting any time soon.
As far as “future proofing” goes, does it really matter? If you’ve been a developer for years you’ll easily be capable of picking up Go and Rust. Of the two I personally found Go a little more challenging to be effective with. It’s easier to get into, but getting concurrency right (not being a memory hog) wasn’t trivial for us in the beginning. You should also look at your local job market. I think PHP would be the best fit for a “mercenary” in my city. By comparison I don’t think there has been a single Rust job posting for a couple of years.