fynyky

The big difference is that you don't have to use all of React! Plus with the ability to run child functions, you inject arbitrary logic inline without having to break the declarative structure.

This is a personal library I’ve been using for a while. I really don’t like how much frontend frameworks require you to invest in them. You have to learn funky domain specific languages, and magic render lifecycles just to debug anything. I mostly just want to create and append elements with better ergonomics. So that’s what I built.

The syntax lets you build a DOM declaratively with plain nested functions. This lets you define logic and views cleanly in a single structure, instead of reasoning across separate UI layout and UI logic. This also means you can use bit by bit instead of having to overhaul a whole project to a framework.

I hope you find it as useful as I have! Would love to get feedback from having fresh eyes on it.

Works fine with iOS 11 and above it seems. Older versions of iOS just died when trying any webrtc stuff. Takes a little bit of fiddling with media constraints but nothing too hard

Pretty simple actually. Just running express with socket.io on heroku. Using redis to enable socket.io cross-server messaging.

Client side the core engine is built on webrtc. Not using any major client side frameworks.

Yeah it's a personal project I've been working on for a while. All data is peer-to-peer and encrypted so there's no data for servers to store. Haven't figured out how to write a proper privacy policy yet

This is a side project I've been working on for a while. Basically I got tired of the whole "do you have skype?", "Are you ready to call?", "Okay calling now" dance every time you had to do a video call with someone. Started building this thing for my friends and I to use while gaming and just built on it from there.

Finally got to a stage where I decided to share this publicly. Would love to get some feedback and hear what you guys think

Check out this fiddle =)

http://jsfiddle.net/TjMgh/4/

One difference is that there is no need to explicitly subscribe to signals. For general functions, knockout requires manually declaring "myViewModel.property.subscribe(...)" for each model you need to subscribe to. In contrast, Reactor's observer blocks automatically detect which signals you have read and sets up the subscriptions automatically.

Knockout has a different class for ko.computed vs ko.observable. For Reactor you use "Signal" for both and just pass in a function when its computed. Additionally there is no need for the trailing "this" at the end of ko.computed.

It's "complete" as far as I've tested it. Changes are automatically pushed out without any additional work.

In terms of how it compares - It's based off the same reactive programming principles but is trying to keep the additional syntax and complexity to a minimum.

Yep. This is an attempt to do what knockout does in a simpler form with less syntax