On Thu, Oct 12, 2017 at 2:27 PM Andrew Gwozdziewycz <apg...@gmail.com> wrote:
> I love seeing all of these project ideas, but I really don't think > Racket needs a "killer app." I think what it needs is the people > passionate about it building tools in it, and *using* those tools in > the work place, and sharing the experiences of using those tools more > vocally. > This line of reasoning also works in reverse. When Racket becomes more popular, people will talk about it more. There's a network effect to consider. > We need people building tools and blogging about why using Racket made > the job easier. Why would it be harder to do in Python, or Ruby? We > need straight up advocacy, and that starts with everyone in this > thread who *hasn't* done that yet. > These activities are good for hardcore developer advocacy. They are less effective at swaying casual devs who can't code themselves out of a jam. You might get some push back on [...]. Explain to them [...] > Education is important. It's also slow and expensive. In my experience, "lead by example" is a more effective starting strategy than "show them the light." Anyway. I don't think it makes sense to solve problems that you don't > have. I've made a career out of solving other people's problems. It's why I'm an expert tool maker and an awful astrophysicist. Programmers and astrophysicists need each other to remain relevant. Ideas are cheap, but it's an easy way to get people taking. And this kind of discussion can lead to truly valuable insights as we share interests, hopes, pain points, and coping mechanisms. Eric -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
