Gabriel Grinberg 2022-07-11 13:06:24 Hey all, I'm Gabriel, and this is my first time sharing Flyde here - a flow-based programming platform I've been working on lately.
I'm a big fan of FBP and am convinced it didn't catch due to 2 factors:
previous attempt's had GUIs that weren't good enough. They didn't take complete advantage of the visual layer
implementation was hard and integration with existing workflows (ci/cd, version control) was almost impossible
youtube.com/watch?v=2hdUKGZEYUw
Feedback is welcome! and looking forward to share more progress in the future 🕺
Yair Chuchem 2022-07-11 14:48:36 Looks nice!
It’s cool to see incremental projects that look like they can actually be used in real projects today.
Also, are you in Israel? If we collect several of us then perhaps it’s possible to make a local meetup :)
Jason Morris 2022-07-15 04:40:58 Yeah, that is very cool. Any thought of going two-directions, so changes in the code result in changes in the flow diagram? Any ideas for how to visualize diffs in the flow interface? Have you considered using zoom to enter into blocks instead of page switching? I feel like zoom has some uncaptured utility for nested structures.
Peter Saxton 2022-07-11 19:02:00 Added continuation passing HTTP fetch to my language. Also implemented another type provider to decode JSON dependent on the type that is needed. vimeo.com/728943149
Jack Rusher 2022-07-12 06:51:50 Forgive me if I missed it in a previous thread, but what's the main thing you hope this ML-like language will have/do that all the others do not?
Peter Saxton 2022-07-12 17:49:09 [June 23rd, 2022 12:28 AM] peterhsaxton: Hej. Glad to have found this community I think it's what I have been looking for for a while. I'm super interested in end user programming. (That seems like a good future of coding topic, or does anyone know a specific "end user programming" community)
Over the last year I have built my own language and structured editor. Pushing the idea of how much can a compiler tell you about your program. The idea is to have a really small AST, there are about 10 different nodes. Because it so small writing new static analysis tools should be easy, it's also really easy to target new environments. i.e. it took me about an hour to write a to Javascript. To keep it small I've made some unusual choices, for one the language contains type provider but not numbers. I keep a dev log of 3-8 minute long videos on various topics. https://petersaxton.uk/log/
Beyond that it's not really usable to anyone else (I haven't documented the keys for the editor so the only way to start is by referring to the source) That might change at somepoint, but I don't know when.
Mariano Guerra 2022-07-12 11:47:41 Jason Morris 2022-07-15 04:50:56 Answered my question about what was closing the boxes, thanks. :) I take it you were able to link the editor to three left column, and leave the preview in the right column. That feels strange, to me, for reasons I can't quite enunciate. Perhaps because the lengths can be so different, and there is no visual cue what part of the right column I'm currently modifying. I'm wanting something like the way cartographers indicate that a portion of the map is at a different resolution. Like images.app.goo.gl/s5eyZYNQKGMVTjGs5
