Re:Why not use GraphQL?
by joelbluminator on Saturday November 07, 2020 @12:20PM
(#25016475)
Unfortunately he's somewhat right. Not because the interviewers necessarily know wtf they're talking - they probably don't. But going against the current hype in an interview can only hurt your chances. Liking something like GraphQL, or React, or Framework Of The Month can't really hurt you even if your interviewer doesn't like it. But not liking it can be a real issue! I would suggest at least staying neutral on the current hype stacks in an interview. It's like debating religion - don't go there...
[ Parent
| on HN ]
So not liking the tools your employer uses makes you less appealing as a candidate?
Also, React is a hype stack now?
Almost anything FB (and FAANG) builds is hyped to infinity. Everyone drank the cool aid on this one.
React and GraphQL are extremely hyped. People build static HTML pages with React because... React. People use GraphQL APIs because... GraphQL.
These days the first thing every JS developer I've seen asks is: can we use GraphQL (which in fact they mean Apollo)?
I'm not saying it doesn't have its use-cases and merits, but it's very much hype tech.
Edit: typo
You would expect to be able to have a discussion of the pros and cons, and recognition at the least that other approaches are viable.
> React is a hype stack now?
Yeah, kinda. You definitely need some sort of front end framework, but I feel like there should be something better than react. I use react every day and it’s fine, but I’m waiting for something else to come and take it’s dominant position.
Re:Why not use GraphQL?
by joelbluminator on Saturday November 07, 2020 @05:18PM
(#25020122)
Idk, a lot of the back office apps I build are basically glorified forms with some content pages / dashboard. You really don't always need a framework.
Re:Why not use GraphQL?
by aabbcc1241 on Monday November 09, 2020 @06:53PM
(#25041386)
Try svelte, see if you like it