Re: [racket-users] Would it help to call racket2 something else?

2019-08-31 Thread evdubs
If "racket" is related to "scheme" by being an illegitimate scheme, I think "cartel" could be a good choice for "an even more illegitimate scheme". Plus, it's almost an anagram of racket. #lang cartel -- You received this message because you are subscribed to the Google Groups "Racket Users"

Re: [racket-users] Re: third-party package tips and developer concerns (Was: New version of file-watchers)

2019-08-31 Thread Sage Gerard
Thanks for the clarification, Neil! Your feedback does help a great deal. I'll also be happy to share updates with a respectful frequency now that I see the other replies. :) ~slg ‐‐‐ Original Message ‐‐‐ On Saturday, August 31, 2019 1:04 PM, Hendrik Boom wrote: > On Sat, Aug 31, 20

Re: [racket-users] Re: third-party package tips and developer concerns (Was: New version of file-watchers)

2019-08-31 Thread Hendrik Boom
On Sat, Aug 31, 2019 at 02:45:02PM +, Sage Gerard wrote: > I looked back and found my mistake: I only asked about blog posts and videos. > I'll refrain from version update posts here from now on. Whatever you originally asked for, I think this ensuing discussion about third-party packages is

Re: [racket-users] Re: third-party package tips and developer concerns (Was: New version of file-watchers)

2019-08-31 Thread Neil Van Dyke
Sage Gerard wrote on 8/31/19 10:38 AM: You probably don't want to be slowing yourself down with offering people previews of new versions, lead times for input, etc. I'm unknown in open source so I think all of us in Racket land are pretty much unknown in open source (outside of Racket/Scheme

[racket-users] [standard-fish] Update: small house facade, with attribute handling code

2019-08-31 Thread Hendrik Boom
Today's version, together with a new README.md file describing my longer-term intentions, rather than what the program dies right now. The code resides on a monotone repository on my server, which I hope to figure out how to make publically accessible. I haven't written a formal copyrght notice

Re: [racket-users] Re: third-party package tips and developer concerns (Was: New version of file-watchers)

2019-08-31 Thread Sage Gerard
I looked back and found my mistake: I only asked about blog posts and videos. I'll refrain from version update posts here from now on. ~slg ‐‐‐ Original Message ‐‐‐ On Saturday, August 31, 2019 10:38 AM, Sage Gerard wrote: > Hi Neil, and thanks for the helpful information and historic

[racket-users] Re: third-party package tips and developer concerns (Was: New version of file-watchers)

2019-08-31 Thread Sage Gerard
Hi Neil, and thanks for the helpful information and historical context. I do have some follow up questions if that's alright, because I want to make the most out of my time here and it seems like you can clarify that. > You probably don't want to be slowing yourself down with offering people >

[racket-users] third-party package tips and developer concerns (Was: New version of file-watchers)

2019-08-31 Thread Neil Van Dyke
First, to Sage, thank you for going to the work to open source third-party packages like this. Here are a few suggestions that came to mind from this post, which I'd like to mention to Racket third-party package developers in general. (Only suggestions, not presuming to tell anyone what to do;

Re: [racket-users] Persistent job queue

2019-08-31 Thread Bogdan Popa
> I haven't been able to find a persistent job queue for Racket, so I thought > I'd ask if one exists before writing a simple one. I did see Jay's job > queue package, but it doesn't appear to persist to disk, and that is a > requirement. FWIW, I am working on a new Redis client package[1] that

Re: [racket-users] New version of file-watchers

2019-08-31 Thread Stephen De Gabrielle
Awesome -thank you for releasing this. s. On Wed, Aug 28, 2019 at 11:30 PM Sage Gerard wrote: > Version 0.2 of the file monitoring package file-watchers is about to > drop. Here's a PR for public review. There are no contributors, so I plan > to merge in 48 hours if there is no feedback. Other