As someone who loves all the non-AI portions of Graphite (the CLI and the reviewer UI) should I be worried about this acquisition? Or will the CLI and Reviewer Ui continue to be be maintained and improved?
Forgive some ignorance, but we use Graphite at work, and I don't dislike it or anything, but I haven't really been able to see its appeal over just doing a PR within Github, at least if you exclude the AI stuff.
What do you like about the non-AI parts? I mean it's a little convenient to be able to type `gt submit` in order to create the remote branch and the PR in one step, but it doesn't feel like anything that an alias couldn't do.
the stacked changes support, for me, was an absolute game changer. the auto rebasing, etc, is -really- nice.
i found it especially useful for Gitops type stuff where you have to make lots of little PRs
> He's also implying that Rails does not use web sockets to communicate with frontend which is not only wrong it should be evidently wrong to anyone who built a Rails app in the last 3 years
Where is the article saying that? I only see " Those things are possible in Rails and Laravel, but they take a bit more effort to set up." which is a very different (and more nuanced/personal take) then what you're stating.
I wish someone would make a keyboard with keycaps that are like 80% size. I think that would make it much easier to hit some of the keys that are further away.
> glove80 has far and away the most comfortable thumb cluster for my hands
If I'm reading your reply further down the page right then you only use two of the 6 keys. Is that right? For me, I think I'd want to use at least 4 or 5 keys in my thumb cluster before I could call it comfortable.
One part of the answer to that is a land value tax. That way the “vultures” won’t be able to simply sit on the property waiting for it to appreciate before selling it.
reply