consolenaut

6 ms·

1.
Shipping Progressive Web Apps everywhere(medium.com)
52 points by consolenaut 6y ago|8 comments
2.
by consolenaut 6y ago
True, and admittedly I've only cast a cursory glance over Relay to keep track of where it is every now and again so maybe its unfair of me to write it off quite so quickly. But I think you're also right about the learning curve be
3.
by consolenaut 6y ago
I do on the whole yes, its not something I rave about unreservedly the same way I do about styled-components for example, but its still a tool I'd opt for on projects that actually have a need to do GQL stuff. Its like your favorite sc
4.
by consolenaut 6y ago
I'm doing a big Apollo/GraphQL piece for the BBC for a lot of the same reasons OP lists, and have run into pretty much all the same issues with Apollo that OP has. Its rough because Apollo does so much for you, its wonderful, but
5.
by consolenaut 6y ago
This is true, but I've found it far more common that a predecessor at the company I'm at wrote the code and isn't around to support it anymore. For simple components it's no biggie, but for non-trivial components it can
6.
by consolenaut 6y ago
I was just thinking "Huh, I used to work with someone who went to work for Massive" until I realized you were the same someone :) Interesting to hear how the Massive/Ubi editorial relationship works from the inside
7.
by consolenaut 7y ago
I think you're right about a general move towards a Git monoculture (as opposed to a GitHub one), but there are dozens of great Git repo hosting/collaboration companies - GitLab, Bitbucket & SourceForge to name a few of the bi
8.
by consolenaut 8y ago
As someone coming from a traditional strict separation-of-content-and-style background and now convert to Styled Components, CSS-in-JS felt unnatural to me when I first encountered it. The problems with styles in large applications are well