Hi,

While looking at an issue with the rendering of the Continue tutorial, I
got to thinking that Continue, as a flagship tutorial for Racket, needs new
sections to cover changes in web development practice, especially
supporting client side web frameworks(angular,Ember,Vue,React) by building
backends that support XMLHttpRequest/WebSockets/Fetch. Other possibilities
include
- developing with client side racket (RacketScript, Urlang, Whalesong?)
- authentication (both doing it yourself, or using OpenID to)
- creating and accessing web API's like AWS, twitter etc.
- custom #lang's or eDSL's to support the above (either highlighting
existing ones or creating new ones)

I think the best way to do this would be to develop a tutorial in the
_style of_ Continue, then it could be linked from, or integrated into the
Continue tutorial.

Any thoughts? Is this a good or bad idea? Would it be better to focus
community effort elsewhere?

Kind regards,

Stephen

-- 
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 racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to