Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Announcing RStudio v1.0

blog.rstudio.org

Post reply on HN
Print view View original

51–60 of 68 posts

Re: Announcing RStudio v1.0

#51

Post by semi-extrinsic »

StefanKarpinski wrote: post #30
statics2245 wrote: post #28

For all the naysayers... Try installing python/jupyter in a corporate environment. It was a no go from the start at the last 4 companies I have worked at. R and RStudio just installed and worked for 3 of the 4 companies. The 4th required a tweak to one environmental variable and everything installed/worked after that. Corporate IT restrictions can make or break software.

The flip side is that RStudio is AGPL [1] – although not too surprisingly this is not heavily advertised. It may be easy to setup, but your legal department will have a heart attack if they find out that you're using it. At some point, RStudio will ask you to comply with the AGPL or pay them for a non-AGPL license. [1] https://en.wikipedia.org/wiki/Affero_General_Public_License

I'm not sure I follow why AGPL for the IDE you're using is a big problem? Surely the IDE license does not affect the license of code written in the IDE?

Re: Announcing RStudio v1.0

#52

Post by StefanKarpinski »

jcheng wrote: post #40
StefanKarpinski wrote: post #30

Earlier quoted context omitted.

The flip side is that RStudio is AGPL [1] – although not too surprisingly this is not heavily advertised. It may be easy to setup, but your legal department will have a heart attack if they find out that you're using it. At some point, RStudio will ask you to comply with the AGPL or pay them for a non-AGPL license. [1] https://en.wikipedia.org/wiki/Affero_General_Public_License

We're proud to be AGPL. The AGPL license is pretty clearly stated on both the product page and the download page. We were an AGPL licensed project years before we were a "real" company, because we thought that for server-oriented software (RStudio was originally conceived to be server only), it was the license most aligned with the principles of the R project. It's certainly not our intention to deceive and then subm…

That's a fair reason for the AGPL license choice for RStudio. It is a product-like software project after all. My experience with corporate legal is that they are much more wary of GPL software than strictly necessary – hence the warning about AGPL since ease of use != ease of permission. (We've had JuliaBox fire-walled from a few big banks, albeit not for license reasons, but because they don't want private data on the cloud, so it's a familiar issue.) I had a hard time finding any mention of the AGPL on the RStudio site, including some broken links.

Congrats on the release! RStudio pushes the envelope on very many data analytics UI features. Excellent work.

Re: Announcing RStudio v1.0

#53

Post by jbmorgado »

raizinho wrote: post #42
jbmorgado wrote: post #18

Earlier quoted context omitted.

I was trying Rodeo these past few days. It still has a lot to improve, I really don't think the autor should have put this out of beta so fast, it's clearly still a 0.x version, not a 2.x. Markdown is extremely limited (what we need is something more like knitr), there are quite a few bugs and it's difficult to access documentation of the packages. I appreciate the work of the author, but all in all, it's nowhere nea…

There something close to knitr for Python: https://github.com/pystitch/stitch

This is great thank you.

It would be great if Spyder would add a plugin to edit these formats or something similar.

Re: Announcing RStudio v1.0

#54

Post by aheilbut »

blahi wrote: post #5
gshulegaard wrote: post #4

Earlier quoted context omitted.

