title |
---|
Research Ideas |
-
it's so hard to get a sense of a project via the folders and files abstraction
-
higher-order functions are tricky to understand
-
it's difficult to keep track of the specific problem we're working on and how it pertains to the larger goal
-
version control of firebase, for development, rollbacks
-
streams as spreadsheets
-
mock up what it would look like to have layers as the core computational abstraction, allowing users to peak under the hood of their apps, change things, and submit pull requests without leaving the app.
-
continue researching types-as-shapes, potentially even building a prototype
-
build a Workflowy-like work planning and branching tool (potentially for woofjs.com)
-
reactive game engines
- make a reactive WoofJS
- make a game engine with an aprt.us interface
- make an Elm game engine
-
can we combine strong types + macros to get natural language coding or less stack overflow?
-
essay about why we should stop teaching for loops in favor of forEach loops and while loops (is this how python works already?)
-
continue working on Cycle v2 w/o VueJS (and maybe without Blockly)
-
continue working on Rose v1 with text as UI
-
work on a Lamdu- or Unison- like structured editor for the web
<script> (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m) })(window,document,'script','https://www.google-analytics.com/analytics.js','ga'); ga('create', 'UA-103157758-1', 'auto'); ga('send', 'pageview'); </script>