abss

The right age. Having strong industry experience the chanches for doing something "more real" and not too academic are higher.

www.opendsu.com

www.opendsu.com

My approach is to extend OOP concepts with embedded types and have two types of events: PropertyChange and DocumentChange.

Curently in Shape, the public MVVM framework I have, those concepts are only partially developed.

Contact me privately for details.

I have some experience in this area, I'm the main author of 3 programming frameworks targeting this (two created for two failed startups ). Now, I got great results like doing 4 products in an year ( with hundreds of concepts, database tables, complex processes) with only 2 programmers. An visible speed improvement but still was not the case that non programmers could program easily. Because of financial constraints we abandoned the creation of the GUI for creating apps and used the framework (targeting Flex/Flash ). Now, I outsourced an MVVM framework for JS (https://github.com/salboaie/SwarmShape) that is created with an architecture that serve the purpose of having visual UI to speed up the development. There is no GUI and tools but the framework is constructed to make tooling possible. I see such UI behave like better spreadsheets usable for creation of simple apps (using reusable components and simple scripting) by intelligent people having only a few days of training. It is feasible, only the business aspects should be clarified. If you want an discussion on this topics, feel free to contact me. salboaie@gmail.com

You can contribute to SwarmESB (ESB type system for node.js) https://github.com/salboaie/swarmESB If you don't know the purpose of ESBs, with SwarmESB you will understand faster because is basically an abstraction on messages, channels, etc. that hides lot of "useless" details that surface in Java ESBs or MOMs.

For really good programmers, with passion on distributed systems new implementation for bus communication (now based on Redis pub/sub) or mechanisms for fail recovery,etc.

We need collaborators native English speakers, capable to create real hype around swarms by writing nice articles, showing proof of concepts. Also, we are open for collaboration with academic researchers to publish new articles on swarms!

SwarmESB have a new and simple programming model. With swarms I'm hoping to make ESBs mainstream to normal programmers.

An ESB is a big and complex project and you can contribute in many ways: code new features, examples, documentation, tests.

var harvest = require("harvests").create();

    harvest.let('father', loadPenguin, 'MrPenguin');
    harvest.let('mother', loadPenguin, 'MrsPenguin');
    harvest.let('family', loadPenguinFamily, wait('father'), wait('mother'));

    harvest.do(function(family){
        console.log(family); //also in  harvest.father, harvest.mother, harvest.family you got values
    }, wait('family') );

    harvest.onFail(function(error, variable, index){
        console.log("Well, move those penguins to the South Pole...", error, variable, index);
    });

Harvests: asynchronous programming as would be synchronous. Simpler alternative to promises and control flow libraries!

From now is possible to call asynchronous functions in a declarative way and to get almost the same experience as with synchronous code

Let't see how many votes we got...

A system similar with Bitcoin could be usefull (something to guarantee convertibility for merchants)?

I wander of social responsibility is enough to convince merchants to use this new currency.

Take a look for a fresh aproach on building distributed systems around a node.js message bus and special DSL to describe message flows : https://github.com/salboaie/SwarmESB

bad move Adobe.

I would rather go in the direction of extending JavaScript in the direction of ActionScript 3. I love Action Script and I feel that JavaScript is a bit hacky for RIA (not clean OOP,refactoring is hard) What do you think?