Most of the interesting things in our field can be done with passing json objects around a network and persisting them in whatever way is durable, a bit secure and easy to develop.
What we really need to see is the advancement of computer vision, robotics, and dynamic, goal-based software decision making capabilities. And I suppose battery technology and radio networking too, but that's more about electricity and physics than software.
When that comes, you will see many mundane human tasks go straight to the robots, and hopefully every family will be permitted to own one (politics is all about limiting people from doing things for sane prices, right?)
If a family's robot could till the land, grow food, cook it, synthesize medicines, build a home, serve as physical security and defence, play games for entertainment, transport the family from place to place, etc etc... then quickly the only world industry still in existence would be semiconductor manufacturers :)
The "no-code" environments from yesteryear were really, really good, and motivated "non-coders" accomplished amazing things with them. Hypercard, for example.
But even with Hypercard, at some point you needed to write code if you wanted to go beyond the happy path envisioned by the tool developer. And I imagine the new "no-code" tools will have similar limitations. And then when the "no-code coders" get bored of playing with those toys, will hand it off to the programmers to extend and maintain.
Why don't we have a library stack where I can define some datatypes and get database migrations, CRUD REST endpoints, and a basic editing web UI, in a maintainable language where I can understand where all that's coming from and incrementally start customizing? I'm pretty sure I've implemented all the pieces you'd need, scattered between the codebases of my last three or four employers: in a language with a decent record system it should be a one-liner to build a set of HTTP routes for a given datatype, not through invisible magic but through a function call that works by plain code.
But it's in no-one's interest to package that up to release it. A traditional business doesn't produce new systems often enough to make a general toolkit. A consultancy does new systems but has no need to make them maintainable (thus Rails, which does all the automatic spinning up but doesn't have the comprehensibility to be reliable). And there's no money in selling libraries to developers, partly because developers would rather do it themselves but mostly because a library you have to buy will never be popular enough to get talented developers using it. Occasionally a huge corporation decides it's worth making a framework for their in-house applications, and even more occasionally they find it worth publishing to the outside world, which is an astonishingly inefficient process for our whole industry to depend on.
This sounds like Django (models+migrations, views for CRUD/REST (maybe with another library for automatic generation from models), admin pages for editing, and in python).
And, one can annotate Python3 to make it typed, so things might improve.
This is why no-code solutions have never become popular.
It's win-win BS. That's why it keeps going. The reality of its economy comes in delay long enough (e.g. 5 years with no profit, keep funding) that every body is detached from economic principle. With printed money lately .. oh the collapse might not come at all, you can be alive in coma for a decade as long as oxygen keeps pumping into your dead body.
This is not a trivial field, contrary to what some are trying to claim.
This is a completely absurd comment and notion. There’s talented people all over the world who don’t need $200k salaries and also simply get things accomplished without whining about not being able to use whatever tech is popular on HN at the moment.