Live data from Hacker News

RIP Low-Code 2014-2025

zackliscio.com

1–10 of 160 posts

Re: RIP Low-Code 2014-2025

#4

Broken link, should point to https://www.zackliscio.com/posts/rip-low-code-2014-2025/

thanks for flagging! reached out the HN team to update -- can't delete or edit once there are comments.

Apologies, mods, please accept this as approval to detach my top comment from the thread once fixed.

Re: RIP Low-Code 2014-2025

#7
I think this view is really short-sighted. Low-code tools date back to the '80s, and the more likely outcome here is that low-code and agentic tools simply merge.

There's a lot of value in having direct manipulation and visual introspection of UIs, data, and logic. Those things allow less technical people to understand what the agents are creating, and ask for help with more specific areas.

The difficulty in the past has been 1) the amount of work it takes to build good direct manipulation tools - the level of detail you need to get to is overwhelming for most teams attempting it - but LLMs themselves make this a lot easier to build, and 2) what to do when users hit the inevitable gaps in your visual system. Now LLMs fill these gaps pretty spectacularly.

Re: RIP Low-Code 2014-2025

#8

I think this view is really short-sighted. Low-code tools date back to the '80s, and the more likely outcome here is that low-code and agentic tools simply merge. There's a lot of value in having direct manipulation and visual introspection of UIs, data, and logic. Those things allow less technical people to understand what the agents are creating, and ask for help with more specific areas. The difficulty in the past…

I agree. I think that once your LLM hits a baseline level of computer science / programming "understanding" it can pretty easily work with whatever language. Using narrow DSLs and low code platforms could be a great way to constraint an LLM and keep it on the happy path.

Re: RIP Low-Code 2014-2025

#9
Interesting article -- my take on low-code has always been less about how much initial development time the application takes to code, and more about how it can ease the long term maintenance of an application. With AI tooling it is going to be easy for companies to spin up hundreds of internal applications, but how are they accounting for the maintenance and support of those applications?

Think about the low-code platform as a place to host applications where many (not all) of the operational burdens long term maintenance are shifted to the platform so that developers don't have to spend as much time doing things like library upgrades, switching to X new framework because old framework is deprecated, etc..

Re: RIP Low-Code 2014-2025

#10
Great to see your name here, Zack. I think the problem with low-code is that its a catch all that spans between primarily data-storage-and-use work (Airtable, quick base, Filemaker, etc), the primarily app-alternative platforms (retool, Mendix, etc, and the ETL tools.

To me, AI changes the inflection points of build vs buy a bit for app platforms, but not as much for the other two. Ultimately, AI becomes a huge consumer of the data coming from impromptu databases, and becomes useful when it connects to other platforms (I think this is why there is so much excitement around n8n, but also why Salesforce bought informatica).

Maybe low-code as a category dies, but just because it is easier for LLMs to produce working code, doesn't make me any more willing to set up a runtime, environment, or other details of actually getting that code to run. I think there's still a big opportunity to make running the code nice and easy, and that opportunity gets bigger if the barriers to writing code come down.

Post reply on HN