3 ms·

Hey Steve, great of you to ask! Here are some suggestions: * Streamline the command line. Why rake to migrate, but rails to generate a migration? I know, I kno

Hey Steve, great of you to ask! Here are some suggestions: * Streamline the command line. Why rake to migrate, but rails to generate a migration? I know, I know. But new folks to Rails do not know. And it would be better if there was just one tool that does it all. * Get rid of the global magic functions. users_path is nice and sweet, but where is it defined? Object? Kernel? Why can't I just call a method on my app. Sort of like how engines work: main_app.users_path is IMO better than users_path. * I guess instance variables in views are a given forever, but I still don't like them. Why can't these be simple methods on objects as well? Simplify, simplify, simplify. Also, deprecate helpers. (Hey, I can dream!) * I would help if my app was defined as a (singleton) class that I can see and use somewhere. It would be better if this were always a Gem, without me doing anything special. Then I could make all kinds of gem dependencies explicit. * Fix mailers to allow them to work with async delivery out of the box. (Bringing back queues? Yes please!) * Make mailers work with Markdown and friends to produce multipart emails out of the box. Write a pretty(ish) plaintext mail, and get HTML formatted for free. (There are gems for this, it would be nice if it were standard) * Get rid of all hardcoded tokens in source code. Especially the session secret. Require dotenv gem and move all config into ENV. Including the database configuration! * Fix the log file format. One line per event would be nice. Proper timestamps would be nice. Use standard Ruby loggers with a good format that the rest of the industry understands.

sytse 13y ago
Love the command line, queue, dotenv and log format suggestions.
steveklabnik 13y ago
* the tension between 'rails' and 'rake' has always been there, and I see it trip up beginners. There is a gem that sorta does this, I'll give this some thought. * Making apps no longer a singleton has been happening on master already, so expect to see a bunch of that. * I like multipart emails too, since I prefer plaintext emails. * Working on the tokens issue, I already commented about it elsewhere in this thread. * As of Rails 4, you can slip in your own Logger, so this is pretty easy to customize if we don't change anything. * Queues were explicitly brought back to 4.1, that's a feature that we (and I, maintaining Resque) really want to get in. Thanks! <3
- sytse 13y ago
  Yey for bringing queues back!
- grey-area 13y ago
  Queues were explicitly brought back to 4.1 Hurray!
tibbon 13y ago
I agree a LOT with the dotenv-rails suggestion. Not having it in there by default sets up users to put variables in their initializers, and then check them into Git.
meerita 13y ago
As a newbie on Rails (I'm designer, don't kill me) i have to agree with point 1. After some couple of days practicing migrations and generators, it doesn't become a problem.
mtarnovan 13y ago
Get rid of all hardcoded tokens in source code. Especially the session secret. Require dotenv gem and move all config into ENV. Including the database configuration! Better yet, make it as 12factor compliant as possible, out of the box.

sytse 13y ago

Love the command line, queue, dotenv and log format suggestions.

steveklabnik 13y ago

* the tension between 'rails' and 'rake' has always been there, and I see it trip up beginners. There is a gem that sorta does this, I'll give this some thought. * Making apps no longer a singleton has been happening on master already, so expect to see a bunch of that. * I like multipart emails too, since I prefer plaintext emails. * Working on the tokens issue, I already commented about it elsewhere in this thread. * As of Rails 4, you can slip in your own Logger, so this is pretty easy to customize if we don't change anything. * Queues were explicitly brought back to 4.1, that's a feature that we (and I, maintaining Resque) really want to get in. Thanks! <3

sytse 13y ago
Yey for bringing queues back!
grey-area 13y ago
Queues were explicitly brought back to 4.1 Hurray!

tibbon 13y ago

I agree a LOT with the dotenv-rails suggestion. Not having it in there by default sets up users to put variables in their initializers, and then check them into Git.

meerita 13y ago

As a newbie on Rails (I'm designer, don't kill me) i have to agree with point 1. After some couple of days practicing migrations and generators, it doesn't become a problem.

mtarnovan 13y ago

Get rid of all hardcoded tokens in source code. Especially the session secret. Require dotenv gem and move all config into ENV. Including the database configuration! Better yet, make it as 12factor compliant as possible, out of the box.