You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a good, small test-case for CMB. If we can give kids a simple playground for a limited language and have it hold up well, it says a lot about the internal stability of the library.
The text was updated successfully, but these errors were encountered:
Update - this is going to require that the Pyret blocks mode is up to snuff. Organizationally, we need to prioritize Data Science, and since WeScheme doesn't have any DS functionality that means we have to use Pyret.
Hmm. I feel pretty confident about being able to get the pyret language module up and running again, but I don't feel confident about getting it deployed to production... certainly not in time for CSEdWeek. If we can't have this ready for CSEdWeek, does that shift our priorities? Our current milestones are focused on making WeScheme blocks really solid before tackling other languages, should that change?
I think having WeScheme work remains the top priority, since WeScheme blocks is by far the easiest and most complete of the two block modes. It may be that we simply punt on the block-based hour of code for now.
This is a good, small test-case for CMB. If we can give kids a simple playground for a limited language and have it hold up well, it says a lot about the internal stability of the library.
The text was updated successfully, but these errors were encountered: