The ultimate "low code" experience I had was back in the 1990s with Delphi. You drag and drop your form elements, get everything just right. Next you hook up your event handlers and type in a few lines of code to do the actual work. It was the best I've ever seen balance of managing complexity, yet letting you write code when you needed to. The C++ version was nowhere near as god, it generated a ton of templates and…
I used Delphi a lot in the 90's and early 00's, but I never really considered it "low code", with the exception of the drag and drop forms designer of course.
Ask HN: What do you think about the no-code movement?
361–370 of 404 posts
Re: Ask HN: What do you think about the no-code movement?
#362The definition is tricky when you start from a negative.
There is a companion term 'low code' - because people discovered that 'no code' is too restrictive. But that is even more foggy. If a new library comes out and suddenly your program shrinks to a short script - is that 'low code'?
Re: Ask HN: What do you think about the no-code movement?
#363What I found is what everyone finds; when the tool does not support something, it gets very hard.
I think of that as follows: the request to make that 'impossible' feature came from somewhere; if you rethink the feature so it's trivial to click together with the tool and then convince the owner of the feature to accept that reality, you often get away with it. Just accepting that you don't need certain complexity for things to function well is often, imho, a perfectly fine solution.
If the client or owner does not accept to work this way, I don't use no/low code at all.
Re: Ask HN: What do you think about the no-code movement?
#364I know an agency of 5 people absolutely flat out delivering low-code solutions on the MS Power Platform, mostly for government agencies. The thing is, these solutions probably couldn't be delivered by non-engineers, but these people are able to move extremely quick because of the platform.
Re: Ask HN: What do you think about the no-code movement?
#365I know an agency of 5 people absolutely flat out delivering low-code solutions on the MS Power Platform, mostly for government agencies. The thing is, these solutions probably couldn't be delivered by non-engineers, but these people are able to move extremely quick because of the platform.
Power Apps is quite buggy and quite difficult to implement with questionable design decisions (The programming language changes with regional language, so member selectors like . get translated to ,) that makes code incompatible if you change Power Apps language (yes, really). Not that you can easily export/import projects from one tenent to another. The programming language itself is not less complicated than classic languages, the strength is the platform. What wordpress is to blogs, Power Apps wants to be for mobile apps if you will.
Power BI is a lightweight App that basically leverage pivot functions of Excel is a small web app. Quite useful, but there should be no illusions about the capabilities. Nice for quick data analysis with the usual drill down.
For a government to use Power Apps means to be extremely dependent on MS. It is rather questionable and very expensive in my opinion.
That said, no code workflows and applications builders would help a lot. But current examples are severely lacking in my opinion.
Re: Ask HN: What do you think about the no-code movement?
#366Earlier quoted context omitted.
I definitely think that's a large part of it, but I saw impressive uses of Excel and Access by non-coders long before it was typical to lock-down workstations the way corporations do nowadays (like, 20 years ago).
Excel is used because it's understood by business types, not because it's the only thing available. They're comfortable with spreadsheets, it's no surprise that they'll try to solve any given problem they have with spreadsheets. You see the same thing in reverse, with programmers reaching for Python when Excel probably would've been a better choice. Everyone reaches for what's familiar.
Connect to database, pull multiple tables into pandas / numpy. Then start joining to find the records they want in python.
Why, why, why ???
Re: Ask HN: What do you think about the no-code movement?
#367Re: Ask HN: What do you think about the no-code movement?
#368Earlier quoted context omitted.
>The ultimate "low code" experience I had was back in the 1990s with Delphi. You drag and drop your form elements, get everything just right. Next you hook up your event handlers and type in a few lines of code to do the actual work. Today I was thinking about Visual Basic 6, which worked more or less the same way. I wonder what similar alternatives we have today? Gambas? https://en.wikipedia.org/wiki/Gambas
Vb6 still works. I just put out a new version of my project today :)
Re: Ask HN: What do you think about the no-code movement?
#369Maybe ask some of these people: 1 hour before you Ask HN: Do you like the term 'nocode'? https://news.ycombinator.com/item?id=29187754 2 days ago Ask HN: No Code GUI Tools? https://news.ycombinator.com/item?id=29160858 3 months ago Ask HN: Is there any future for low-code/no-code development? https://news.ycombinator.com/item?id=28150056 4 months ago Ask HN: Anyone built a business with no-code tools? https://news.yc…
We have to start doing like those Soccer Mom Facebook groups and put something like: "please use the magnifier glass[0] to search if your question hasn't been asked before" [0] https://hn.algolia.com/ Edit: I'm getting heavily downvoted. Sorry guys, it was just a joke.
Just because it's been asked before doesn't mean that the people answering it are the same etc etc
Re: Ask HN: What do you think about the no-code movement?
#370At the end of the day you are still instructing a machine to operate.
Every task that's complex enough still requires a "coder mentality" to perform.
It's just that many people don't want to bother with the quirks of classic programming languages and the technical baggage that they drag around from birth.
The worst feeling comes when you realize you are spending most of the time fighting with the tools than actually solving the problem you had in the first place.