What's the difference between riot and browserify? about riot HOT 7 CLOSED

1. i use php instead of node and i want to have cons (Evnts/MVP) from riotj
2. riotjs propose one clear design pattern (MVP) in nodejs u can create different implementations of course.

from riot.

Why do you even need Browserify for events? You can simply scoop the node event emitter source code and use it under any setup, or use https://github.com/component/emitter

from riot.

The closest cousin to Riot is Backbone and the purpose is to produce modular / maintainable code. Riot promotes the use of MVP design pattern and provides some utility functions to achieve the goal. Browserlify's goal is to "require('modules') in the browser". Looks like Require.js to me ?

from riot.

Riot, as far as I can see is based on the observer pattern, just like the whole node.js event system. With browserify I can create the models which inherit from an EventEmitter, the same as the $.observable function. But I can also use the common.js pattern to modularize the client, use node.js modules and bundle all the scripts in a single file. This is just a humble opinion but I think Riot is more focused to the people that don't use node.js as a backend platform.

from riot.

Riot attempts to be the most minimalistic starting point to MV* world. There should be no extra on the library itself. If something is missing you add it there, not the other way around. It will also be a good source for documentation about organizing code in modular fashion (not there yet).

from riot.

@gagle Browserify brings node modules to the browser and riot.js is a client side library. Why there is confusion and why this issue is still open boggles the mind.

from riot.

@tbranyen agreed.

from riot.