51–60 of 82 posts
I have written non-trivial code in Rust and Go. The thing about Rust is that it needs a bit of perseverance and experience of writing a bit of non-trivial code in Rust to really appreciate it. Writing tutorial like code won't cut it. Life-cycle of a Rust developer: https://imgur.com/kNkV7jm Good, bad and the ugly: https://imgur.com/udNcZXa With Go, in my head it is best explained in terms of the scene in the movie: P…
Earlier quoted context omitted.
Maybe I can try to chime in: Go is not an OOP language, you get the dot notation on structs and that's pretty much it. Rust is all about advanced OOP and very fussy static type checking. That said, IMHO, Go to me feels more like a replacement for Node more than a replacement for C.
> That said, IMHO, Go to me feels more like a replacement for Node more than a replacement for C. Except the first release of node was May 2009 and the first announcement of golang November 2009. Node was also first showcased in November 2009. So for me golang cannot be seen as a replacement for node just from chronological order. Also their design goals at the time seems very different.
That, at least for me, feels not as much the "obvious" choice for C programs.
I have written non-trivial code in Rust and Go. The thing about Rust is that it needs a bit of perseverance and experience of writing a bit of non-trivial code in Rust to really appreciate it. Writing tutorial like code won't cut it. Life-cycle of a Rust developer: https://imgur.com/kNkV7jm Good, bad and the ugly: https://imgur.com/udNcZXa With Go, in my head it is best explained in terms of the scene in the movie: P…
What does "error management story" refer to in the second pic?
Now there is a failure crate https://github.com/withoutboats/failure. It is an improvement, but it still feels that one has to type a lot for something basic. Now, this is a matter of taste and many people will be ok with this.
I have written non-trivial code in Rust and Go. The thing about Rust is that it needs a bit of perseverance and experience of writing a bit of non-trivial code in Rust to really appreciate it. Writing tutorial like code won't cut it. Life-cycle of a Rust developer: https://imgur.com/kNkV7jm Good, bad and the ugly: https://imgur.com/udNcZXa With Go, in my head it is best explained in terms of the scene in the movie: P…
I recently started using Go for a bunch of small services a new product needed. I was amazed at how easy and fast it is to get up to a point of high productivity in Go. The language is really straight-forward to begin working in. Probably the most fun I've had learning a new tool in many years.
Your thoughts as revealed by the question fall into a pattern I recognize from when I was younger, where I used to think (for example) 6 months was like this eternity, and (for another example) what I was gonna major in was super important because it would define my life for 40 years. Ha ha, I should've been so lucky! Or rather, unlucky, because reality is much more interesting. The reality is, in 10 years you'll be learning something else entirely, and when you've been at this game a while, you start to lose count of the languages and paradigms you've learned. You get so you can pick up a language in a couple of weeks, or a weekend. Each one of them is worth it, for the things you learn along the way, and the ways it teaches you to think. Any rock is sufficient for sharpening your knife.
Rust is harder to learn but solves some harder problems and arguably you'll learn more valuable concepts as a result.
Think of Go as a better Python and Rust as a better C. Which type of programming do you do more? Rust is harder to learn but solves some harder problems and arguably you'll learn more valuable concepts as a result.
In what sense is Go a "better Python"? My impression of Go is that it (by design) is extremely minimalistic, leading to simple, verbose code, that is understandable by the lowest common denominator, allowing large scale collaboration. And also it has good concurrency.
Back then Perl had a huge traction, mostly from sysadmins. Python got traction from web backend, and systems (redhat used to have a good python conde for starting-up servers).
I think both Rust and Go will coexist un different industries/use cases.
IMHO the killer app/use for GO are lambdas/cloud functions because they are cheaper to execute than python.
For Rust, I expect to see someday a unikernel that boots an app into a VM/light container.
I think if you find what level of programming interests you, the tools will follow from that.