Re: [racket-users] Pitching use of Racket at work?

2019-09-19 Thread Neil Van Dyke
Sage Gerard wrote on 9/19/19 10:47 AM: To add color: A prior supervisor said  "if it's famous, we should use it." [...] If you want to appear among the first results, just present your work using language that matches nothing else. If I could briefly return the favor of color, by connecting

Re: [racket-users] Pitching use of Racket at work?

2019-09-19 Thread Sage Gerard
> different tools tend to be considered unproven or inadequate. To add color: A prior supervisor said  "if it's famous, we should use it." Adoption is often confused with maturity. Corporate politics follows high school rules more than we'd like to admit. > there seems to be what has the

Re: [racket-users] Pitching use of Racket at work?

2019-09-19 Thread 'Richard Cleis' via users-redirect
> On Sep 18, 2019, at 12:25 PM, Sage Gerard wrote: > > This question is more for private-sector programmers in firms using > well-adopted technologies: How many of you tried to get your team to try > Racket at work for smaller tasks? What was their reaction? Three of them use it because they

Re: [racket-users] Pitching use of Racket at work?

2019-09-18 Thread Neil Van Dyke
I'll assert that Racket is currently for a subset of the people who are allowed to choose whatever tools they want: academics, hobbyists, people developing small tools for individual use (like sysadmins did with Perl), and... some startups.  Most organizations, you can't choose any tools you

[racket-users] Pitching use of Racket at work?

2019-09-18 Thread Sage Gerard
This question is more for private-sector programmers in firms using well-adopted technologies: How many of you tried to get your team to try Racket at work for smaller tasks? What was their reaction? I know there are not enough Racket programmers out there to justify many risks in maintaining