Echo JS 0.11.0

Update to v0.0.3b will have these benchmarks

| Name             | Ops / sec |
| ---------------- | --------- |
| nanocopy         | 1,607.397 |
| fast-copy        | 1,231.544 |
| lodash.cloneDeep | 562.028   |
| clone            | 445.612   |
| deepclone        | 389.008   |
| ramda            | 382.105   |
| fast-clone       | 323.623   |

Sorry, forgot to make repository public for the first release. It is live now: https://github.com/anywhichway/nano-copy

MaxArt's suggestion is simple and clean. If you are up for more work, perhaps have a threshold a user can set.

I get the general sense of the article and think the ideas have some merit; however, it reads like it was generated by an AI. Lots of strange grammatical structure and jumps from a partial thought to a conclusion or statements about history and relationships that are barely strung together. This makes it pretty hard to follow.

I certainly understand your point. Many of the concepts were developed internally prior to hyperHTML getting to the point it is today. If I bailed on TLX, I would go with hyperHTML. hyperApp is cool, but it kind of feels like reverse Polish notation on a calculator at times (dating myself!). Technically nothing new to learn but a whole different way of thinking. React is feeling pretty clunky, is lacking some key features, and is pretty opinionated. And, although Vue is probably easier for many to grasp than React, it also seems more complex than needed at times. And, it is also a good bit bigger than many other options. The main current plus of TLX is rapid spin-up with direct templating and the opportunity for almost full separation of concerns. JSX options make it so hard to do that. A lot comes down to  the profile of the team required to do a particular job both in size and skill sets.

Hi traker1!

v0.0.6a ALPHA now supports turning Express or Koa apps into function oriented servers. Just one require and one line of code on the surface, fosify(app), only 10 internally.

Note we do make very isolated direct use of the Node Response object which is counter to Koa docs, but in our small test case, things seem to be OK.

Kind of frustrating that Koa does not provide more API compatibility with the underlying Request and Response objects. Will re-work our internal code over time remain isomorphic but not break Koa rules.

Thanks, adding an express mount first and then Koa.

Just added NodeJS support and well as support for older browsers that do not have native Promises.

What are the specs of your test platform? I just installed locally Windows 10 64bit, 8GB, i7, 2.6GZ, node v8.1.3. Very different results. It also seems I can't create an Issue in your github respository. Do you have Issues turned off?:

Single param top 4:

 moize         │ 30,522,105 
fast-memoize  │ 23,692,264
micro-memoize │ 15,164,454
iMemoized     │ 9,512,034 (by anywhichway, not in your test suite)

Multiple pram:

 moize       | 17,628,577 
micro-memoize │ 9,016,574 
iMemoized     │ 8,114,019 (by anywhichway, not in your test suite)
 lru-memoize   │ 6,269,999 

Multiple param (objects - did not add iMemoized to suite)

 moize         │ 18,108,941
micro-memoize │ 10,661,604
lru-memoize   │ 6,255,101  
memoizee      │ 5,797,888 

My guess is if you take the time to build in browser tests, the results will be different yet again.

The core tlx parser has now been replaced with hyperx. Very thankful for you pointing it out. Saved MANY hours of development. Also added "inverted JSX". HTML can now be treated like a template directly, more like VUE or Ractive.