@jgeddes has joined the channel
@jerome.martin.dev has joined the channel
@zacromero3 has joined the channel
There is another interesting video https://www.youtube.com/watch?v=R3zEOsh8AnQ
I think that right approach for racket2 design is think in terms of neuroscience and cognitive science. The things whats really mater is consistency, in style, in naming, in logic.
Another important thing is right balance in abstraction levels.
Very important thing is correlation in mental model, code syntax, and code semantics.
This is another reason against infix notation and C like syntax, we made lisp look like C but semantic remains the same - this will create huge problem of code understanding. And this is the major problem for people who learning how to write programs, they struggling with infix notation a lot already, C like syntax is a mess, and introducing it to lisp language will create untold problems with understanding.
Lisp is great for representing time flow, it doesn’t mess with code execution order, so this is strong side that must be used in advantageous way.
The weak side is data structures representation, relation between data, etc, this is where things can improve. Introduction of typed racket is good in this sense. Because it allows to create bounds between functions and data.
> I do think that many users seriously underestimate our commitment to backwards compatibility.
I do believe this is a non future. Even big companies with a lot of money failing on this kind of stuff. Splitting forces for small community is a general bad idea.
Python Rust Go and others have the experience of drastically change things and going to wide adoption and overall success nevertheless or exactly because of this changes.
I don’t think that this is mostly technical problems, they a conceptual. And solving conceptual problems is something entirely different. You need to have conceptual answers for this king of things. And right questions.
What is project goals are? Is racket2 closest to this goals that racket1? How do long term support for racket1 in this regards relates to this goals? Etc etc.
Regarding the backwards compatibility- the core team has a lot of experience in this AND have an excellent track record on backwards compatibility.