8 ms·

It possible that they are using the best current tech and what is fashionable right now is actually garbage that would never work for a high volume, easily main

It possible that they are using the best current tech and what is fashionable right now is actually garbage that would never work for a high volume, easily maintainable site.

Mikushi 6y ago
Bingo. Modern web dev has actually made me hate my job, it's a nightmare for no real value. Source: Former Pornhub dev as well.
- cutler 6y ago
  Did I get this right in that you would rather be back at Pornhub where they don't indulge all the whims of modern web dev?
TallGuyShort 6y ago
I'm relieved to see others with this sentiment. I enjoyed full-stack (including front-end) development back when JQuery was just starting to be a thing. Now when I have to dig into these layers where you have an Angular components wrapped inside some React stuff that's all part of an Elm app I just hit a mental block too fast. I don't understand how anyone can reason about their code in such an environment...
- cutler 6y ago
  Angular inside React inside Elm??? Does such a thing really exist or did I miss the hyperbole?
  - TallGuyShort 6y ago
    Angular and React intermingled, yes. Elm in the same project, yes. I'm still unclear on the relationship between what was Elm's responsibility vs. mainstream JS framework's responsibility.
- Nextgrid 6y ago
  When MVC front-end frameworks were taking off (back in the Ember.js days) I imagined a future where you'd have a combined backend + frontend framework and you could interact with data objects from the frontend directly like you'd use an ORM on the backend and all the communication, synchronization, data serialization, etc abstracted away (obviously with security restrictions enforced on the backend). Meteor.js was the only serious attempt at this but it was too different from the status-quo (for most projects, SQL is what you want - MongoDB will bring lots of problems down the line) and never caught on. Instead, 10 years later, we still mostly have a mess of everyone reinventing the wheel and doing most of the API communication, de/serialization, error handling manually. MVC has never taken off on the frontend either despite it being a good fit for most projects in my opinion. We have things like GraphQL, websockets, etc and yet still nothing that takes all of those together and provides a no-BS development experience comparable to backend frameworks like Django, Rails or Laravel.

It possible that they are using the best current tech and what is fashionable right now is actually garbage that would never work for a high volume, easily maintainable site.

Mikushi 6y ago

Bingo. Modern web dev has actually made me hate my job, it's a nightmare for no real value. Source: Former Pornhub dev as well.

cutler 6y ago
Did I get this right in that you would rather be back at Pornhub where they don't indulge all the whims of modern web dev?

TallGuyShort 6y ago

I'm relieved to see others with this sentiment. I enjoyed full-stack (including front-end) development back when JQuery was just starting to be a thing. Now when I have to dig into these layers where you have an Angular components wrapped inside some React stuff that's all part of an Elm app I just hit a mental block too fast. I don't understand how anyone can reason about their code in such an environment...

cutler 6y ago
Angular inside React inside Elm??? Does such a thing really exist or did I miss the hyperbole?
- TallGuyShort 6y ago
  Angular and React intermingled, yes. Elm in the same project, yes. I'm still unclear on the relationship between what was Elm's responsibility vs. mainstream JS framework's responsibility.
Nextgrid 6y ago
When MVC front-end frameworks were taking off (back in the Ember.js days) I imagined a future where you'd have a combined backend + frontend framework and you could interact with data objects from the frontend directly like you'd use an ORM on the backend and all the communication, synchronization, data serialization, etc abstracted away (obviously with security restrictions enforced on the backend). Meteor.js was the only serious attempt at this but it was too different from the status-quo (for most projects, SQL is what you want - MongoDB will bring lots of problems down the line) and never caught on. Instead, 10 years later, we still mostly have a mess of everyone reinventing the wheel and doing most of the API communication, de/serialization, error handling manually. MVC has never taken off on the frontend either despite it being a good fit for most projects in my opinion. We have things like GraphQL, websockets, etc and yet still nothing that takes all of those together and provides a no-BS development experience comparable to backend frameworks like Django, Rails or Laravel.