skrger

4 ms·

1. 1.▲
   by skrger 13y ago

   It's very hard to impossible to really judge based on these short examples but I can totally relate to both of you. E.g. if you see a feature that seems to be free in terms of coding it is very hard to resist offering it. If you do tha
2. 2.▲
   Printing Drones by the Sheet (video)(twylah.com)

   3 points by skrger 14y ago|0 comments
3. 3.▲
   Interview about the raid (for running a TOR node)(raided4tor.cryto.net)

   1 points by skrger 14y ago|0 comments
4. 4.▲
   All-Female Species Survives by Stealing DNA of Other Animals(geekosystem.com)

   3 points by skrger 14y ago|0 comments
5. 5.▲
   Curiosity may be tainted with Earth microbes(articles.latimes.com)

   1 points by skrger 14y ago|0 comments
6. 6.▲
   DataTables for Twitter Bootstrap 2(datatables.net)

   3 points by skrger 14y ago|0 comments
7. 7.▲
   by skrger 14y ago

   Well it is a deliberate choice, calling it a feature may still be a stretch. The log becomes unreadable because if you have many Rails instances (Like 25 unicorn workers in my case) writing unbuffered in one log file it becomes a holy mess.
8. 8.▲
   by skrger 14y ago

   I think you have to add some code flushing the BufferedLogger after each request to really get the old behavior. But this is not my point, for me rails has been about sane defaults - this is what makes it fun to start and easy to work with.
9. 9.▲
   Rails 3.2 feature: unreadable production logs(github.com)

   54 points by skrger 14y ago|34 comments