4 ms·
> If you wanted to change the world of programming I would think of a way to abstractly describe dataflows in the vain of unix pipes. Define every part of the t
by jcelerier 9y ago
> If you wanted to change the world of programming I would think of a way to abstractly describe dataflows in the vain of unix pipes. Define every part of the transforms you need to do on incoming data, where those responsibilities should be, and then link them together.
there are plenty of people programming in datflow languages where you do exactly this (eg LabView, Max/MSP, PureData, vvvv, etc...). Guess what: after some time it just becomes shit too, because making such graphs is freakin hard.
exhibit A: http://1cyjknyddcx62agyb002-c74projects.s3.amazonaws.com/files/2014/11/screenshot.jpg http://1cyjknyddcx62agyb002-c74projects.s3.amazonaws.com/fil...
exhibit B: https://ni.i.lithium.com/t5/image/serverpage/image-id/184872i5D184D60A62CEF6F?v=1.0 https://ni.i.lithium.com/t5/image/serverpage/image-id/184872...
- gravypod 9y agoJust because it hasn't worked before doesn't mean that there isn't a good way, that has yet to be created, for describing data flows and modularizations of systems.