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't like knowing the truth.
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't like knowing the truth.
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
> You even have a complete analysis for each request, that you can open with one click:
Do I get the queries generated for the request and time it took for them? And the time it took for the templates to be rendered?
Werkzeug debugger and flask-debug-toolbar are my baseline for debugging toolbars. They don't try to be everything and give me everything I need.
> You guys would be amazed if you tried frameworks like Symfony (instead of discarding PHP for not being beautiful or whatever)
Helpful exception logs and inline repls are one of n things to take into consideration. This alone isn't going to buy any converts.
At the end of day, they are convenience tools. It's not like I can't debug code or profile db requests without them. If I can get an inline context aware repl, superb. If not, good old breakpoints are mighty fine.
In saying that, the PHP LANGUAGE has some pretty glaring and terrifying warts, a fact that Rasmus doesn't try to hide.
I came to Rails from Symfony and there are definitely things I miss. Rails is way better overall, but there are loads of little things that were fantastically useful.