261 karma · joined November 22, 2010
And really its by definition not a tail call when you have to run destructors after a "tail" call, and tricky/annoying to express that destructors should be run prior to a tail call.
Also, I'm really interested in the debug-ability of Chicken. Instead of a stacktrace, which sort of captures "where you're going", a stacktrace in Chicken captures "how you got here", which in conjunction with using immutable data structures would make the most absolutely amazing blob of data to be sent back by a customer - you could potentially restart execution with their data and step thru.
RR crops still boost demand for roundup and clones, competing on brand is a valid and proven strategy, and you can still sell RR(tm) branded seeds that you guarantee are roundup ready at perhaps a lower markup. And you can target your next herbicide immune crop at a patent protected herbicide.
I write PHP professionally. I like PHP programmers. I'm starting to have a soft spot for PHP. PHP and its standard library are a minefield.
This remark is rather parallel to "she shouldn't dress that way...". If doing something makes some people behave like creeps, its generally the fault of the creeps. And if the would be mystery man is prepping something, I'd rather he unveiled it than a cabal of creepers.
I think this is the business model devaluing the product. "the Atlantic" both in name and typography wants to evoke a newspaper, but the internet broke the model that allowed newspapers to do real journalism.
a) its a code review, not an author review
b) be respectful of your reviewer's time:
1. 200 lines is a big review obligation, 500 lines should be a hard maximum. Remember that boilerplate code does have meaning, and it counts. If you can't make time for reviews, then don't rubber stamp, just don't review.
2. Run whatever automation and analysis is available to you before submitting for review, and fix what it tells you to fix or note the trigger and document why its a false alarm.
3. You may count unit test code at 1/3 the normal rate, and even get 50 lines totally free. This relieves the burden of mentally running your code, and makes it easy to request additional test cases, which will be easier on your ego than bugs.
All the big problems people have with code reviews are about checking your ego, respecting your peers, and clear communication.
The problem of changes being to big ... is another instance where you're ignoring the results of the code review. "This change is too big for me to review effectively" is a 100% legitimate problem with a change. The change should get rejected on that basis alone.