4 ms·
Personally, I don't like Go. I wish my projects needed Rust's speed, or its safety, or its engineering powers. But I don't. For simple parsing or number crunch
by greenhouse_gas 9y ago
Personally, I don't like Go. I wish my projects needed Rust's speed, or its safety, or its engineering powers.
But I don't. For simple parsing or number crunching, Go is just right.[1]
I find the fast prototyping, the wonderful IDE environment (VSCode, vim), and the community to be _so good_ that I don't need anything else.
There was a time I thought of learning Python[2] or Rust, but found both lacking.
[1]. Sure, I wish I was smart enough to get a job working on Quantum, working as a kernel dev, or in fintech where every nanosecond counts. But I'm not. The Rust community is great, there's a lot of help out there, and it seems like an amazing and cool language.
[2]. I tried it out a bit. My main issue is that it doesn't (didn't) have nearly as good of an IDE community (PyCharm is practically the only good IDE for Python, and in the bit of time I spent with it, I found it much less powerful than their Java IDE) revolving around it.
- didip 9y agoWhat part of Go you don’t like?
- greenhouse_gas 9y agosafety, immutability, lack of functional behavior, Algebraic data types. All the fun stuff.
- sp33der89 9y agoHave a look at Nim(https://nim-lang.org/ https://nim-lang.org/ ). It doesn't have great IDE support, but VSCode plugin works well enough and the language has a lot going for it. Edit: posting this because I'm in the same situation. I like Rust/Nim/Elixir but Go has a great productive ecosystem even though the language is quite "barebones".
- greenhouse_gas 9y agoI don't know about its IDE support, but it doesn't have as large of a community as Go.
- sidlls 9y agoI went from using primarily C++ to using primarily Python and now to doing some development in Rust. Rust is suitable for systems programming. Like C++, it's also suitable for application programming, which is what most development is. One need not be writing kernels to justify using Rust. At my job, for example, I'm slowly introducing bits of Rust here and there to do some data engineering. I wouldn't use it for high-performance numerical computations, but ergonomically it's almost as easy as Python (for me) and the safety, type, and other guarantees it provides make for a more robust pipeline.