4 ms·

RAD for the web ;) ? Forget about it. Rewriting everything (front-end-wise) is a constant source of income for frontend "developers".

iostream25 4y ago
It's more like: there's no standard "backend as a service" API, so it's "vendor lock-in city" Your complaint has been largely addressed by UI component libraries, starting with React and Vue and now Svelte. One can choose IBM's "carbon" library, or the Google "material UI" library and it's numerous derivatives... If you wish to be snarky about frontend developers not being "real" developers, then I will duly note that you are chiming in on a "backend as a service" promotional thread, and noting that this concept is fine but proposing that frontend developers are the problem, not the notion of Backend-as-a-Service being any issue, producing vendor-lockin. If CRUD is so-well defined, standardize such a market sector service. I agree that much of web-development is CRUD. Much of desktop and mobile GUI development is wiring. Much of programming is instantiating and connecting pre-written code modules. The details matter. No-Code exists, but look where that leaves you in the app development life-cycle...
iostream25 4y ago
The true reality that precedes your complaint: The world wide web was created as a remote-folder document-browsing application in which an index-page told you of the contents of a folder, etc. One still speaks of a "web root" folder etc. It wasn't designed as a FRP state-machine, or as a 2-way-bound GUI. Before the XML Http Request, there was only loading new resources, so the notion of dynamically updating a page UI was entirely dependent upon clicking something and waiting for a new page to load with the hopeful results of your posted form data or whatever, reflected in the UI, IF the developer was kind enough to have done so. This situation created the complicated frontend situation of today as it became apparent that the Web would be a general client-server application UI
steve_taylor 4y ago
Rabid Application Development

iostream25 4y ago

It's more like: there's no standard "backend as a service" API, so it's "vendor lock-in city" Your complaint has been largely addressed by UI component libraries, starting with React and Vue and now Svelte. One can choose IBM's "carbon" library, or the Google "material UI" library and it's numerous derivatives... If you wish to be snarky about frontend developers not being "real" developers, then I will duly note that you are chiming in on a "backend as a service" promotional thread, and noting that this concept is fine but proposing that frontend developers are the problem, not the notion of Backend-as-a-Service being any issue, producing vendor-lockin. If CRUD is so-well defined, standardize such a market sector service. I agree that much of web-development is CRUD. Much of desktop and mobile GUI development is wiring. Much of programming is instantiating and connecting pre-written code modules. The details matter. No-Code exists, but look where that leaves you in the app development life-cycle...

iostream25 4y ago

The true reality that precedes your complaint: The world wide web was created as a remote-folder document-browsing application in which an index-page told you of the contents of a folder, etc. One still speaks of a "web root" folder etc. It wasn't designed as a FRP state-machine, or as a 2-way-bound GUI. Before the XML Http Request, there was only loading new resources, so the notion of dynamically updating a page UI was entirely dependent upon clicking something and waiting for a new page to load with the hopeful results of your posted form data or whatever, reflected in the UI, IF the developer was kind enough to have done so. This situation created the complicated frontend situation of today as it became apparent that the Web would be a general client-server application UI

steve_taylor 4y ago

Rabid Application Development