Hacker News new | ask | show | jobs
by tediousdemise 1593 days ago
These comments all present valid reasons why low-code is usually a nightmare. To me, the most egregious offender is vendor lock-in: https://en.wikipedia.org/wiki/Vendor_lock-in.

It's all fine and dandy if you found a low-code solution that works for you, as long as you're comfortable paying a premium to pigeon hole yourself with that solution for the unforeseeable future, with no guarantees that you won't get royally screwed by some combination of planned obsolescence, feature deprecation, or the success of the company whose low-code product you are using.

1 comments

Vendor lock-in is not always a problem. Imagine that you have a situation where you can either throw one engineer at it to create a custom solution or buy an existing one that locks you into their service offering? What would you choose? It is not always clear-cut, but it is better to buy simply because employees are not permanent in most cases. After they leave, there will be zero support.
If you treat them right, why would they leave? You are just planning for abuse in this case, which no amount of tooling will make okay.