[racket-users] Re: Message in the meantime?

2019-07-23 Thread Brian Adkins
On Tuesday, July 23, 2019 at 9:28:53 PM UTC-4, Alex Harsanyi wrote:
>
>
> On Wednesday, July 24, 2019 at 12:55:40 AM UTC+8, Greg Hendershott wrote:
>>
>> Although I'm still skeptical that changing the surface syntax will be a 
>> sufficiently big net gain, and ought to be the next, highest priority? 
>> I'm running with that idea for the following. 
>>
>
> I had a look at the proposals at 
> https://github.com/racket/racket2-rfcs/issues, and they seem reasonable 
> changes which, in my opinion, would improve the Racket language.  Most of 
> these changes, if they are implemented, would also allow a relatively easy 
> transition of existing Racket code.
>
> I can see only one proposal for changing the syntax and it is no more 
> radical than "#lang at-exp", which is already part of Racket, and seems to 
> be popular.
>
> On the other hand, anyone who is reading the posts on racket-users list, 
> would think that the Racket is a risky language to learn and use at this 
> time.  Perhaps it is time to stop the speculation and comment on the actual 
> proposals being made?
>
> Alex.
>

Alex:

Given that options being considered include converting official 
documentation over to the as-yet-to-be-defined new syntax and relegating 
#lang racket to a similar status as #lang mzscheme or #lang scheme, I don't 
think it's unreasonable to feel there is some risk as things stand 
*currently*. 

I expect more clarity to come which may reduce the risk, but it does seem 
like the majority of people who are downplaying the risk (or the perception 
of risk) are those in favor of the proposed changes. I suppose that's a 
natural response.

Brian 

-- 
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/56faf557-a627-4856-b030-effca5700fee%40googlegroups.com.


[racket-users] Re: Message in the meantime?

2019-07-23 Thread Alex Harsanyi

On Wednesday, July 24, 2019 at 12:55:40 AM UTC+8, Greg Hendershott wrote:
>
> Although I'm still skeptical that changing the surface syntax will be a 
> sufficiently big net gain, and ought to be the next, highest priority? 
> I'm running with that idea for the following. 
>

I had a look at the proposals at 
https://github.com/racket/racket2-rfcs/issues, and they seem reasonable 
changes which, in my opinion, would improve the Racket language.  Most of 
these changes, if they are implemented, would also allow a relatively easy 
transition of existing Racket code.

I can see only one proposal for changing the syntax and it is no more 
radical than "#lang at-exp", which is already part of Racket, and seems to 
be popular.

On the other hand, anyone who is reading the posts on racket-users list, 
would think that the Racket is a risky language to learn and use at this 
time.  Perhaps it is time to stop the speculation and comment on the actual 
proposals being made?

Alex.

-- 
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/3aea6a05-1c10-4b70-b942-88583080f43d%40googlegroups.com.


[racket-users] Re: Message in the meantime?

2019-07-23 Thread Brian Adkins
On Tuesday, July 23, 2019 at 12:55:40 PM UTC-4, Greg Hendershott wrote:
>
> Although I'm still skeptical that changing the surface syntax will be a 
> sufficiently big net gain, and ought to be the next, highest priority? 
> I'm running with that idea for the following. 
>
> It seems like there are at least two "flavors" or "strengths", of giving 
> Racket a non-sexpr syntax someday: 
>
> 1. The new syntax will be a choice, fully co-equal with sexprs. Both are 
>"first class", "forever". Any great new Racket features work with 
>either. 
>
> 2. The new syntax will become the preferred syntax, used in 
>documentation and advocacy. ("Change the culture" is the phrase I 
>thought Matthew used initially -- but I welcome him 
>clarifying/correcting/revising.) Sexprs and #lang racket will get a 
>status that's not as weak as "deprecated", but not really as strong 
>as co-equal with the new syntax. 
>

Option #1 is the only viable option from a community perspective. And I 
think it will demonstrate the value of language oriented programming more 
clearly.

I chose Racket for many reasons, but one important reason was that the age 
of the language allowed me to examine the history of how the community 
operated over a *long* period of time to get an idea of what I might expect 
in the future. I didn't even consider languages that I felt were too young.

If anything other than option #1 is our course of action, then any 
(current, or hypothetical future) users would be right in assuming the 
possibility that sometime later, the new official language might also be 
deprecated for something very different than what they expect. This is how 
*not* to build a community.

I'm sure people disagree with this line of reasoning, and I respect your 
different perspective, but hopefully we can all at least agree that 
expectation management is important, and that expectations a currently a 
bit muddled.

If the core team and/or community wants something other than option #1, I 
would much prefer to know sooner rather than later. It would make me sad, 
disappointed, frustrated, etc., but I suppose I would then reluctantly take 
a cue to consider Chez Scheme given it was chosen by Racket people I 
respect to be their foundation, just as I considered (and eventually chose) 
Racket, via PLT Scheme, when I discovered Paul Graham chose it for the 
foundation of Arc (after he abandoned his language community).

Brian
 

-- 
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/e286c725-0f3e-4a94-ab89-589667d0cf3b%40googlegroups.com.