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 the above two: At one interdisciplinary lab, the stated tenure criteria was "be famous in your field", and one of the dominant strategies was... name a new field (and you'd automatically be famous in it). :)
Now, by "our own boats and airplanes" Are you referring to Racket2?
I was thinking instead that we haven't built much startups (boats/airplanes), ourselves. Rather than almost cargo-culting, figuratively in the original sense of the term, to try to get other people to bring their boat/airplane of goodies here.
Early on, there was one really positive public-sector-ish Web data science startup, that a couple of superhumanly-productive PhD ancient astronauts managed to build (which I think wouldn't have been doable initially, had they not used a Lisp, and one of them happened to choose Scheme), and which I understand has been able to keep evolving, over the years. There's currently a few smaller Racket-using startups emerging, and maybe some of them will have experience report writeups on HN, and be considered successes in that tough audience. And of course, we have core Racket itself, which in many ways is a successful startup.
I don't suspect that things I've seen mentioned about Racket2 will have any net effect on adoption by other startups. I'd like to see Honu tried for some things, maybe starting with dogfooding it for HtDP. And Honu might incidentally, also be part of a larger DSL solution (e.g., alternative way, to the boring lex&yacc-like modules, as a better way to make some non-sexp DSLs for non-developer domain experts). But I'd stick with leaving `#lang racket/base` as the canonical language for developers, and let people build upon that the things they find they need -- for core's research/teaching, and third-parties' work and hobby projects.
I hope we didn't lose any additional people/projects, over the recent commotion and uncertainty, besides what we already sadly know about.
Today, I *don't* recommend that people ask "What do we need to attract other developers?", but rather, "Do I want to do a startup/project, and if so, should I use Racket, and then what do I have to do, to launch my own minimum-viable-product, and then later grow it?"
My own top-level requirements are to do things that benefit society, do technically/craft-wise rewarding programming/engineering/research, have some sense of community/collaboration with good people, and make good money. (Money, so that I can continue to live in my HCOLA town, and focus my energy on the first three things.) The next levels of my requirements might well involve Racket, and so might also involve contributing requirements like other people doing startups that use Racket. We have yet to see what are the top-level and supporting requirements that will drive core Racket, and then individual people and organizations can try to see how that fits with their own respective requirements graphs.
-- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/ea874c46-7930-2955-4450-717dd9e6d2b8%40neilvandyke.org.
