HN user

ashishmax31

39 karma
Posts4
Comments19
View on HN

+1 to this. Especially with go, most of the (non-integration) tests I end up writing are behaviour driven tests. I'm not really sure how one can write these sort of tests without interfaces and mocks.

Blockchain Is Puny 5 years ago

I'm no expert in crypto. But how would people know that your public key belongs to "you" ?

I learned Go as my first statically typed language(Worked on ruby and some python before that). Although I missed the functional goodies from Ruby in Go, I thought that was the price I had to pay for performance and static checking guarantees.. Nevertheless, I enjoyed writing Go and its take on writing concurrent programs. As others have called it, I thought of Go as "modern C with garbage collection and first class concurrency primitives".

All this changed when I started learning Rust, man was I blown away by the language.. I never thought a statically typed language with manual memory management can feel so "scripting language" like.(Sure the borrow checker annoys you sometimes, nothing a `.clone()` can't fix when you are starting out). I truly enjoy writing Rust these days and never have I missed anything major from Ruby.

I'll be damned if I sit here and criticize Ken Thompson and Rob Pike, but I feel like in their quest to make Go "simple" they've perhaps held a little too hard on to their past.

tldr; Go feels a little too verbose and "dated" after learning rust.

Please can you elaborate on the objective measures of code quality part? Do you mean to use static analysis tools like code climate? Also, if you don't mind can you share some good reads/books which cover these topics? Thanks

Happy New Year HN 6 years ago

Happy new year to all the HNers, no place like this on the internet :) പുതുവത്സര ആശംസകൾ...