Funny, many people say this, but iPython notebooks have been around for a while (now called Jupyter Notebooks since they are not Python specific anymore) and it didn't spur a massive migration to Python...at least as far as I can tell. Not a bad thing, it's just R Notebooks kind of seem like old news to me. Addendum: I looked it up and it appears that Jupyter Notebooks actually have an R kernel ( https://irkernel.git…

Yeah but jupyter leaves bad taste in the mouth. Very frustrating to debug, binary file (no git/diff), much harder to layout than RMarkdown, no variable explorer. Additionally, the kernel idea is kind of lame/not implemented well. And you are getting nowhere in the data world without proper R support. There wasn't migration to python because there's a total lack of anything to migrate to in python. It has only textboo…

I'm curious why you view the jupyter kernel idea to be not implemented well?

Re: Announcing RStudio v1.0

#55

Post by 0x001E84EE »

semi-extrinsic wrote: post #51
StefanKarpinski wrote: post #30

Earlier quoted context omitted.

The flip side is that RStudio is AGPL [1] – although not too surprisingly this is not heavily advertised. It may be easy to setup, but your legal department will have a heart attack if they find out that you're using it. At some point, RStudio will ask you to comply with the AGPL or pay them for a non-AGPL license. [1] https://en.wikipedia.org/wiki/Affero_General_Public_License

I'm not sure I follow why AGPL for the IDE you're using is a big problem? Surely the IDE license does not affect the license of code written in the IDE?

> Surely the IDE license does not affect the license of code written in the IDE?

Agreed. However, the R programming language and many of its libraries are GPL licensed.

Can someone elaborate how R can be legally used in to develop proprietary or commercial software? RStudio's website [1] lists all of this large companies that apparently use R.

[1]: https://www.rstudio.com/

Re: Announcing RStudio v1.0

#56

Post by yihui »

StefanKarpinski wrote: post #52
jcheng wrote: post #40

Earlier quoted context omitted.

We're proud to be AGPL. The AGPL license is pretty clearly stated on both the product page and the download page. We were an AGPL licensed project years before we were a "real" company, because we thought that for server-oriented software (RStudio was originally conceived to be server only), it was the license most aligned with the principles of the R project. It's certainly not our intention to deceive and then subm…

That's a fair reason for the AGPL license choice for RStudio. It is a product-like software project after all. My experience with corporate legal is that they are much more wary of GPL software than strictly necessary – hence the warning about AGPL since ease of use != ease of permission. (We've had JuliaBox fire-walled from a few big banks, albeit not for license reasons, but because they don't want private data on…

Just for the record, if you follow the Download RStudio link on the RStudio homepage, or go to Products -> RStudio, you will see the license clearly mentioned before you try to download RStudio. AGPL is also displayed in our Github repository if anybody cares about looking at the source repository: https://github.com/rstudio/rstudio So I don't know why it was so hard for you to find the mention of AGPL...

Re: Announcing RStudio v1.0

#57

Post by blahi »

aheilbut wrote: post #54
blahi wrote: post #5

Earlier quoted context omitted.

Yeah but jupyter leaves bad taste in the mouth. Very frustrating to debug, binary file (no git/diff), much harder to layout than RMarkdown, no variable explorer. Additionally, the kernel idea is kind of lame/not implemented well. And you are getting nowhere in the data world without proper R support. There wasn't migration to python because there's a total lack of anything to migrate to in python. It has only textboo…

I'm curious why you view the jupyter kernel idea to be not implemented well?

Because it breaks all the time for some esoteric (but always different than the previous) reason.

Re: Announcing RStudio v1.0

#58

Post by jmcphers »

0x001E84EE wrote: post #55
semi-extrinsic wrote: post #51

Earlier quoted context omitted.

I'm not sure I follow why AGPL for the IDE you're using is a big problem? Surely the IDE license does not affect the license of code written in the IDE?

> Surely the IDE license does not affect the license of code written in the IDE? Agreed. However, the R programming language and many of its libraries are GPL licensed. Can someone elaborate how R can be legally used in to develop proprietary or commercial software? RStudio's website [1] lists all of this large companies that apparently use R. [1]: https://www.rstudio.com/

It's no problem to use GPL software to develop commercial software. If it were the vast majority of software would be open source as some of the most popular compiler toolchains are primarily or wholly open source.

What you cannot do, however, is modify GPL software, as you're then creating a derivative work which must legally also bear the GPL license.

Re: Announcing RStudio v1.0

#59

Post by progman »

capnrefsmmat wrote: post #17

I've been co-teaching a class in computing for statisticians this semester (some details on the previous iteration here https://www.refsmmat.com/posts/2016-01-22-stat-computing.htm... ) and have mixed feelings about RStudio. Most of our students use RStudio for their work. It's convenient and easy. For developing standalone scripts or functions, rather than notebooks or R Markdown files, the typical workflow is to wr…

In Common Lisp you could take a snapshot of the current session with "save-image". Doesn't Racket provide something like that?

http://stackoverflow.com/questions/480083/what-is-a-lisp-ima...

Re: Announcing RStudio v1.0

#60

Post by ccordoba12 »

jbmorgado wrote: post #19
anc84 wrote: post #13

Earlier quoted context omitted.

What are you missing in Spyder compared to RStudio?

Markdown/Knitr is one of the biggest points. A modern interface would also be nice. And native support for Vim (I know there is a plugin but it's quite limited).

(Spyder maintainer here) What do you mean by a modern interface?
Post reply on HN