[racket-users] Re: Racket2 on a ubiquitous platform [was the case, and a proposal, for elegant syntax in #lang racket2]

2019-07-25 Thread Atlas Atlas
четверг, 25 июля 2019 г., 22:03:15 UTC+3 пользователь stewart mackenzie написал: > If you want to Racket2 popular make it easy for users to get the > programmer's responsive applications and programmers will come in > droves. Drop Chez, reimplement the Racket interpreter in Rust and > target i

[racket-users] a question related to bound-identifier=?

2019-07-25 Thread Yongming Shen
Hi there, Based on my understanding, (bound-identifier=? id-a id-b) only returns true if id-a would bind id-b AND id-b would bind id-a. Also based on my understanding, id-a will bind id-b doesn't imply that id-b will bind id-a. So, if I only want to check whether id-a will bind id-b, which func

Re: [racket-users] Re: The case, and a proposal, for elegant syntax in #lang racket2

2019-07-25 Thread Greg Hendershott
> I've taught the exact same material at the start of a 3rd year CS PL > course, and the students there didn't find the syntax as easy as one would > hope for students with that much CS “experience”. In fact, unsurprisingly, > many find the syntax as hard as expected for having trained on very > di

Re: [racket-users] on reducing barriers in the Racket community

2019-07-25 Thread Atlas Atlas
If we want more women, or any other group of people, involved in Racket, the only way to achieve this is to explain to this groups of people why do they need Racket. *(And openness and honesty is a great way to do it)* And try to answer this question for ourselves. What Racket can offer to this

Re: [racket-users] Racket2 on a ubiquitous platform [was the case, and a proposal, for elegant syntax in #lang racket2]

2019-07-25 Thread Neil Van Dyke
A lot of interesting ideas, stewart.  For now, I'll just highlight this one, and a few bulleted comments: stewart mackenzie wrote on 7/25/19 3:03 PM: If you want to Racket2 popular make it easy for users to get the programmer's responsive applications and programmers will come in droves. Drop

Re: [racket-users] on reducing barriers in the Racket community

2019-07-25 Thread Atlas Atlas
It is crucial to understand that "lowering barriers" can mean different even opposite things. You can lower barrier by helping someone to learn. And you can actually "lower barrier" by diminishing the goal. And when we talking about social interaction we must acknowledge that people a different

[racket-users] Racket2 on a ubiquitous platform [was the case, and a proposal, for elegant syntax in #lang racket2]

2019-07-25 Thread stewart mackenzie
I want expand on and make sure Maria's point doesn't get lost in that firestorm over at [the case, and a proposal, for elegant syntax in #lang racket2] . Maria is bang on the money imho (her email is copied below mine) JVM got popular because programmers didn't need to program C. Javascript and B

Re: [racket-users] Criteria for selecting Chez Scheme as the runtime for Racket

2019-07-25 Thread Brian Adkins
On Thursday, July 25, 2019 at 12:45:36 PM UTC-4, Matthew Flatt wrote: > > Reordered slightly: > > At Thu, 25 Jul 2019 09:04:29 -0700 (PDT), Brian Adkins wrote: > > I know Chez had a reputation for being a fast implementation - was > > performance the main criteria? > > [...] > > Were there oth

Re: [racket-users] on reducing barriers in the Racket community

2019-07-25 Thread Neil Van Dyke
Atlas, I will have to think more about your message, but I think you're right to suggest that FAANGs might be part of a problem.  For example, see yesterday's outreach email from a FAANG (quoted at end of this email), posted as an apparent diversity initiative, to students of a big-name CS depa

Re: [racket-users] on reducing barriers in the Racket community

2019-07-25 Thread Atlas Atlas
I never said that lowering barriers is lying or insulting. I say that lowering barriers by lying (by making an impression instead of a reality demonstration) is really bad way to go. If there is actual barriers, the work must be putted to improve on them, and not to improve on showing that thi

Re: [racket-users] on reducing barriers in the Racket community

2019-07-25 Thread Matthew Butterick
Mr. Atlas, since this seems to be only your second contribution to the racket-users list (the first was yesterday) I'm reluctant to impute much weight to your views, since I can't verify that there's a sincere human behind them. In any case, I can agree with you on the value of education. But t

Re: [racket-users] Criteria for selecting Chez Scheme as the runtime for Racket

2019-07-25 Thread Matthew Flatt
Reordered slightly: At Thu, 25 Jul 2019 09:04:29 -0700 (PDT), Brian Adkins wrote: > I know Chez had a reputation for being a fast implementation - was > performance the main criteria? > [...] > Were there other factors, in addition to > performance, that uniquely qualified Chez? Good performan

[racket-users] Criteria for selecting Chez Scheme as the runtime for Racket

2019-07-25 Thread Brian Adkins
I'm curious about the process that resulted in selecting Chez Scheme as the runtime for Racket. I know Chez had a reputation for being a fast implementation - was performance the main criteria? Were other Scheme implementations considered & rejected? If so, why? Were there other factors, in ad

Re: [racket-users] Re: The case, and a proposal, for elegant syntax in #lang racket2

2019-07-25 Thread Alexander Shopov
To whoever will implement a new syntax forRacket, may I give the following resources. I really hope they are widely known and I am just stating the obvious common knowledge. There have been previous attempts of using an alternative syntax: * M-expresisons - dating to the original McCarthy Lisp pa

Re: [racket-users] on reducing barriers in the Racket community

2019-07-25 Thread Atlas Atlas
1. To increase inclusiveness of some group of people, you educate people from this group on the subject of lisp racket computer science etc. 2. By lowering "barriers" you just welcome someone who doesn't care for the project and ruining community from inside. 3. By making a show about what projec

[racket-users] Re: The elegance of tail-nesting recursive syntax

2019-07-25 Thread rocketnia
On Wednesday, July 24, 2019 at 7:46:11 PM UTC-7, Hendrik Boom wrote: > > Too bad we have to use #/ instead of / in ordinary Racket because / is > already used for division. There are a lot more #/'s then divisions in > a typical Racket program. > > Redefining div to mean division isn't a real