5 ms·

Atom is very different from other things. The editor component is something that revolves almost entirely about state, and a huge amount of state at that. I th

by rtpg 12y ago

Atom is very different from other things. The editor component is something that revolves almost entirely about state, and a huge amount of state at that. I think the future is, like many abstractions, one where your tighter loops escape the abstraction (like numpy's C bindings). There's still advantages on a big-picture scale to using declarative frameworks like React EDIT: one thing is that a text editor can know a lot better how to edit the DOM after an event (like hitting a character) than React's general algorithm

seanmcdirmid 12y ago
This is why I designed Glitch: http://research.microsoft.com/apps/mobile/showpage.aspx?page=/en-us/people/smcdirm/managedtime.aspx http://research.microsoft.com/apps/mobile/showpage.aspx?page... Note that all the live editor examples in the essay are written in Glitch. Think of Glitch as a react like framework that focuses on fixing mutable state through time management rather than avoiding it.
- warkid 12y ago
  I believe that the page you referenced to is broken. I.e. no videos or code samples on, see screenshot - http://snag.gy/lMAp8.jpg http://snag.gy/lMAp8.jpg
  - seanmcdirmid 12y ago
    Ugh...mobile link, this should work: http://research.microsoft.com/en-us/people/smcdirm/managedtime.aspx http://research.microsoft.com/en-us/people/smcdirm/managedti...
- bglazer 12y ago
  Hi Sean, having skimmed the presentation you linked to, Glitch's programming model seems similar to VHDL and Verilog, in that the "tick" is an explicit construct and statements are not guaranteed to execute sequentially. I'm not experienced in VHDL, so I might be completely wrong here. Did you take any design cues or inspiration from hardware design languages?
  - seanmcdirmid 12y ago
    There is an inspiration from synchronous reactive languages, which are in turn inspired by hardware design (not sure if they predate or post date vhdl); you can read the related work section of the essay-linked conference paper if you are interested about lineage. Glitch is a bit weirder in that all statements execute at the same time within a tick, their order isn't just unfixed: they are guaranteed to see all of each other's effects (except event handlers, which execute more hardware-like discretely to do state transitions).

by rtpg 12y ago

seanmcdirmid 12y ago

This is why I designed Glitch: http://research.microsoft.com/apps/mobile/showpage.aspx?page=/en-us/people/smcdirm/managedtime.aspx http://research.microsoft.com/apps/mobile/showpage.aspx?page... Note that all the live editor examples in the essay are written in Glitch. Think of Glitch as a react like framework that focuses on fixing mutable state through time management rather than avoiding it.

warkid 12y ago
I believe that the page you referenced to is broken. I.e. no videos or code samples on, see screenshot - http://snag.gy/lMAp8.jpg http://snag.gy/lMAp8.jpg
- seanmcdirmid 12y ago
  Ugh...mobile link, this should work: http://research.microsoft.com/en-us/people/smcdirm/managedtime.aspx http://research.microsoft.com/en-us/people/smcdirm/managedti...
bglazer 12y ago
Hi Sean, having skimmed the presentation you linked to, Glitch's programming model seems similar to VHDL and Verilog, in that the "tick" is an explicit construct and statements are not guaranteed to execute sequentially. I'm not experienced in VHDL, so I might be completely wrong here. Did you take any design cues or inspiration from hardware design languages?
- seanmcdirmid 12y ago
  There is an inspiration from synchronous reactive languages, which are in turn inspired by hardware design (not sure if they predate or post date vhdl); you can read the related work section of the essay-linked conference paper if you are interested about lineage. Glitch is a bit weirder in that all statements execute at the same time within a tick, their order isn't just unfixed: they are guaranteed to see all of each other's effects (except event handlers, which execute more hardware-like discretely to do state transitions).