3 ms·

You mean, visually? or conceptually? Visually is more complex, you need to build a UI. But the concept, that can be done with a DSL, combining the concatenate

by mamcx 8y ago

You mean, visually? or conceptually? Visually is more complex, you need to build a UI. But the concept, that can be done with a DSL, combining the concatenate/stack/tacit programming paradigms. How much nice, depend in what you want...

0815test 8y ago
Haskell seems to support the flow-based-approach quite well, 'conceptually'. And I'm not sure that it can be done effectively and intuitively without the first-class-functions, lazy-evaluation, strong typing, etc. that Haskell provides.
NicoJuicy 8y ago
Visually is kinda easy. There are a lot of UI tools for that on Github. The concept, can't be done in a DSL. Because node-red makes exceptionally well use of the dynamic programming paradigm ( and with the optional payload property). Just converting it to a Dictionary<string,object> when it enters || exits a node doesn't seem enough. + A huge performance drain
- mamcx 8y ago
  How you think > dynamic programming paradigm is implemented? With something like Dictionary<string,object>. Yep, exist some tricks you can apply, but to make things "dynamic" you will need to use something like that. C# have the buildings blocks for make something like that, like the Expando object and the whole meta programming. However, a custom interpreter could be best. P.D: I'm implementing a custom programming language, and research about it a lot. BTW, the use of hash maps with a decent hash function will not be necessarily the bottleneck...
  - NicoJuicy 8y ago
    > Because node-red makes exceptionally well use of the dynamic programming paradigm Because of flexibility around the payload/context property. I can map anything generic through abstracts and T1,T2,... In c#, but it's not enough Not sure about anything use related. Or I need to reduce the flexibility that I wanted before and look to the mapped properties only and ignore the rest. Which would be a lot easier

by mamcx 8y ago

0815test 8y ago

Haskell seems to support the flow-based-approach quite well, 'conceptually'. And I'm not sure that it can be done effectively and intuitively without the first-class-functions, lazy-evaluation, strong typing, etc. that Haskell provides.

NicoJuicy 8y ago

Visually is kinda easy. There are a lot of UI tools for that on Github. The concept, can't be done in a DSL. Because node-red makes exceptionally well use of the dynamic programming paradigm ( and with the optional payload property). Just converting it to a Dictionary<string,object> when it enters || exits a node doesn't seem enough. + A huge performance drain

mamcx 8y ago
How you think > dynamic programming paradigm is implemented? With something like Dictionary<string,object>. Yep, exist some tricks you can apply, but to make things "dynamic" you will need to use something like that. C# have the buildings blocks for make something like that, like the Expando object and the whole meta programming. However, a custom interpreter could be best. P.D: I'm implementing a custom programming language, and research about it a lot. BTW, the use of hash maps with a decent hash function will not be necessarily the bottleneck...
- NicoJuicy 8y ago
  > Because node-red makes exceptionally well use of the dynamic programming paradigm Because of flexibility around the payload/context property. I can map anything generic through abstracts and T1,T2,... In c#, but it's not enough Not sure about anything use related. Or I need to reduce the flexibility that I wanted before and look to the mapped properties only and ignore the rest. Which would be a lot easier