5 ms·
"GraphQL will completely replace REST in the coming years." What the hell? Where's your source for that? She says the solution is that product managers should
by elliotec 10y ago
"GraphQL will completely replace REST in the coming years." What the hell? Where's your source for that?
She says the solution is that product managers should be able to make an app do whatever they want to do and skip the engineers. This makes her sound very inexperienced. Don't you think we would have gotten there by now if possible?
So her new mission is to create a drag and drop interface that can build every app every company would ever want, and she doesn't have a clue how to do it "but probably with React." Nice.
Does she think the only thing requiring code are websites? Does she think we can just drag and drop Google search algorithms and space shuttle software into existence?
This almost seems like a troll article.
- cortesoft 10y agoI am pretty sure it is satire. It has to be, right?
- deleted 10y ago[deleted]
- jodrellblank 10y agoSo her new mission is to create a drag and drop interface that can build every app every company would ever want, and she doesn't have a clue how to do it "but probably with React." Nice. Solve coders recreating the same things over and over, by coding the next rapid application development environment. Sorry, sorry, the first RAD. Of course.
- rakoo 10y ago> Does she think we can just drag and drop Google search algorithms and space shuttle software into existence? To be honest, I'd say a good 80% of websites are a variation around the same theme: authenticate a user and let them CRUD resources following a pretty standard access model. I guess OP would like to see an easy solution for all these websites that does 80% of the job of such an application, and let the user configure the fine details of how resources are displayed rather than code how layers are going to interact between each other, even though this interaction is pretty much already known. Of course, you won't be able to do that "with React", much like you won't be able to do that "with MongoDB" only, that was a bit short-sighted. And of course a generic stack won't be able to scale to the size of Twitter or Instagram or Reddit. Which means that engineering time should be spent on scaling, not on gluing your Express application with your React frontend for the n-th time.