nicercat · HackerTrans

ah, but the path less trodden has its own rewards. The purity of the command line, the sparsity of it all it, unpolluted by decadent convenience-cruft, is satisfying in itself. Approach the heart of the machine!

nicercat

10 anni fadiscuss

actually, while the idiom seems initially appealing that feestyle guitar would more closely resemble using the (superficially analogue) mouse than using a (clearly digital) keyboard, actually the opposite is true. That is because the mouse is limited to a small selection of prescribed onscreen choices, whereas the keyboard, while still being a digital medium (unlike the freestyle guitar - on that I agree), has a much, much wider palette of expressiveness thanks to the inevitably orders-of-magnitude greater combination of command combinations of which it is capable.

nicercat

10 anni fadiscuss

but you don't have to save it to view it under the command line.

  > plot(rnorm(100))

is not going to give you anything different under R-Studio, than command-line R, other than redirecting the identical output into a convenience window in its IDE. Sure R-Studio will save a history for you and throw a few conveniences at you but, command-line >plot(rnorm(100)) will popup a window on all OS versions of R and you'll be able to visualize all day long. Including multiple open charts. With selectable focus for further manipulation. R-Studio (MS-VS-RStudio) is just a very thin wrapper on something which is 100% there already. However, in return for nominal initial friendliness, it has the downside of sleepwalking you into a workflow which, if you don't understand what's going on underneath, will hold back your R learning curve.

Now IDEs are useful, if you understand the tradeoffs. They're a higher-level wrapper on stuff, with all the pluses and minuses that that entails. Higher-level = lower learning curve, greater immediate productivity, vs lower-level = higher learning curve, lower immediate productivity but greater long term power.

comments