3 ms·

What do you mean? Rails seems to come with authentication, session management, cookie management, an ORM, extensive logging capabilities and a bunch of other th

by WA 2y ago

What do you mean? Rails seems to come with authentication, session management, cookie management, an ORM, extensive logging capabilities and a bunch of other things. Go and Kotlin are languages, not frameworks, and they certainly don't include these things. So what are you comparing exactly?

neonsunset 2y ago
My initial comment lists two great options that make choosing Rails an unconditionally short-sighted decision.
- wiseowise 2y ago
  ASP.NET - maybe, but you’ve got to be kidding if you suggest Vert.x to be a replacement for RoR. They operate on completely different levels of abstraction (even ignoring nightmare of Reactive code you have to write using Vert.x).
  - p2detar 2y ago
    Not a nightmare at all, if you know what you’re doing. There’s a learning curve indeed, I’ll give you that.
  - neonsunset 2y ago
    Maybe my impression on Vert.X was misplaced. Trying it out left me off with "Oh, so kind of like ANC minimal API with Rx.NET but faster". I should revisit this, thank you. JVM ecosystem has other great frameworks like Active-J and Ktor. My main point is, unless that's what you're most productive in, RoR is a really poor choice for both small and large codebases and there are plenty of options that completely eliminate the classes of issues you would otherwise have to spend the time on. Sure, I like using C# (and recently F#) a lot but it wouldn't kill me if I had to use Kotlin/Java/Go/Swift instead. All these have understandable tradeoffs and merits to them. On the other hand, my experience of interacting with advocates of Python, Ruby and Erlang is incredibly poor - it's impossible to have a technical conversation and it seems that their communities live in a bubble of belief that using interpreted junk comes with magical productivity advantages inaccessible to expressive modern compiled languages with rich type systems and excelled back-end frameworks/libraries.

by WA 2y ago

neonsunset 2y ago

My initial comment lists two great options that make choosing Rails an unconditionally short-sighted decision.

wiseowise 2y ago
ASP.NET - maybe, but you’ve got to be kidding if you suggest Vert.x to be a replacement for RoR. They operate on completely different levels of abstraction (even ignoring nightmare of Reactive code you have to write using Vert.x).
- p2detar 2y ago
  Not a nightmare at all, if you know what you’re doing. There’s a learning curve indeed, I’ll give you that.
- neonsunset 2y ago
  Maybe my impression on Vert.X was misplaced. Trying it out left me off with "Oh, so kind of like ANC minimal API with Rx.NET but faster". I should revisit this, thank you. JVM ecosystem has other great frameworks like Active-J and Ktor. My main point is, unless that's what you're most productive in, RoR is a really poor choice for both small and large codebases and there are plenty of options that completely eliminate the classes of issues you would otherwise have to spend the time on. Sure, I like using C# (and recently F#) a lot but it wouldn't kill me if I had to use Kotlin/Java/Go/Swift instead. All these have understandable tradeoffs and merits to them. On the other hand, my experience of interacting with advocates of Python, Ruby and Erlang is incredibly poor - it's impossible to have a technical conversation and it seems that their communities live in a bubble of belief that using interpreted junk comes with magical productivity advantages inaccessible to expressive modern compiled languages with rich type systems and excelled back-end frameworks/libraries.