The problem isnt the means of production, its the robustness of the outcome in the real world (aka hostile environment). If your LC environment includes components and runtimes that will survive, then you might be ok. For example, ita one thing to have an LC app that takes in, say, an mailing address, but quite another to expect that widget to handle users typing in addresses half baked, or across multiple countries, or while wearing gloves, or if you have not 100 users but 100,000, or any other of the bazillion things that happen in the real world.
If the environment is under tighter control, say, an internal intranet app, or tye LC runtime provides high quality widgets and plumbing that handle scale, protections, etc, then LC can be awesome.
The nearest analogy I can think of is using Squarespace vs rolling a website. Squarespace is great, and has all kinds of widgets, and is fab, until it suddenyl isnt and you need to add custom code, whereupon it all grinds to a halt. Rolling by hand is insane, slow, crazy, until you realize that its the only way to get what you want on your terms. Horses for courses.
If the environment is under tighter control, say, an internal intranet app, or tye LC runtime provides high quality widgets and plumbing that handle scale, protections, etc, then LC can be awesome.
The nearest analogy I can think of is using Squarespace vs rolling a website. Squarespace is great, and has all kinds of widgets, and is fab, until it suddenyl isnt and you need to add custom code, whereupon it all grinds to a halt. Rolling by hand is insane, slow, crazy, until you realize that its the only way to get what you want on your terms. Horses for courses.