Go is not the new Ruby.
Ruby has keyword arguments and optional arguments with defaults.
Among [many] other things.
Go Is the New Ruby
21–30 of 61 posts
Re: Go Is the New Ruby
#22I don't really get the affinity of Go and Ruby. The most similar thing I could say about them both is that they're both not Java. This makes sense from a hiring sense, either your hiring from the large Jvm/.Net pools or you're not. I suppose both Ruby and Go have less steep learning curves compared to Java/Kotlin/Scala. I can't wait until Go v2 gets generics then I can use it like other statically-typed compiled, gc'…
The affinity for the author is in the last line,
"Go has become the new Ruby. A language I use to get things done, and enjoy programming again."
Good for him
Re: Go Is the New Ruby
#23Go really is the easiest language I've used. It installs with no fuss. The VSCode extension sets everything up and works perfectly. The library documentation is so clear that it usually answers any question I have without having to dig up blog posts and without dodging top search result Stack Overflow pages closed without answering the question. The highly opinionated nature means I can go into any Go code base and m…
Go is the new Java. It runs everywhere, is easy to learn and use and people who don't get it hate it with passion. Anyway, comparing go documentation with rust docs, I'm surprised anyone can get any work done with rust.
I'd say Go is more like Basic.
Re: Go Is the New Ruby
#24I kinda throught Elixir / Phoenix was the new Ruby / Rails. Nice read none the less.
Indeed. For scripting languages, it's usually Python people moving to go and Ruby people adopting Elixir.
Re: Go Is the New Ruby
#25Go really is the easiest language I've used. It installs with no fuss. The VSCode extension sets everything up and works perfectly. The library documentation is so clear that it usually answers any question I have without having to dig up blog posts and without dodging top search result Stack Overflow pages closed without answering the question. The highly opinionated nature means I can go into any Go code base and m…
Go is the new Java. It runs everywhere, is easy to learn and use and people who don't get it hate it with passion. Anyway, comparing go documentation with rust docs, I'm surprised anyone can get any work done with rust.
I’m a devout Go developer and I feel like this is accurate. It’s got some uglies (eg no generics, verbosity in general), but man, overall, it’s so pleasant to work with. Which is probably how great Java developers feel. Thanks for inspiring empathy!!!
Re: Go Is the New Ruby
#26A statically typed compiled systems language with anachronistic C semantics and a regressive package dependencies system is never going to be a new high level DSL oriented scripting language. A far better take is that Crystal is the new Go, because it mixes the benefits of a high level language with the benefits of a lower level language, and learned a lot more of the lessons from the ruby and node ecosystems about how to manage code dependencies.
Re: Go Is the New Ruby
#27A statically typed compiled systems language with anachronistic C semantics and a regressive package dependencies system is never going to be a new high level DSL oriented scripting language. A far better take is that Crystal is the new Go, because it mixes the benefits of a high level language with the benefits of a lower level language, and learned a lot more of the lessons from the ruby and node ecosystems about h…
I mean this to come of in a non antagonistic way, but did you read the article? You seem to be refuting the title of the article without addressing any of the points made within it.
Re: Go Is the New Ruby
#28> But, just like in Java, if I need speed, I can preallocate and reuse memory to avoid hitting the GC.
No, you can't. Language constructs in Go allocate in ways that are not immediately obvious. When the GC runs, it still has to scan all of that memory, regardless of whether you preallocated it or not, which is especially unfortunate with a non-generational garbage collector like that of Go.
Also, I have to say that I really don't get it when people say that they have to think about the borrow checker for a long time before writing a program in Rust. That's not the case for me or anyone else I know.
Re: Go Is the New Ruby
#29“All languages suck, but they all bring interesting concepts as well, that can overall make you a better programmer.” True on so many levels. Learning other languages means learning a new way of thinking due to the reasons those languages were created in the first place. Even if you never change the language you use daily, learning other languages and doing small projects in them will make you better in your “home” l…
Not true, There are lots of languages that bring absolutely nothing to the table in terms of making you a better programmer. Take something like Elm, it doesn't make you a "better programmer". It does make your program better by being statically typed. Kinda like typescript doesn't make you a better programmer than if you use javascript, but it makes your program better. You can say this for a lot of languages.
Uhm, Elm is a really bad example to pick, given how many other languages now have libraries that implement "the Elm architecture" for UIs of various sorts, while Elm itself is almost entirely a "please spit out some HTML" toolkit.
Re: Go Is the New Ruby
#30> But, just like in Java, if I need speed, I can preallocate and reuse memory to avoid hitting the GC. No, you can't. Language constructs in Go allocate in ways that are not immediately obvious. When the GC runs, it still has to scan all of that memory, regardless of whether you preallocated it or not, which is especially unfortunate with a non-generational garbage collector like that of Go. Also, I have to say that…
One possibly useful thing to know is that the Go GC doesn't scan non-pointer memory, so if you have big strings, byte arrays, or structs that don't contain pointers, they don't need to be scanned.
Also, while the garbage collector may not be generational, it's mostly concurrent. Looks like GC pauses are below 1ms now?