It would be awesome to have this in Rails 4 by default.
Better Rails errors
21–30 of 50 posts
Re: Better Rails errors
#22It would be awesome to have this in Rails 4 by default.
A bit late now, but 4.1 could get a campaign for this.
Re: Better Rails errors
#23This was always something of a killer feature for me in Python, and one of the reasons I use Flask a lot. Good to see Rails support for in-browser debugging, it's a super convenient workflow to never have to go back to the terminal, just alt-tab from editor to browser.
Your workflow may be good, I don't mean to judge that. But is not the rails way to be in the shell, rails console and editor at all times? Instead of trying things out in the browser you have automated testing doing that for you?
Why would you ever want to make a web app without constantly testing it in a browser?
Re: Better Rails errors
#24You guys would be amazed if you tried frameworks like Symfony (instead of discarding PHP for not being beautiful or whatever). It has always had these features, and in Symfony2 it only got more awesome. You even have a complete analysis for each request, that you can open with one click: https://s3.amazonaws.com/i.imm.io/OvjX.jpeg https://s3.amazonaws.com/i.imm.io/Ovk9.jpeg Edit: Being downvoted. Some people just don…
This isn't a specific draw to PHP, for example several Python frameworks have some flavor of 'debug toolbar' which does the same. Nice feature if you do use PHP otherwise, though.
The downvotes may be partly because you are using an article about a specific Ruby project as a jumping off point to promote another language, which is slightly obnoxious - make a thread for your new PHP stuff you are interested in, people who are happily using Ruby don't need to be exhorted to use other languages for no specific reason
Re: Better Rails errors
#25Re: Better Rails errors
#26Earlier quoted context omitted.
Your workflow may be good, I don't mean to judge that. But is not the rails way to be in the shell, rails console and editor at all times? Instead of trying things out in the browser you have automated testing doing that for you?
Why would you ever want to make a web app without constantly testing it in a browser?
If you've got a decent test suite, it's much faster to leave the browser out of the loop, especially when you're refactoring stuff under the hood.
Re: Better Rails errors
#27Re: Better Rails errors
#28I'm a complete rails newbie. I've added 'better_errors' into my Gemfile, started my server/also with Pow and yet I see the same errors as before?
Re: Better Rails errors
#29Only one comment: WOW!
Re: Better Rails errors
#30You guys would be amazed if you tried frameworks like Symfony (instead of discarding PHP for not being beautiful or whatever). It has always had these features, and in Symfony2 it only got more awesome. You even have a complete analysis for each request, that you can open with one click: https://s3.amazonaws.com/i.imm.io/OvjX.jpeg https://s3.amazonaws.com/i.imm.io/Ovk9.jpeg Edit: Being downvoted. Some people just don…
You're being downvoted because your comment (or any comment in the style of 'but Y does this already!') adds no value to the discussion.