Re: [racket-dev] new package system collections and conflicts

2014-12-03 Thread Jay McCarthy
Your frustration is understandable given the lack of charity I've shown in this thread. I apologize and promise to try to be better. I know I'm repeating myself annoyingly, but I think the most productive way to move forward is if you could identify problems that you're trying to solve where the

Re: [racket-dev] new package system collections and conflicts

2014-12-03 Thread Neil Van Dyke
I don't think I need charity. I thought the vision for the new package system had already been explained adequately. I would be very interested to learn how the model is well-suited to third-party developers like me. But -- I mean this constructively -- I'd be happy if someone simply came

Re: [racket-dev] new package system collections and conflicts

2014-12-03 Thread Robby Findler
I think there is perhaps a misunderstanding. The design of the pkg system is (partly) driven by the observations the core team has about what gives us special privilege and then working to lift those restrictions so we don't need to operate under that special privilege. And I'll note that this

Re: [racket-dev] new package system collections and conflicts

2014-12-03 Thread Matthias Felleisen
Thanks for being with with us for so long. I think you misunderstood the word 'charity' here and perhaps Jay could have used a different, a more appropriate word than 'charity', which I now realize can have a negative connotation. Otherwise, I think that the package system design is about

Re: [racket-dev] Line editing in the default REPL

2014-12-03 Thread Leif Andersen
My goal was not to replace xrepl, but to provide basic line editing support to the default repl without licensing violations or massively increasing the distribution size. If you're talking about implementing line editing yourself, then my personal reaction to that would be wonderful, but doing

Re: [racket-dev] Line editing in the default REPL

2014-12-03 Thread Eli Barzilay
On Wed, Dec 3, 2014 at 2:45 PM, Leif Andersen l...@leifandersen.net wrote: My goal was not to replace xrepl, but to provide basic line editing support to the default repl without licensing violations or massively increasing the distribution size. Yes, that's exactly what I was talking about.

Re: [racket-dev] Line editing in the default REPL

2014-12-03 Thread Sam Tobin-Hochstadt
On Wed, Dec 3, 2014 at 6:10 PM, Eli Barzilay e...@barzilay.org wrote: If you're talking about implementing line editing yourself, then my personal reaction to that would be wonderful, but doing it properly is something that is difficult and easy to underestimate I've already done this

Re: [racket-dev] Line editing in the default REPL

2014-12-03 Thread Eli Barzilay
On Wed, Dec 3, 2014 at 6:22 PM, Sam Tobin-Hochstadt sa...@cs.indiana.edu wrote: On Wed, Dec 3, 2014 at 6:10 PM, Eli Barzilay e...@barzilay.org wrote: If you're talking about implementing line editing yourself, then my personal reaction to that would be wonderful, but doing it properly is