[openlowcode]

I know what you mean. While web is unavoidable in some area for the 'instant deployment' benefit it brings (in consumer internet...), it lacks in my opinion a solid architecture fundation (separation of business data and layout...), and we pay a high price for this (costly development, high cost of obsolescence...). So I prefer to avoid web development when I can.

Also, many development environments (not only web) are not keen with 'medium skill' developpers: the architecture is too complex that it is a mess just navigating around, and it requires self discipline and experience to organize your development. There should be, in my opinion, a 'safe place' for people whose job is just to transcript business requirements into working code without requiring extra 'architecture' skills. Most IT departments of companies have this 'medium skillset' population, and as a result, there is a lot of waste and drama.

With that in mind, I spent around 1 year of my private time designing a low-code framework to provide enteprise IT developers with a 'medium skillset' an efficient tool to develop business apps. This is fully open-source, so do not hesitate to have a look and get involved ( https://openlowcode.com/ )

[tcbasche]

> requires self discipline and experience to organize your development

Almost like developers with self-discipline is a bad thing...

I feel like you've just had bad experiences and have tarred web dev with the same brush. Either that or tried to conflate enterprise development with web development. Those things are not the same.

[MetalGuru]

Instant deployment and obsolescence is the same sentence. Do you not see the contradiction? Also, how on earth does the web not have a separation of concerns between business logic and UI?

[openlowcode]

Hi,

I am not sure what your point is. Instant deployment is an advantage of web architecture: you have nothing to do on the user device for them to use the new version of your software (barring some rare issues with browser cache).

On the other hand, so far at least, a web application does not age so well at the timescale of enterprise software (an application will live 10-30 years in a company). So we have an obsolescence problem often, i.e. a 5+ years old application will need to be rebuilt to use more modern technology, often at a high cost.

Originally, web architecture mixed in web pages presentation and business data, a result of an hypertext architecture being used for transactional software it was not aimed at at the beginning. Sure, there have been billion of dollars of investment in web technology since then and a lot of things have improved. However, I have the strong feeling things are still messed-up, especially for developments 'in the wild' for team who do not have strong architecture skills.