News for hackers. Stuff that matters.
Re:Urql: a GraphQL client library by methyl on Friday May 31, 2019 @11:25AM (#20061744)
> if you don't want to hit your users with a 500 KB bundle size.

Still I do think if you are building a web application (and not a static site or a blog) it is expected it can take a second or two to load it for the first time. 500 KB bundle is nothing wrong in that case.

Re:Urql: a GraphQL client library by pavel_lishin on Friday May 31, 2019 @11:56AM (#20062059)
> it is expected

It's also expected that my train is going to be late, but we can lament this condition, instead of resigning ourselves to it.

Re:Urql: a GraphQL client library by ctvo on Friday May 31, 2019 @01:28PM (#20063023)
The initial question of why did you make something iteratively better (in terms of size). It's only 20KB. Can be used to stop progress in any field by replacing the keywords.

I would hate to use something built by people with the attitude that compromising on performance when you don't need to is OK because it falls in line with current expected ranges.

Re:Urql: a GraphQL client library by RossDM on Friday May 31, 2019 @12:13PM (#20062209)
18% of the Alexa Top 10K sites grew by 1MB+ from July 2017 - July 18. (source: https://twitter.com/katiehempenius/status/113320912700037939...)

Ignoring the impact of libraries you send to the frontend will lead to death by a thousand cuts.

Re:Urql: a GraphQL client library by methyl on Friday May 31, 2019 @12:25PM (#20062353)
How many of those Top 10k Alexa sites are full-blown web applications that need GraphQL in the first place?
Re:Urql: a GraphQL client library by RussianCow on Friday May 31, 2019 @03:19PM (#20064075)
It might be expected, but I have to admit, there is a certain joy to using a website that loads instantaneously (like Hacker News). Whether or not that joy translates into additional revenue to justify the costs is another question entirely...