“Implement text editor DOM updates manually instead of via React”

Re:“Implement text editor DOM updates manually instead of vi... by seanmcdirmid on Thursday February 26, 2015 @11:51PM (#9117234)

This is why I designed Glitch:

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.

[ Parent | on HN ]

Re:“Implement text editor DOM updates manually instead of vi... by warkid on Friday February 27, 2015 @02:44AM (#9117682)

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

[ Parent | on HN ]

Re:“Implement text editor DOM updates manually instead of vi... by seanmcdirmid on Friday February 27, 2015 @03:00AM (#9117736)

Ugh...mobile link, this should work:

http://research.microsoft.com/en-us/people/smcdirm/managedti...

[ Parent | on HN ]

Re:“Implement text editor DOM updates manually instead of vi... by bglazer on Friday February 27, 2015 @10:03AM (#9119171)

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?

[ Parent | on HN ]

Re:“Implement text editor DOM updates manually instead of vi... by seanmcdirmid on Friday February 27, 2015 @10:25AM (#9119300)

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).

[ Parent | on HN ]