Hey folks! Just found this community from a post on a Discord about low profile keyboard. My name is Kiril and I live in Stockholm, Sweden. I like developer tools, build systems, programming languages and combinatorics / optimisation. I have worked / toyed with Go, Rust, Clojure, Bazel build, making custom keyboards. Not too long ago I worked at a company called Tink, focused on developer tools - making build times faster (cache-able, remote etc) locally and in CI. In general, making creating a tighter feedback loop for developers. This year I co-founded a company with the goal of making the developer life better. It is somewhat unpopular to question Git but we wanted to explore and experiment with development workflows that are not constrained by it. You can check out and try what we have so far here https://getsturdy.com/

Also in sthlm, enjoys rust, and just building my first keyboard :) Sturdy looks neat!

this is pretty cool Kiril! How does the syncing happen without git? 🤔 cc @Geoffrey Litt as well who may like this

We do a 2-way synching between a directory on the dev machine and the backend. Changes are eagerly synced and the versioning and collaboration on code happens through the web application. Here is a recent post about our ideas as well as high level implementation https://getsturdy.com/blog/2021-08-18-unbreaking-code-collaboration

Welcome Kiril! Sturdy looks awesome! I've been thinking/looking for similar solutions. I've explored improving development on a phone or tablet before, and I think replacing git with live sync will be necessary to properly allow that. It doesn't seem like your company is focused on mobile/tablet workflows yet, but I'm glad to see innovation in this space!

👋 @André Terron are you already using something for a development from tablet workflow?

I tried a bunch of different apps. Usually when I want to code from the tablet I'm not doing any heavy lifting, so what worked the most for me was using observablehq.com, or Coda by Panic (which is being discontinued) to just play around with some plain html/js/css or svgs. If you're interested, I can get into more details on what apps I tried and why they didn't work for me.

@Kiril Videlov I'm curious what the history granularity is? (also JFYI i was the SRE TL for CitC @ google and am SO glad to see this exists, even if i want open source client code and a decentralized approach eventually.)

Hey @heartpunk! The granularity is more or less every save action. We had a FUSE implementation before but that was replaced with recursive file watching.

ohhhh, ok, so that's what CitC did. i thought y'all were going a level more granular than that and that made me super excited, but i see it is not that. we also were snapshot based fwiw. i'm so glad to see all the tooling you're building out around this service though, google never went that far and i kind of doubt they will (unless you shame them into doing so). any thoughts re open source clients? also I looked at your graphql API docs and was surprised to see there wasn't an obvious way to either read or write a file?

@heartpunk Sophie, I think to be more granular than that we would need to integrate on the editor level, as opposed to file system level. Which is interesting for sure, with things like the language server protocol. You are right that the graphql api is not the full picture - it is at this point our front end API. The computer (agent) - backend communication is not on the graphql api, yet. I think we will at some point provide the client sources, we have just not gotten to it yet - doing open source is a special type of challenge.

yes! absolutely, i'd love to chat.