[freework]

As much as I want to love this thing, I can't help but feel like they are trying to solve an unsolvable problem.

We don't consider Michaelangelo a genius because he thought up the David statue. We consider him a genius because he went through the process to make the statue exist.

Great software exists not because someone thought it up. Great software exists because someone went through the process of making that software a reality. There is no shortcut, in the same way that there is no shortcut between thinking up a really nicely painted portrait, and making that portrait a reality. The only way to make a painting a reality is to learn how to paint. The only way to make a program a reality is to learn how to code. Any tool that claims to make coding easier is nullified by the fact that you have to still have to learn that tool too!

[ics]

What is your point? Regardless of how easy or hard the tools we make are obviously someone has to learn them to use them, and when they use them well it will be praised. If this allows people to make better and more robust software with less skill, the bar gets raised and that's a great thing. You could say the same thing about any new tool or language but, well, that's how things develop.

    Is it a magic bullet? No Yes
                           |   |
                          Ok.  |
                               |
                  Find some larger things to shoot. Repeat.

[meemoo]

More than making coding easier, I think we're trying to give strict structure to code and pair it with a visual metaphor to help manage complexity. There is a learning curve, but we're designing it to stick close to JavaScript.

If we succeed, I imagine that we'll just increase the complexity of the coding that we take on. That's an interesting possibility. I'd like to imagine a new generation of startups with more interesting tech than CRUD.

[rubinelli]

The strict structure kinda bugs me. I expect situations where a clean solution using higher order functions outside this framework is possible, but if I implement it, I no longer have this clear picture of the system. Or I submit to it, perhaps duplicating code and spreading gnarly business rules on top of what should be "pure" data flow logic.

EDIT: Still, I'm all for experimentation. If they can pull this off, great!

[mugenx86]

>Any tool that claims to make coding easier is nullified by the fact that you have to still have to learn that tool too!

This statement is proven false by the number of IDE's that claim to make coding easier, and in fact do.

Noflo makes code easier to maintain and collaborate on by providing a visual map of how code is designed. The benefits of which should be plainly apparent if you have ever been tasked with maintaining >10,000 of lines of code.