3 ms·

Judging from the red/blue colors in the logo and that the website was generated with Frog, I assume that once you feel too big for Pyret's shoes you'll discover

Judging from the red/blue colors in the logo and that the website was generated with Frog, I assume that once you feel too big for Pyret's shoes you'll discover that you've actually been using Racket all along and will start using the Racket language directly.

AstralStorm 10y ago
But why? Best languages are truly general. This should aim to replace Racket, not be bait for a switch.
- baldfat 10y ago
  Racket is both a programming language and a framework for building programming languages. http://queue.acm.org/detail.cfm?id=2068896 http://queue.acm.org/detail.cfm?id=2068896 Racket is the most fun I have had in Programming and the more I "get it" the more I enjoy it. I can't say that for any other language.
- davexunit 10y ago
  Racket is a platform for running many languages. It's different than the usual "one language for everything!" mantra. You can Pyret for one part of a program, Racket for another, Typed Racket for another, etc.
baldfat 10y ago
http://www.pyret.org/pyret-code/ http://www.pyret.org/pyret-code/ > One of the enduring lessons from the Racket project is that no full-blown, general-purpose programming language is particularly appropriate for introductory education. By the time a language grows to be useful for building large-scale systems, it tends to have accumulated too many warts, odd corners, and complex features, all of which trip up students. The journal paper for DrScheme (the old name for DrRacket) explains this in some detail. In that respect, the closest fellow travelers of us Pyreteers are the Racketeers (see how that works?). In fact, the first version of Pyret was merely a #lang in Racket. Nevertheless, Pyret represents a departure from Racket (for now and for the near future, at least) for several reasons:
skrishnamurthi 10y ago
Except note that Pyret is not implemented atop Racket. It used to be (a #lang) but that proved not suitable for our needs, so we built a very sophisticated run-time system on top of JavaScript. Pyret now compiles to JavaScript entirely in the browser (and Pyret's compiler is written in Pyret itself, so it's all bootstrapped goodness). That said, Racket is indeed a fantastic next language after Pyret. I myself constantly switch between the two.

AstralStorm 10y ago

But why? Best languages are truly general. This should aim to replace Racket, not be bait for a switch.

baldfat 10y ago
Racket is both a programming language and a framework for building programming languages. http://queue.acm.org/detail.cfm?id=2068896 http://queue.acm.org/detail.cfm?id=2068896 Racket is the most fun I have had in Programming and the more I "get it" the more I enjoy it. I can't say that for any other language.
davexunit 10y ago
Racket is a platform for running many languages. It's different than the usual "one language for everything!" mantra. You can Pyret for one part of a program, Racket for another, Typed Racket for another, etc.

baldfat 10y ago

http://www.pyret.org/pyret-code/ http://www.pyret.org/pyret-code/ > One of the enduring lessons from the Racket project is that no full-blown, general-purpose programming language is particularly appropriate for introductory education. By the time a language grows to be useful for building large-scale systems, it tends to have accumulated too many warts, odd corners, and complex features, all of which trip up students. The journal paper for DrScheme (the old name for DrRacket) explains this in some detail. In that respect, the closest fellow travelers of us Pyreteers are the Racketeers (see how that works?). In fact, the first version of Pyret was merely a #lang in Racket. Nevertheless, Pyret represents a departure from Racket (for now and for the near future, at least) for several reasons:

skrishnamurthi 10y ago

Except note that Pyret is not implemented atop Racket. It used to be (a #lang) but that proved not suitable for our needs, so we built a very sophisticated run-time system on top of JavaScript. Pyret now compiles to JavaScript entirely in the browser (and Pyret's compiler is written in Pyret itself, so it's all bootstrapped goodness). That said, Racket is indeed a fantastic next language after Pyret. I myself constantly switch between the two.