maktouch

8 ms·

31.
by maktouch 8y ago
Hmm, our API is pretty big and we never had an issue where GraphQL couldn't solve it ( https://player.me/api/graphiql ) > I don't see how I can implement complex object hierarchies that are not rigid. I&#x27
32.
by maktouch 8y ago
I like the abstraction of patches, because some of our projects still runs SVN and HG, and because we're all on Phab, we're all using the same flow. We actually don't feel any urge to move to git at all (it's probably go
33.
by maktouch 8y ago
I love buildkite and I wish they had better pricing model -- we would definitely love to pay for more. Pros of buildkite: - Very powerful. Plugin system is amazing and easy to extend. We wrote our own buildkite-docker executor, and I merged
34.
by maktouch 8y ago
We run buildkite-agents in its own kubernetes cluster, and the nodes are pre-emptible on Google Cloud so 30% of the price and it dies everyday, so it gets cleanup automatically
35.
by maktouch 8y ago
I don't find it as pretty as Phabricator's "Merge branch 'dev-hello' into 'master'" Phabricator makes it so that the squashed commit summary is the summary of the diff (merge request)
36.
by maktouch 8y ago
We moved from Gitlab to Phab a year ago. Context: - One of the main repo is a monorepo in Git with over 40~ services - We have a lot of smaller repos that are outdated or depreciated. - We have an extensive pipeline that builds Docker image
37.
by maktouch 9y ago
Could you explain this? We use node everyday and I don't understand what you mean.
38.
by maktouch 9y ago
How does it work with ingress? Does it ship with its own ingress like istio? We tried istio a while back and it was too slow and hungry. Reverted back to no service mesh and it worked fine. I'm gonna be trying this next!
39.
by maktouch 9y ago
Wow that's weird. We actually did the inverse, from AWS + Kops to GKE. In our case, the cluster just stopped working suddenly. Been using GKE for over a year now. No issues at all.
40.
by maktouch 9y ago
Right now: - Self hosted Gitlab CE - Gitlab runners in pre-emptibles nodes with autoscaling Future (almost done, still in testing phase): - Phabricator (for git, code review and issues) - Jenkins ("lightweight" CI, more details at
41.
by maktouch 9y ago
We're moving away from gitlab because the performance is too much to bear. We're hearing "aaaaaarg I really hate gitlab" a few times a day. The pipeline pages takes 7 seconds to load. It's really bad. We stopped usi
42.
by maktouch 9y ago
We're using Apollo v1 and tried the upgrade to v2 a few weeks ago. It was hard and buggy to replicate what we had (subscriptions, batched requests, polling requests). We reverted to v1 in the end because if the bugs and the complexity.
43.
by maktouch 9y ago
The kind of query where it fails (and where it especially hurts) is queries like `getLatestNotifications`. It would be a lot of cruft added to prevent this kind of bugs. So, yes, you know which one is bad, but it's not a query that&#x2
44.
by maktouch 9y ago
I really like the Apollo stack, but if you're thinking of using it in production right now, you should wait a little! There's a massive bug where if your graphql outputs 1 small error, the whole component does not get loaded. Imag
45.
by maktouch 9y ago
> Another problem GraphQL hasn't tackled (afaik) is polymorphism. You can say "hey give me this person" or "give me this company", but what if you want a customer that can be either a person or a company? http:&
46.
by maktouch 9y ago
I agree that subscriptions are a work in progress, but how is mutations is a work in progress? Pretty sure it's defined and it works pretty well.
47.
by maktouch 10y ago
Ah! Finally found the culprit :-) I run my fleet of runners in pre-emptible instances on GCP (they die after 24h). I forgot to pin the version in my startup script, so all it did was a simple apt-get install gitlab-ci-multi-runner. For some
48.
by maktouch 10y ago
Pretty sure no one really doubted jQuery power.. it's about maintainability, state management, modularization. If you tinker hard enough, you can achieve those with jQuery, but it'll never be as easy as React. Also, your site does
49.
by maktouch 10y ago
That's weird. Cookies are part of the HTTP standard, no? That means iOS would be the one that is not respecting the RFC. Kinda like Safari throwing exceptions when you're trying to access localstorage in incognito.
50.
by maktouch 10y ago
That's deprecated :(
51.
by maktouch 10y ago
We started nginx-ingress as a deployment, and we converted it to a DaemonSet: - We rarely deploy new versions of the ingress controller - We can't (or don't know how to) choose in which nodes the pods will go. If I make a deployme
52.
by maktouch 10y ago
I found this last week and I'm very impressed because it solves a lot of the problems we had with existing ingresses. I really like how you guys decided to do your own 3rd party manifests instead of using annotations. I'm going to
53.
by maktouch 10y ago
I've been running K8S for the past 6 months. So far, so good. Helm helped us a lot in our workflow. A lot of trial and errors, but to answer your points, this is what we're doing so far: > * Where do you store the YAML manifest
54.
by maktouch 10y ago
It's really interesting to see that you're using Cassandra for this. IIRC, Cassandra was created by Facebook for their messaging, and realized that eventual consistency was a bad model for chat, so they moved to HBase instead. (so
55.
by maktouch 10y ago
I love gitlab! We just deployed our review app deployment to Kubernetes (create a new subdomain in route53, create a new namespace in k8s, create all kubernetes manifests in that namespace, create ingress manifest, boom!). Here's some
56.
by maktouch 10y ago
I think it really depends on what you work on. > Almost a whole decade ago we had pretty simple and straight forward build patterns for frontend. a decode ago, we didn't really build web apps like today though. The browser landscape
57.
by maktouch 10y ago
React can be used without JSX like Mithril is doing. In fact, pretty much all the JSX compiler does is convert those to React.createElement()..