4 ms·
Unexplained important things: * concurrency, is there any nice built in syntax like Python async? Any kind of threading? Multiprocessing support? * error hand
by AstralStorm 10y ago
Unexplained important things:
* concurrency, is there any nice built in syntax like Python async? Any kind of threading? Multiprocessing support?
* error handling, how is it done? Where are exceptions?
* standard and file io, string operations, serialisation?
* no builtin higher math types (matrix etc.), is math done on decimal floating point numbers?
* foreign functions, interfacing with other languages, embedding?
- davexunit 10y agoJudging 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 agoBut why? Best languages are truly general. This should aim to replace Racket, not be bait for a switch.
- baldfat 10y agoRacket 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 agoRacket 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 agohttp://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 agoExcept 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 agoAlso: * metaprogramming - templates, macros, generic programming?
- jswrenn 10y agoShhh! That's on the horizon! One of the frustrations of using Racket—which is macros all-the-way-down—is debugging. When you see an error message or use a stepper-debugger, you want it to be in terms of the code you wrote; not in terms of the code generated by some complicated macro which was glued together by a sleep-deprived graduate student. One of the graduate students here in the PLT group at Brown, justinpombrio, is working on resugaring—taking a sequence of evaluation steps in terms of a post-macro-expansed program, and presenting them back to the user in terms of the surface-syntax of the language. (More on this at his website, http://justinpombrio.net/ http://justinpombrio.net/) We're just starting to prod at implementing Pyret's existing syntactic sugar in this manner, which will be a first step to a proper macro system.
- jswrenn 10y agoGreat points! These are important things, but not necessarily important to Pyret. Pyret is not designed to be a general-purpose programming language, so the design of the language is directed and constrained by the needs of the teachers who use it. Pyret's number representation is one consequence of this: Pyret numbers are stored as either exact rational numbers: > num-sqrt(4.41) 21/10 or, when an exact representation isn't possible, as "roughnums" (which are backed by a Javascript floating-point number: > num-sqrt(2) ~1.4142135623730951 Pyret's users overwhelmingly use Code.Pyret.Org, an in-browser development environment. Unfortunately, Javascript is a very hostile compilation target. For the time being, this rules out support for threading. Pyret does not have FFI from an end-user perspective, but several of the standard library modules are implemented in hand-written Javascript. Pyret has file I/O, but not in its online development environment, since the web page does not have filesystem access. (Disclosure: I am a developer of Pyret!)