4 ms·

If I need to call Rails services and methods from ERB, then it isn't frontend :) It's comparative to hiring a front-end and putting them to work on .php files.

If I need to call Rails services and methods from ERB, then it isn't frontend :) It's comparative to hiring a front-end and putting them to work on .php files. It's so far back in the past, that it becomes degrading, and you start feeling regression in front-end skills.

powersurge360 5y ago
Web dev seems to be headed in three directions imo: 1) The old style, where the server owns the routing but can cede control over html to the frontend for discreet applications. Always cedes control of JS and CSS to the frontend. 2) A fully separated frontend and backend application that talks to one another over REST or GraphQL 3) A very javascript-light frontend that uses a technology like LiveWire, LiveView, or Hotwire to render on the server but push reactively to the frontend I think any is fine and each have their merits. I imagine that #3 is the one that is most likely to supersede #1 as it's a direct evolution. But I would think that it's a bit gatekeeping to tell someone whose whole job is HTML templates, javascript, and CSS that they are No True Frontender.
erulabs 5y ago
There was a major release of PHP8 2 months ago. To add to that - JavaScript was invented in 1995. PHP, "so far back in the past", was invented in 1994. It's only regression in the exact language and framework you wanted to use. Certainly not "front-end skills". I worked at a company where our iOS team refused to make multiple API calls for any given view. They wanted 100% of the data for _any_ given activity the user could do to be a single call, formatted how they wanted. I pushed very hard to let that team go, but failed, although I do still chuckle at the horrific reviews the app gets for general bugginess. It's absolutely mind blowing that people getting paid 150k say "well I'll touch that code but _never_ that other code". I hate to paint with broad brush strokes, but I never once saw that attitude from a non-college graduate. Loathed to use the word "entitled", but holy cow.

powersurge360 5y ago

Web dev seems to be headed in three directions imo: 1) The old style, where the server owns the routing but can cede control over html to the frontend for discreet applications. Always cedes control of JS and CSS to the frontend. 2) A fully separated frontend and backend application that talks to one another over REST or GraphQL 3) A very javascript-light frontend that uses a technology like LiveWire, LiveView, or Hotwire to render on the server but push reactively to the frontend I think any is fine and each have their merits. I imagine that #3 is the one that is most likely to supersede #1 as it's a direct evolution. But I would think that it's a bit gatekeeping to tell someone whose whole job is HTML templates, javascript, and CSS that they are No True Frontender.

erulabs 5y ago

There was a major release of PHP8 2 months ago. To add to that - JavaScript was invented in 1995. PHP, "so far back in the past", was invented in 1994. It's only regression in the exact language and framework you wanted to use. Certainly not "front-end skills". I worked at a company where our iOS team refused to make multiple API calls for any given view. They wanted 100% of the data for _any_ given activity the user could do to be a single call, formatted how they wanted. I pushed very hard to let that team go, but failed, although I do still chuckle at the horrific reviews the app gets for general bugginess. It's absolutely mind blowing that people getting paid 150k say "well I'll touch that code but _never_ that other code". I hate to paint with broad brush strokes, but I never once saw that attitude from a non-college graduate. Loathed to use the word "entitled", but holy cow.