Who's using mercury about mercury HOT 15 OPEN

Doing just a small private project for now. To try it as alternative to my own virtualdom. :-)

from mercury.

i'm building a social network as part of http://gener.us/. it's still some months away from being released. http://gener.us/about/our-vision/ explains the bigger picture.

from mercury.

I'm using mercury heavily in a not-done-yet application.

from mercury.

@nrw nice! Btw we have an IRC room on freenode called #virtualdom come there to ask questions and such :)

from mercury.

I'm working on converting a project from react (which actually is working, but I'm still trying to get my test suite ported over)

from mercury.

@Raynos Is Uber using it?

Also, for this ecosystem of libraries, what set of browsers do you intend to test against?

from mercury.

@gobengo uber is not using it yet, will eventually :)

My personal browser testing is current + previous (same as google engineers) for big 5 so IE10+, I'll take PRs for IE9.

I think @Matt-Esch wants to make virtual-dom work in IE8.

from mercury.

@Raynos cool wrt Uber using it someday (btw I live with Amos there if you know him)

Just looking into all this today. I have a hard must on IE9 with my work on streamhub-sdk et al, whose patterns are mostly Backbone-ish Views and streams3-style streams

In my experience it is rarely too annoying to support IE9. If I end up using any of these libs I will inevitably test there and aim to PR back. IE8 is a different beast.

Love the work in general on a react-decoupled virtual-dom and FRP/observable tools. I'm still trying to figure out when and how to use streams3 vs observ-style observables vs rxjs-style observables. Sad that they seem to have a good amount of overlap, given that it seems one of the benefits of the patterns is composition but that they don't compose trivially.

Do you have an opinion on when you'd use an objectMode streams3 vs an observ?

from mercury.

@gobengo if you dont need back pressure then you dont need streams3.

If you dont need to handle a large stream in chunks due to memory limitations then you dont need streams3

streams3 is also great if your working with any kind of IO. If your not working with IO then you dont need streams3.

observs are good if you want to observe some in memory data.

from mercury.

In terms of the IE8+ support, generally speaking the ES3 style makes faster code and so virtual-dom just so happens to work in IE8. A while back I had the tests running in IE8 and they were only failing because the tests were using fake properties on the nodes, and this was also causing errors in phantom.

There is no standardization of the DOM though, that is out of scope. The node properties map onto the DOM node in the browser you're running it in. If that property happens to have different side effects in other browsers then that is what will happen .

from mercury.

I've began a new version of http://www.heroloop.com as a PhoneGap mobile app using Mercury. AngularJS has been driving me crazy, so it's an attempt to ditch it.

from mercury.

@mattferrin nice! Come hang out in #virtualdom on IRC (freenode) if you have questions

from mercury.

The vapor client for ethereum is being built with mercury 😸

from mercury.

Coviu's main video conferencing UI is built on Mercury, and we love it ❤️

EDIT: team asked me to offer @Raynos a free account if you want one 😉

from mercury.

https://github.com/lazurite-app/lazurite is built with mercury. Also got a couple of clients where I'll be using mercury / virtual-dom in projects (':

from mercury.