4 ms·
That's always the case though. The reason why we use programming languages is because we need the expressiveness they offer. Attempting to simplify it any furth
by chrisco255 7y ago
That's always the case though. The reason why we use programming languages is because we need the expressiveness they offer. Attempting to simplify it any further severely limits the type of applications you can build. And so you end up with cookie cutter apps. It might be fun, it might even be useful for some back office tasks, but if the marginal cost to produce a thing goes to near zero, it would imply the supply of apps competing for that category would explode.
- tluyben2 7y agoA lot nocode or lowcode tools are visual programming languages; they are in fact just programming tools but look (and often are) simpler to start off with. But when you need more, you are in fact programming with code, just via a visual interface. Which indeed can (will) become painful for many tasks. Then you are using the wrong tool for the job. Thing is, and this differs per market; most companies do not need anything more than endless streams of crud apps, and that is where these tools shine. You (and many of HN) might work in the b2c market, but where I work, people do not care much about how things look or ux; they care if they work just a little better than the sap or oracle interfaces they had before. Actually, this goes for many (most?) b2c products as well; most (traditional; challenger banks are a lot better) banking or airline apps I know look like bad template barf-ups (many are indeed that, bought from the same cooking cutting companies) and yet people use them. Would it be better if they were custom designed with money spent on actual ux and design? Sure, but apparently not enough to matter to the company commissioning it. When companies I work with look for no/low code, the only reason they will not use it is vendor lock in; if they cannot run on premise and/or ‘eject’ the code, they will not use it. Several products allow this and they are fairly popular (so much in fact that they cannot find enough ‘devs’ for their clients). These systems have their place; it is just (much) faster (some boring things in regular environments are just a few clicks with these tools) for some x% of applications while another y% you cannot do with them or is very difficult; I would still do the x% in such a tool as thinking ‘we might need x+y later on’ is premature usually and in my experience does not pan out. We have programmed applications ‘created for expansion’ 15-20 years ago that run to this day which would have fit in the x%; aka we wasted time and money while the expansion was never realised by the client. Edit; > it would imply the supply of apps competing for that category would explode. And that is a very consumer centric approach; we are not all making fitness apps or something; these apps would all look (more or less) the same but work on different APIs and data; that is fine for almost everything; not only some internal stuff. It helps companies a great deal to just have something their clients can use vs nothing, even if the cost is close to zero; and they cannot be the same as they talk with different systems and different data. Even creating partner dashboards more efficiently than slinging code is something people do all the time and you cannot ‘just copy paste that’ to another company. These products are not generally meant to build ‘the next whatsapp’. But you can prototype it with them and show investors; I agree with you there though; wrong tool for the job.
- TuringTest 7y ago> When companies I work with look for no/low code, the only reason they will not use it is vendor lock in; if they cannot run on premise and/or ‘eject’ the code, they will not use it. Several products allow this What nocode tools don't have lock-in? The ones I know which are open source still have these proprietary add-ons for important stuff like authentication or connecting to other systems.
- PeterisP 7y agoConceptually some no-code tools work essentially as glorified editors or code generators for a particular subset of a mainstream programming language. In this case, at any point you can abandon the no-code tool for a project or part of it and continue maintaining and developing it as an ordinary bundle of code.
- rhlsthrm 7y agoWhich ones? As a dev, if I had one that ejected into readable React (Typescript) code I'd probably use it.
- AlchemistCamp 7y agoWordPress
- pydry 7y ago>Thing is, and this differs per market; most companies do not need anything more than endless streams of crud apps, and that is where these tools shine. IME at least 20% of the needs of these companies are not met by "basic CRUD app programming" which is why these no-code things never really take off despite often appearing quite impressive. 80% is not enough. Basic CRUD also implies an understanding of domain modeling and normalized relational db design. In practice these are uncommon enough skills among developers never mind users of tools like these. That's half the reason why spreadsheets business users want turned into apps are so horrendous - it's not even intrinsically a problem with excel, it's just that the relationships between the domain objects are usually confused and the data is in a mess.
- wtvanhest 7y agoOn one hand this is correct, many apps compete only on form function like (Instagram vs snap). I think there will always be a random form function that captivates (today’s ticktok), but my prediction is that the web will be won less by competing on form factor, and rather won focused on other parts of the user experience. In a simple example, logistics is an obvious differentiator, 2 day vs 5 day shipping etc. There are so many dimensions to compete on and app design will contribute to many of those dimensions, but some ways to compete will not involve coding.