Am I the only one who forgets Racket? Everytime I visit the site and browse through the documentation, I find myself wondering why I'm not using the language. Years ago I used Chicken Scheme but this seems more robust and the standard library is adequate. Who's using this in production? What's your experience?
Well, I haven't used it in production , but I used it for a research project last semester. It was actually pretty good, and there are definitely some very nice features. The standard library was pretty good except it missed some functional features I wanted like immutable vectors (or even just functional operations on mutable vectors). The language is extremely flexible, and you can take advantage of this to write s…
Racket v5.3.2
31–40 of 44 posts
Re: Racket v5.3.2
#32Am I the only one who forgets Racket? Everytime I visit the site and browse through the documentation, I find myself wondering why I'm not using the language. Years ago I used Chicken Scheme but this seems more robust and the standard library is adequate. Who's using this in production? What's your experience?
I used to use Racket in production and prototyping (few years ago), as a "glue language" and "business-logic" for a web-app, for the parts that are not IO, memory, compute intensive, etc. My metrics for language choice are: 1. Simple to learn and remember (they tend to correspond) 2. Module System; Support for modularization of complexity 3. Simplicity of coding and maintaining simple modules 4. Simplicity of coding…
What do you think Racket could do to improve (particularly 5)?
And what could other languages learn from Racket's module system?
Re: Racket v5.3.2
#33Am I the only one who forgets Racket? Everytime I visit the site and browse through the documentation, I find myself wondering why I'm not using the language. Years ago I used Chicken Scheme but this seems more robust and the standard library is adequate. Who's using this in production? What's your experience?
Re: Racket v5.3.2
#34Earlier quoted context omitted.
Well, I'm a little biased, but I would learn Haskell. It's the one I learned first--in fact, I learned it during my very first college CS course. (The course, coincidentally, was in Scheme.) If I managed it as a freshman, it can't be all that difficult :P. Haskell has a couple of very good freely available books: Learn You a Haskell [1] and Real World Haskell [2]. I also found Write Yourself a Scheme in 48 Hours [3]…
For Windows developers I would advice to use F# instead. Being a Microsoft language helps smuggle it into the work environment of the enterprise. It has become my scripting language for Windows tasks.
The compiler has to be compiled from source[2] on Ubuntu, which seems to suggest hardly anyone is using it.
Would there be any compelling reason to use F# if you're not working in a primarily Microsoft environment? What does the language itself offer over Ocaml or Haskell?
[1]: https://en.wikipedia.org/wiki/F_Sharp_%28programming_languag...
[2]: https://fsxplat.codeplex.com/wikipage?title=FSharpLinux
Re: Racket v5.3.2
#35Earlier quoted context omitted.
For Windows developers I would advice to use F# instead. Being a Microsoft language helps smuggle it into the work environment of the enterprise. It has become my scripting language for Windows tasks.
OK, I'm curious now. Wikipedia says[1] the reference implementation is open-source and cross-platform, which is great, but I never hear of anyone talking about F# outside the Microsoft world. The compiler has to be compiled from source[2] on Ubuntu, which seems to suggest hardly anyone is using it. Would there be any compelling reason to use F# if you're not working in a primarily Microsoft environment? What does the…
Given that, library access and ability to thread are the two big things it is going to have over Ocaml. Cleaner syntax when compared to Ocaml too. Haskell, not much.
Re: Racket v5.3.2
#36Earlier quoted context omitted.
Well, I haven't used it in production , but I used it for a research project last semester. It was actually pretty good, and there are definitely some very nice features. The standard library was pretty good except it missed some functional features I wanted like immutable vectors (or even just functional operations on mutable vectors). The language is extremely flexible, and you can take advantage of this to write s…
> Also, for a dynamically typed language, I thought it had too many different types. It was too easy to get mixed up between bytestrings and strings, for example. It was also not obvious when you should use or expect nil vs #f. That said, the features for creating your own types (mostly structs) were very good--I found they were very lightweight but still flexible enough to be useful. You can also used a typed dialec…
> You can also used a typed dialect of Racket if that's easier
I'm not sure that proposing a move to a typed dialect will solve a problem with too many different types. :-)
Re: Racket v5.3.2
#37Earlier quoted context omitted.
> Also, for a dynamically typed language, I thought it had too many different types. It was too easy to get mixed up between bytestrings and strings, for example. It was also not obvious when you should use or expect nil vs #f. That said, the features for creating your own types (mostly structs) were very good--I found they were very lightweight but still flexible enough to be useful. You can also used a typed dialec…
> > Also, for a dynamically typed language, I thought it had too many different types. > You can also used a typed dialect of Racket if that's easier I'm not sure that proposing a move to a typed dialect will solve a problem with too many different types. :-)
Re: Racket v5.3.2
#38Never having done anything non-trivial in a Lisp or Scheme, I'm looking forward to filling in a tiny bit of this huge gap in my knowledge. But like some other posters, I'll be surprised if I end up liking it better than Haskell.
Re: Racket v5.3.2
#39Re: Racket v5.3.2
#40Earlier quoted context omitted.
For Windows developers I would advice to use F# instead. Being a Microsoft language helps smuggle it into the work environment of the enterprise. It has become my scripting language for Windows tasks.
OK, I'm curious now. Wikipedia says[1] the reference implementation is open-source and cross-platform, which is great, but I never hear of anyone talking about F# outside the Microsoft world. The compiler has to be compiled from source[2] on Ubuntu, which seems to suggest hardly anyone is using it. Would there be any compelling reason to use F# if you're not working in a primarily Microsoft environment? What does the…
Queries and type providers are nice features of F# 3.0, but not sure how much it would matter as feature.