How do I make Rails not suck?

I finally got a summer software development internship.
I'm lucky to get this, as I don't even have my AS yet.
I'm stoked, but the issue is that I'm a C, C++, and ASM programmer at heart, and have been since early high school.
The internship is for a decent-sized company as a Ruby on Rails developer.
Ruby is...okay. I can live with it. But I find Rails mind-numbingly retarded. I've been learning it, and it just seems so ugly, inflexible, and sandboxed. Hell, just read this statement directly from the documentation:
[quote]
Rails is opinionated software. It makes the assumption that there is a “best” way to do things, and it’s designed to encourage that way – and in some cases to discourage alternatives. If you learn “The Rails Way” you’ll probably discover a tremendous increase in productivity. If you persist in bringing old habits from other languages to your Rails development, and trying to use patterns you learned elsewhere, you may have a less happy experience.
[/quote]

Basically, it’s built to restrict and control the developer. Rails’ name is very apt, as it keeps you directly on the track it wants you on, and gives you no power to truly deviate. I understand the MVC Architecture, but it appears almost dictatorial in enforcing its specific interpretation of MVC.

How can I make this less unpleasant? Using Rails right now is about as pleasant as pulling my own teeth out.

Damn, I'm still not used to the text boards, so I fucked up on the quote.
Still.

>>2
Yeah you're a fucking retard fuck off back to /g/.

Yeah, Ruby on Rails is fast becoming the new PHP. As a CS student in Silicon Valley, it's hard to find a job that's not run by trendwhore Macfags who don't know that better frameworks exist. The great thing about being a Django consultant, however, is that although the jobs are more scarce, the pay is better because the developers are more scarce.

I understand the MVC Architecture, but it appears almost dictatorial in enforcing its specific interpretation of MVC.
I think you don't really understand MVC. It is a way of structuring the system so that you can focus on and isolate the various concerns of the system. If you really wanted to mix the concerns of the system, you may as well forego the use of MVC structure.

The rails system is intended as a high level system, not a low level system. You're not really supposed to do much low level design work when you use this system.

so use some light weight thing instead (like sinatra or whatever) "mounted" inside the rails app (so you can still access its models)

http://boards.4chan.org/jp/res/8644544

>>7
Back to the imageboards !