News for hackers. Stuff that matters.
Re:Why We Chose Rails to Build Gitlab by rapind on Tuesday January 22, 2019 @05:15PM (#18973149)
Or Elixir, or Rust, or Node. Having spent time with all of these options, Rails is still really really good for a lot of use cases. Go comes nowhere near Ruby's readability for me (but I like the lack of surprise).

Personally I'd love something typed, performant, and as readable as Ruby with a convention focused platform like Rails. Elixir + Phoenix is probably the closest I can find, but not a perfect fit. Maybe close enough though.

Re:Why We Chose Rails to Build Gitlab by Legogris on Tuesday January 22, 2019 @05:31PM (#18973284)
If we're talking memory usage, I don't think Node is necessarily a significant improvement over Ruby.
Re:Why We Chose Rails to Build Gitlab by dmlittle on Tuesday January 22, 2019 @05:22PM (#18973203)
FWIW Elixir isn't necessarily lightweight. Memory will stay pretty flat (even during high workloads) but it's not lightweight.
Re:Why We Chose Rails to Build Gitlab by jamescostian on Tuesday January 22, 2019 @05:43PM (#18973397)
> Go comes nowhere near Ruby's readability for me

I am not fluent in either, and I'm not looking to change that, but I have read code in both. I feel the exact opposite way, and I'm not trying to start a war or anything, but I was wondering if you'd be open to talking about what things in Go you find hard to read (and what things in Ruby you find very easy to read). Or is this about libraries (are Go libraries providing lower-level APIs than Ruby ones?)? Or have you read/written a lot more code in Ruby than Go?

Re:Why We Chose Rails to Build Gitlab by hazz99 on Tuesday January 22, 2019 @07:00PM (#18974217)
I agree - Go has issues, but they're not related to readability. Perhaps if you include "familiarity with the standard interfaces" (like using io.Reader) which is different to other languages, and took a while for me to get used to.
Re:Why We Chose Rails to Build Gitlab by hazz99 on Tuesday January 22, 2019 @05:40PM (#18973369)
Is there a benefit learning Elixir over Erlang? I've working a little bit with Erlang, and I've wondered if its worth the jump.
Re:Why We Chose Rails to Build Gitlab by knrz on Tuesday January 22, 2019 @07:17PM (#18974360)
Completely! With convention and macros, it's a whole new language.
Re:Why We Chose Rails to Build Gitlab by anonyfox on Tuesday January 22, 2019 @05:35PM (#18973316)
Crystal it is. Combined with the amber framework, porting the Ruby Code should be straightforward. Yes stuff isnt even 1.0 yet, but I would seriously bet on it right now.