91–100 of 113 posts
Earlier quoted context omitted.
Take a look at Apollo. https://github.com/apollographql/apollo-client
Thanks for suggestion. The back-end is written on Go, the client talks to it via web-socket. I am wondering if Apollo can handle that.
Earlier quoted context omitted.
If anywhere is the place to find others who miss the days of small HTML pages with CSS, especially for reading, HN is that place. :)
After reading my ceremonial 1000th testimony about how HN user prefers sites with less CSS I'm about done with it though. We get it! Engineers are proud of how little they care for white space and colors! Can we talk about something else in the top comments of any page about website design?
That's not what people here are saying, though. Indeed, even your parent comment said how he misses a small HTML pages with CSS. Most engineers would be totally fine with HTML and a modest payload of nice, modern CSS styling, a perhaps a small bit of non-required progressively enhancing JS.
Our problem is with huge JS frameworks used in sites that aren't actual web applications (e.g., Gmail), but rather web sites (like news sites). And I say this as someone who has primarily made my living the past 5 years as a "frontend engineer" (ie, JS programmer). JS frameworks can be wonderful for actual web applications, but they're way overkill for documents online for reading (and also make the experience worse for the reader).
Oh, and we also hate of dozens/hundreds of kb of unneeded font downloads.
Also, for the record, I'm a big fan of (appropriate use of) white space and color. I definitely come down heavily on the side of bettermotherfuckingwebsite.com (vs motherfuckingwebsite.com).
Is anyone else here writing their GraphQL queries / REST calls in their components? IMO coupling the data layer with the presentation layer is a terrible idea.
Earlier quoted context omitted.
As a standalone all-by-myself indie developer I was skeptical of GraphQL when it first appeared, but later I discovered it is much easier to develop APIs for my own consumption with GraphQL. The basic GraphQL boilerplate seems bad, but is actually fun to write and makes total sense. And once you have the structure in place it is super easy to add functionality. Plus bonuses if you have more than one database or are m…
> Plus bonuses if you have more than one database or are mixing data from your database and external APIs in your backend responses. You can easily do that with a RESTful API too.
Do you guys think it makes sense for a newspaper to use React for the frontend? I would think React might make sense for realtime dashboards and similar webapps. But does it make sense for displaying articles, navigation and ads?
No it doesn't. We (as a marketing tech company) deal with major publishers all the time and come across all kinds of ridiculous and complicated tech used to show a basic article when a simple static website would be easier and faster at this point.
It's a lack of good talent, resume-led motivations for choosing technology and overall poor vision in execution by CTOs and management.
Earlier quoted context omitted.
> Plus bonuses if you have more than one database or are mixing data from your database and external APIs in your backend responses. You can easily do that with a RESTful API too.
You can do anything with any programming language, framework or design pattern.
Is anyone else here writing their GraphQL queries / REST calls in their components? IMO coupling the data layer with the presentation layer is a terrible idea.
They're not writing queries/API calls inside components. They're defining the components' data requirements alongside the components.
Earlier quoted context omitted.
Seems like it's all you ever see here lately. I really should avoid reading HN comments on new web technologies.
I wish there were some way to avoid being subject to resume driven development when I'm on the internet. Alas, it's not to be, because instead of taking a step back and asking "do we need this" we get webdevs asking "how can I force fit the latest shiny bauble into my professional CV." And we end up with react graphQL node AWS kubernetes docker rube goldberg machines pumping tens of millions of bytes of data and bill…
I've looked at GraphQL a number of times. Does anyone have any practical examples of integrating it with backend(s), APIs, and/or specific databases? So instead of "we use GraphQL, much love" + basic example and how it looks on React - a "here's how we take that structure and resolve it and return it." Because that structure looks amazingly sweet - but if in the background it's requiring circles of work, work and rew…
A good GraphQL backend resolves the graph into query results efficiently, rather than just field by field. But that does take a but of getting used to....
Do you guys think it makes sense for a newspaper to use React for the frontend? I would think React might make sense for realtime dashboards and similar webapps. But does it make sense for displaying articles, navigation and ads?
React is a view library and it does this very well. It doesn't have all the bells and whistles like Angular and it's plethora of helpers ($HTTP etc) or complex dependency injection. I would argue it's the perfect candidate for this purpose. What does a news site need? Articles? Ads? Basic nav? Angular or Ember would be overkill. And with Redux, it's very easy to think about complex UI state. My only complaint with Re…
It's a 3kb React alternative with the same API.