@tslumley Went through the same considerations eons ago with LispStat. Ended up with nonlinear models inheriting from linear in order to pick up things like diagnostics.
@henrikbengtsson@jimhester_ @tslumley @ekuber @Thoughtfulnz Nobody is suggesting removing that.
But neither python nor julia tell you how to get out in their startup messages, and that's OK: for both an end of file (^D) does the job, which the generic terminal REPL quit. And that works in R too.
@jimhester_ @tslumley @ekuber @Thoughtfulnz In any case, the startup message would most likely have scrolled off the screen at the point where 'type this' information would be useful. An IDE with a help menu that is always visible and provides this information would be more useful.
@jimhester_ @tslumley @ekuber @Thoughtfulnz One could argue that having a larger startup message that python, as R and Julia both do, might make it slightly more likely that a user would notice and look, but I doubt it.
@jimhester_ @tslumley @ekuber @Thoughtfulnz Unfortunately we live in a world where most system startup messages are not very useful so we've been pretty much conditioned to ignore the lot.
@sid_mnnit@kategchalmers Using vectorized operations, if that is possible, will give the best performance. But rewriting a loop in terms of vectorized operations is not always easy.
@sid_mnnit@kategchalmers In principle, apply function calls could more easily be optimized to perform better, but this currently doesn't happen. Once you are used to them, using apply functions can produce cleaner code and simplify debugging.