mori

A router and an immutable collections library (immutablejs or mori for instance) are very convenient additions, but by no means necessary.

Can someone explain the advantages of using this over mori (which doesn't include cursors per se at the moment, but are easy to implement on top of mori data structures)?

For those unaware (or too lazy to go to the website) the transliteration is as follows: 'Dulce et decorum est pro patria mori' -> Sweet and fitting it is for the fatherland to die.

It originated in robotics, and was coined by Masahiro Mori in 1970.

You're not going to hear about Naoki Mori on HN.

More in the vein of ReactJS, ClojureScript, Om, mori etc...

It should be noted that in the original latin work, 'Dulce et decorum est pro patria mori...' the phrase is also spoken with irony/satire, but then subsequently taken out of context and used to rally the troops.

That being said, I'm very interested in mori, immutable-js or lz.js.

Compared to the stuff I do on a phone in idle moments, chatting with a simulated hermit while contemplating a memento mori desktop seems positively useful.

This has already occurred in a small way with things like the virtual dom technique (which can be easily made immutable and updated purely) and the rise of things like Mori and Immutable.js.

Wikipedia: "The term was coined by the robotics professor Masahiro Mori as Bukimi no Tani Genshō in 1970.

The complete list of male scientists in the last few years are: Naoki Mori, James H.

They should be more cautious, or have people around them that will urge them to be more cautions (like some 'Memento Mori' roman serf).

Mori's insight was that people would react with revulsion to humanlike robots, whose appearance resembled, but did not quite replicate, that of a real human.