[revskill]

Ruby code is like poetry. Rails code is like a song.

Working with RoR always made you feel being like an artist, instead of being only a software developer.

RoR is always my inspiration on how to design a software from start to finish.

[theflyinghorse]

Perhaps I am an odd duck (I come from heavy Java backend experience including Spring and struts and now Go) but Rails feels incredibly clunky.

I am working on a mid-size Rails app and it's a total horror show. Setting up debugger alone was very difficult (had to locate just the right patch version of a ruby gem that would work with my app); I can't just follow the calls because things are wired together behind the scenes based on names and sometimes through delayed jobs. I can't just read code and understand what it's doing I have know Rails and a myriad of other tools (react on rails and such).

So far RoR has left a fairly unpleasant taste in my mouth.

[asark]

Having spent a lot of time on legacy Rails codebases that need new features and fixes, existing ones coming in from clients, and so on, I'd consider it practically write-only as soon as eyeballs are off it for a couple months or a handoff happens. Heroic testing practices that I rarely see in the wild could save it from that fate, but little else. Ruby's got some great libraries available but there's too much magic and "wtf is this even?" going on in your average Rails codebase. Sinatra with Sequel over it any day if it's my choice and the product's intended to have any kind of lifespan, and we're using Ruby.

[uurrnn]

I have barely any experience with Ruby or Rails, but I'm interested in your similies.

Could you link a repo that you feel represents this kinda mentality?