News for hackers. Stuff that matters.
Re:Rebuilding our tech stack for the new facebook.com by jdavis703 on Friday May 08, 2020 @02:26PM (#23117868)
The thing is, every place I've worked that was against ORMs or frontend frameworks wound up evolving their own half-documented, half working framework. I find it's easier to spend as much time learning the abstraction as the underlying technology, and then that knowledge can be ported from system to system.
Re:Rebuilding our tech stack for the new facebook.com by freedomben on Friday May 08, 2020 @02:34PM (#23117945)
My experience too. The whole "we don't use a framework" sounds great but it always turns in to some sort of home grown framework that is poorly documented, has bugs, and isn't open source so you can't take it with you when you leave.
Re:Rebuilding our tech stack for the new facebook.com by rhizome on Friday May 08, 2020 @04:03PM (#23118850)
Related: "I don't watch or even own a TV" [watches Netflix/YouTube on a laptop six hours a day]
Re:Rebuilding our tech stack for the new facebook.com by akamia on Friday May 08, 2020 @05:33PM (#23119742)
You also miss out on the community aspect of things. Working with a framework like React means that there is a worldwide community of developers that you can tap into when you run into a roadblock.

It is incredibly frustrating to run into an issue with a home grown framework and have to ask around only to discover that the person who wrote the part you're having trouble with left the company 2 years ago and no one else understands it.