3 ms·
it is genuinely odd to see this prejuidice against graphical tools persist in 2020 .. text file dot-conf and graphical tools are different but.. is it controver
by mistrial9 7y ago
it is genuinely odd to see this prejuidice against graphical tools persist in 2020 .. text file dot-conf and graphical tools are different but.. is it controversial that a graphical tool can emit performant code ?
I have no experience with NiFi itself.. just that graphical tools are not inherently "non-technical"
- cameronh90 7y agoI don't think it's about whether a graphical tool is performant. Many programming languages aren't performant either. It's more that graphical tools don't generally serve their stated purpose of making it possible for non-programmers to get things done because it appears that the main skill behind programming is actually problem decomposition and modelling rather than syntax. Additionally, graphical tools tend to have a bunch of problems inherent to them, such as being unable to write comments and harder to store in git and work on collaboratively and only having one single editor, which is usually much buggier than a text editor and compiler. So: graphical "languages" don't make most things much easier, and make other things much harder.
- ibejoeb 7y ago> it appears that the main skill behind programming is actually problem decomposition and modelling rather than syntax Totally. This is where declarative and intention-oriented systems shine. Take something like SQL, where, in the majority of cases, the end-user needs to know next to nothing about algorithmic complexity and can still achieve excellent performance and correct results. It'd be neat to see a system that was actually designed toward problem decomposition. What's the state of the art around this kind of stuff?
- tonyarkles 7y agoWe have very obviously worked on different types of end-user SQL. One that springs to mind had 30 or 40 tables, evolved over the years as “special cases” popped up, and by time I was asked to look at it, it was maybe too far gone. I tried. Maybe if the schema had been tended like a garden, the queries wouldn’t have been so crazy, but... Mind, though, that this system had made a ton of money for 15 years, so in a way it was a huge win for them! They just eventually painted themselves into a corner and performance started to get worse faster than Moore’s law could save them. Last I heard, the great untangling is still in progress, and I stepped away from that project a few years ago. They likely have still come out on top when you take the sum of revenue they made from the system, but they incurred a huge unanticipated cost and got backed into a pretty bad corner. Sales people were still selling features that didn’t exist, and the team was desperately trying to build new things while also fixing the ever degrading performance.
- hermitcrab 7y agoI think GUI tools come a cropped when they try to do too much, but can work very well in limited domains. We have recently released a GUI tool to do data transformation/ETL ( https://www.easydatatransform.com https://www.easydatatransform.com ). It is aimed more at power Excel users, than programmers or data scientists. We have tried to overcome some of the issues mentioned here: * It is only intended for the limited domain of data transformation, which limits the complexity. * No need to remember any syntax/commands for the vast majority of use cases. * The transformation template is stored in a single XML file, so it can be versioned. * You can use regexp, Javascript and command line arguments to get extra power if you need it. * It is written in C++ and is fast. Obviously it can't do everything you can do with a general purpose programming language, but it hopefully do enough for many use cases and is much easier to learn.
- JimmyRuska 7y agoI don't think it's a prejudice. I've seen pentaho introduced as a way to enable business analysts to do work otherwise expensive developers would have to do. It simply didn't work, business analysts were not able to use it, devs had to take over and when they did they did not want to use pentaho. It's an easy trap for upper management to fall into thinking the selling point of these tools is the ability to allow the non tech staff to do the programming.
- Mouse47 7y ago+1 to this. I've seen similar stories play out with Microsoft's Logic Apps, Power Apps, and to a lesser extent Dynamics.
- skywhopper 7y agoThat seems to be the thrust of the comment you’re replying to: the graph is essentially a programming language, with all the same complexity but multiplied because the same level of complexity is being managed without the same level of sophistication of tools like version control and even basic code re-use constructs typical in text-based languages.
- chii 7y agoThere's a general level of elitism in the programming world. GUI tools are seen by some programmers as a "worse" tool, but without any real evidence, and it's likely due to the fact that GUI tools enable non-programmers to reach some level of output that used to be the sole domain of programmers. It's a similar train of thought that leads to a lot of game developers to look down on games made with GUI tools like gamemaker or such.
- RhodesianHunter 7y agoCan we claim that it's elitism when it's born from experience? Programmers have seen these sorts of UIs fail to deliver countless times as described in the root of this thread. Where is the counter example?
- pjmlp 7y agoUnreal, Unity, Substance, Octane Render, and Scratch.
- wpietri 7y agoGUI tools have a very long history of being about to revolutionize the industry but ending up as dead ends. If you want evidence, just look to the past. I'm honestly all for tools that enable non-programmers to get things done. E.g., Excel, Google Forms, Zapier, and a lot of Salesforce tooling all deliver to some extent on that promise. But there's only so much they can do. You're right that there's also an elitism problem. But if we're going to get past that, we have to start by understanding what GUI tools are good for. And being honest about their limits.
- pjmlp 7y agoNot all game developers, AAA game engines have lots of visual languages specially for what the game designers and artists end up using.
- lmm 7y ago> is it controversial that a graphical tool can emit performant code ? No. But it's controversial to claim that a graphical tool can do maintainable code.
- atoav 7y agoI am working with graphical tools and node based structures for years. Think about Blenders shader nodes or modular synthesizers. These systems are good to play around, try things out, quickly change how things are connected. Above a certain complexity they become very hard to organize. If the complexity of your problem is below this level and the user has any self control, all is good. If the complexity of your problem is higher you'd need a programmer who knoes how to handle this anyways.
- tiew9Vii 7y agoHow do you do what has become basic best practices in a gui? Everything under source control, defined as code. * This gives you the ability to trace who did what * Good code-commit hygiene with prs * The ability to revert changes * Ability to have an exact replication and promote across environments Pragmatically test changes, unit test your flows * Tie all the above up with a deployment pipeline NiFi is being used in the critical parts of business data pipelines and all the devops rules for reliable development and deployment go out the window. If NiFi is used by one person for a minor role the GUI is fine. But if it’s the core data pipeline which is a critical service used by multiple teams it’s not the smartest way to do things.