3 ms·
It's cool technology, but if I take a look at an example of a simple react todo list in a similar project like flowhub: https://app.flowhub.io/#project/c111454c
by kabes 9y ago
It's cool technology, but if I take a look at an example of a simple react todo list in a similar project like flowhub: https://app.flowhub.io/#project/c111454c9fd2f74d37d1e8a4e739adfd/c111454c9fd2f74d37d1e8a4e739adfd_noflo https://app.flowhub.io/#project/c111454c9fd2f74d37d1e8a4e739...
This looks more complex, harder to reason about and harder to make than just writing the code. And it only gets worse as complexity increases. But of course I've got way more mileage writing code than doing this.
- samuell 9y agoThe link leads nowhere (seems login required, but even after login doesn't work). Link to screenshot instead?
- kabes 9y agoOops, here's a screenshot: https://screenshots.firefox.com/W3XZIh4yCnlcuMNM/app.flowhub.io https://screenshots.firefox.com/W3XZIh4yCnlcuMNM/app.flowhub...
- wdanilo 9y ago@kabes there is a BIG difference between Luna and NoFlow. Luna is purely functional, immutable, lazy, has double representation you can switch any time. NoFlow is visual layer over imperative, mutable JS without ability to swithc reprs. These features dictate how easy it is to do something in the language. You cannot judge a language by trying another slightly similar, its like telling "I don't like Python. I've been programming with Cobol and it was awful. Python is also textual so it's a no-go for me". I strongly encourage you to try Luna and I would be more than happy to discuss your thoughts about it. In fact, there are many people who prefer working in Luna's visual environment when processing data, discovering what is inside data and building high-level components. If you're building something low-level it is sometimes easier to do it in text - you can then just write Luna code instead and use nodes for high level data processing. Did I address your concerns?