Not until there’s demand. I think we do see demand for Python transfers. 



> On Feb 13, 2019, at 3:11 PM, Stephen De Gabrielle <[email protected]> 
> wrote:
> 
> Should there be similar pages for Javascript, Java,C#, C/C++, Ruby, PHP, 
> Visual Basic, Scratch and Haskell?
> 
> S.
> 
> On Wed, Feb 13, 2019 at 8:03 PM Stephen De Gabrielle 
> <[email protected]> wrote:
> I created a DRAFT page on the Racket GitHub wiki:
>       https://github.com/racket/racket/wiki/Python-to-Racket
> It links to a 'Choosing a data structure' page 
> https://github.com/racket/racket/wiki/Choosing-a-data-structure
> - this just as copy of the table created by Jens Axel Søgaard at: 
> https://stackoverflow.com/questions/27584416/in-racket-what-is-the-advantage-of-lists-over-vectors/27589146#27589146)
> 
> Please edit/delete as you see fit
> 
> Kind regards
> Stephen
> 
> 
> On Tue, Feb 12, 2019 at 5:20 PM Matthias Felleisen <[email protected]> 
> wrote:
> 
> This is perfect! Thanks — Matthias
> 
> 
> 
> 
> > On Feb 11, 2019, at 11:04 PM, Claes Wallin (韋嘉誠) <[email protected]> wrote:
> > 
> > For anyone creating such a web page for Python to Racket specifically,
> > there is probably a great deal of inspiration, and reminders of
> > stumbling blocks, to be found in Arne Babenhauserheide's
> > https://www.draketo.de/py2guile book (available online for free) about
> > going from Python to Guile Scheme.
> > 
> > -- 
> >   /c
> > 
> > On Sun, Feb 3, 2019 at 7:00 AM Matthias Felleisen
> > <[email protected]> wrote:
> >> Racket needs *you*. Please.
> >> 
> >> The proper approach is to have short pages for different language 
> >> immigration groups: Python and R come to mind as obvious examples but I am 
> >> sure there are others.
> >> 
> >> What I mean is we need help and *you* can help. Let me explain it with the 
> >> Python example:
> >> 
> >> 1. Set up a page (wiki?) called “From Python to Racket”
> >> 
> >> 2. Create two sections that are immediately visible from the top:
> >> 
> >>        — idioms
> >>        — performance pitfalls
> >> 
> >> 3. In the specific case of Python, the second subsection needs to start 
> >> with a subsection on
> >> 
> >>        — Python Lists aren’t Racket Lists
> >>        — then point to data/ralis and show how to transliterate the 
> >> loop/append example like this
> >>        — optionally also show the more native Racket idiom
> >> 
> >> 4. When anyone observers another blog/social media/whatever post on Racket 
> >> is slow because I come from Python,
> >> 
> >>        (a) point the posters to the page  or
> >>        (b) if it is a new case, write a section for this example then do 
> >> (a)
> >> 
> >> 
> >> If you want to help advertise Racket to others, this is an excellent way 
> >> of helping out.
> >> 
> >> Thanks — Matthias
> >> 
> >> [[ p.s. For my very first Python program (a couple of days before meeting 
> >> with GvR), I used Python’s append and was annoyed beyond belief. ]]
> >> 
> >> 
> >> --
> >> 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 [email protected].
> >> For more options, visit https://groups.google.com/d/optout.
> > 
> > -- 
> > 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 [email protected].
> > For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> 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 [email protected].
> For more options, visit https://groups.google.com/d/optout.

-- 
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to