phryneas

I guess you're talking about [Safelisting Persisted Queries](https://www.apollographql.com/docs/graphos/platform/security...) here. Afaik, if you want to use the full integration with the GraphOS platform, you'll need an account with us. The feature is supported on the free account with a rate-limit, and if you would need more, you could go with the "developer" account, which we launched this summer, which is quite reasonably priced and comes with starting credits: https://www.apollographql.com/pricing

That said, Apollo Server is open source and at no point you are locked into our platform - it's just that our platform takes a lot of work away from you, allowing you to manage those whitelists easier. If you want to manage your whitelist yourself, it's totally doable - I just did a quick google search and have come up with more than a dozen articles describing various ways of doing it. Just be aware that there is a lot of coordination between builds and deployments going on, quickly leading to very complex setups - which is why we offer the platform integration in the first place.

So I think the idea was not to lock anyone out of these features, just create a quick pit of success by making the GraphOS integration really easy - but I can see where your feelings are coming from. I hope we can earn back your trust over time!

Many people here tell you "study", others tell you "don't". Both is okay. In Germany, you probably don't need it when going into IT, and in my last job we had many people coming from both perspectives and it was a great mix. What counts in most companies more than a degree is experience - and you probably will not get happy in a company where it is the other way round. One pro for studying is that you can get the time to learn social skills among your peers - I can only say for myself that I really needed that more than anything else. You could of course also do both: become a Werksstudent. In the end, it's all up to you ;) If you are looking for a job now, my old colleagues at Mayflower are always looking for promising people (and you certainly match that description). They are great developers and amazing humans. They have offices in Munich, Würzburg and Berlin, so no matter if you want to stay where you are or get out into the world a bit (which I certainly would recommend), you could work with them. Take a look at https://mayflower.de/karriere/ and even if they don't have a job as Werksstudent out there right now, just apply anyways and see. Oh, and tell them greetings from Lenz - that's me ;)

Also, two-way-data-bindings like just `state.totals` work when you're just re-rendering your whole app on every frame, but as soon as you get away from that, there will always be either some "observing" or "signalling" involved to trigger rerendering of the correct parts of your application. Redux goes the "signalling" way, MobX goes the "observing" way, both have their benefits and drawbacks.

You are right, if all your state is "cache state", then you don't need Redux. But at that point you don't need any state management library and are already searching for the wrong tool from the beginning. If you have actual global state, you'll come very quickly to a point where an actual state management library beats writing your own though, both in developer experience as well as performance.