2 ms·
Speaking only from a Scheme adoption perspective (which I don't think is the goal of the authors, but is relevant to some practitioners on HN)... One of the ba
by neilv 5y ago
Speaking only from a Scheme adoption perspective (which I don't think is the goal of the authors, but is relevant to some practitioners on HN)...
One of the barriers to adoption that Scheme faced at a crucial point in time seemed to be that many people had seen Scheme in an intro CS class, and thought it was just an academic toy language.
I don't think a Fisher Price makeover helps fix the "toy" optics. :)
- Zababa 5y agoThat's a good point. I had my first semester in Scheme, and while it was fun, the biggest project was a Sudoku solver with the sudoku directly in the program. We didn't even do file IO. On the other hand, we studied functional programming with Javascript while using it to build a webpage, something that was concrete. We learned domain and tuple relational calculus with SQL and PHP, and built a small website, again something concrete. We had the choice between logical and graphics programming. I took logical, where we did some Prolog, and solved a few enigmas with it. In the graphics programming, people used C++ with a library and made a cool 3D scene with trees, a river and a few objects. All of that was made without libraries (except for the C++ graphics stuff), so the usual "ecosystem problem" that plague small languages compared to the big ones wasn't even a problem here. But I still finished college with a clear divide between "language you use for work" and "language you use for research probably?". That was before knowing about package managment, frameworks and ecosystems. It's hard to not be biased after that.
- eatonphil 5y agoI don't think this is really the case. A quick search will show you a number of places Scheme is used in real software such as in gdb, gimp, etc. See also the work Cisco has supported in Chez Scheme. I don't think it will ever be as popular as Ruby, Python or JavaScript but it's a very simple language to implement and use as a scripting language so I see it continuing to be a reasonable choice in some environments.
- neilv 5y agoScheme is suited for more than just a scripting language. Production-grade implementations are difficult rather than easy. We've mostly failed at adoption that arguably was merited, including for the reason I mentioned. One sign of the failure became that, for years and years, advocates kept trotting out the same handful of adoption examples. Those examples started to get stale, and at some point sounded out of touch or desperate, like bragging about how we got on the junior varsity team in high school, still mentioning that well after high school. I worked on one of the relatively big success stories, and even I've given up on mentioning that example in most circumstances. BTW, Chez is great, and it's now being used for the Racket backend.
- eatonphil 5y agoNo disagreement about production-grade implementations, but most of the actual examples of use are proprietary and aging (exactly as you say). Whereas embedded Scheme just happens more frequently in major OSS so I find it less embarrassing to bring up, as you say.