3 ms·
It's a combination of resume-driven development and premature optimization. The former doesn't need explaining but the latter can be explained as developers be
by Nextgrid 6y ago
It's a combination of resume-driven development and premature optimization.
The former doesn't need explaining but the latter can be explained as developers being concerned about requiring the benefits of GraphQL in some uncertain future and decide to include it from the start, even though in most cases they end up never actually reaping the benefits while still being plagued by the extra overhead of using that technology.