3 ms·

Most of the web is just CRUD apps, be it php, rails, cgi calls, <your favorite language>. And no one is saying get rid of JS front end stuff, it should be used

by w-ll 4y ago

Most of the web is just CRUD apps, be it php, rails, cgi calls, <your favorite language>. And no one is saying get rid of JS front end stuff, it should be used to enrich and not hinder. > drop the files in an S3 bucket If you have a completely static site you still shouldn't host of s3, that's a big no no. S3 isn't a CDN; you want a CloudFront or something else in front of that. But as soon as you need something more your gonna get lost or locked in.

arvinsim 4y ago
> And no one is saying get rid of JS front end stuff, it should be used to enrich and not hinder. Having separation between the HTML on the server side and the JS on the frontend side is exactly why React become popular. Personally, I don't want to go back to the PHP+jQuery days. I want one language and one framework to handle both HTML and JS interactivity.
- w-ll 4y ago
  > Having separation between the HTML on the server side and the JS on the frontend side is exactly why React become popular. But did they really. Cuz now i see .jsx files with sql calls, adding in static js and css, and logic with mixed html in... Its honestly blowing my mind how we got to this point. We all agreed biz logic, and view should be separated. and that html, css, js should also be in sperate files. and then .jsx or the like came along and merged them all back together in some of the ugliest code ive seen in years.
qudat 4y ago
> Most of the web is just CRUD apps I disagree, pages for web apps don’t just CRUD one entity, they mix and match many entities in complicated ways. Also, I was referencing rails auto generated crud pages where there’s a single form and a single entity table. If that’s all that’s required then kudos but rarely has that been true for the companies I work for. I wish it were true.
- w-ll 4y ago
  Mixing and matching a C(reate) or U(pdate) api call into a single request is exactly why its better. Logic can be checked, verified, confirmed, denied and rolled back. Multiple entities with multiple endpoints are harder, if not impossible to enforce.
oneeyedpigeon 4y ago
> Most of the web is just CRUD apps And most of that doesn't need to be.

by w-ll 4y ago

arvinsim 4y ago

> And no one is saying get rid of JS front end stuff, it should be used to enrich and not hinder. Having separation between the HTML on the server side and the JS on the frontend side is exactly why React become popular. Personally, I don't want to go back to the PHP+jQuery days. I want one language and one framework to handle both HTML and JS interactivity.

w-ll 4y ago
> Having separation between the HTML on the server side and the JS on the frontend side is exactly why React become popular. But did they really. Cuz now i see .jsx files with sql calls, adding in static js and css, and logic with mixed html in... Its honestly blowing my mind how we got to this point. We all agreed biz logic, and view should be separated. and that html, css, js should also be in sperate files. and then .jsx or the like came along and merged them all back together in some of the ugliest code ive seen in years.

qudat 4y ago

> Most of the web is just CRUD apps I disagree, pages for web apps don’t just CRUD one entity, they mix and match many entities in complicated ways. Also, I was referencing rails auto generated crud pages where there’s a single form and a single entity table. If that’s all that’s required then kudos but rarely has that been true for the companies I work for. I wish it were true.

w-ll 4y ago
Mixing and matching a C(reate) or U(pdate) api call into a single request is exactly why its better. Logic can be checked, verified, confirmed, denied and rolled back. Multiple entities with multiple endpoints are harder, if not impossible to enforce.

oneeyedpigeon 4y ago

> Most of the web is just CRUD apps And most of that doesn't need to be.