Post AZUqWJNa2vhqptSSBs by jerod@changelog.social
(DIR) More posts by jerod@changelog.social
(DIR) Post #AZUP9KPrKOo0d2L916 by changelog@changelog.social
2023-09-06T11:48:45Z
0 likes, 0 repeats
“Git is not good enough. You should never be satisifed with the state of the art if it's killing you. And right now the start of the art is killing us.”Steve Yegge: https://youtu.be/EReooAZoMO0
(DIR) Post #AZUPatJDhlx8fLNTRA by zorn@jawns.club
2023-09-06T11:53:56Z
0 likes, 0 repeats
@changelog I would not say it’s killing us. But I would say we can do better.
(DIR) Post #AZURwXr8LaY4PSh3ya by tshirtman@mas.to
2023-09-06T12:20:16Z
0 likes, 0 repeats
@changelog git still feels like the least worse option, but it’s true i never worked at google.This sapling thing looks like it can be used with git repos, maybe i’ll give it a shot and see what it does. Though we don’t have that many repos, and i almost never need to interact with repos outside my team, so i have like 10 repos i care about and less than 4 i interact daily with. I think it’s still true that not every one is google and so not everyone needs the tools google has to manage that.
(DIR) Post #AZUi5OVO54xbHWlOhE by thedoubl3j@fosstodon.org
2023-09-06T15:21:07Z
0 likes, 0 repeats
@changelog git doesn't force me to make that many repos though? the argument that I see being made (I could be misinterpreting this) is that there are so many repos git has a hard time managing those but the tool didn't force that upon the user...management of code did, right?
(DIR) Post #AZUqO7sAwYKopfriLo by changelog@changelog.social
2023-09-06T16:54:03Z
0 likes, 0 repeats
@thedoubl3j seems he’s using repo count as a proxy for overall project scale ¯\_(ツ)_/¯
(DIR) Post #AZUqWJNa2vhqptSSBs by jerod@changelog.social
2023-09-06T16:55:36Z
0 likes, 0 repeats
@changelog I like git quite a bit
(DIR) Post #AZUvJphv2WGX6cq9q4 by kaezarrex@fosstodon.org
2023-09-06T17:49:13Z
0 likes, 0 repeats
@changelog Are tools "not good enough" because they can't scale for large enterprises? It often seems that when a tool is built to scale that large, it's criticized for being overkill for most use cases.I wonder if there are examples of tools that walk that line well. They are able to be Google-scale, and they are generally accepted as worth using for small projects.
(DIR) Post #AZV4GplZGP0K0VBwpc by develwithoutacause@techhub.social
2023-09-06T19:29:37Z
0 likes, 0 repeats
@changelog As a Googler I 100% agree. #Git is way too complicated and difficult to work with. #GitHub is decent, but is quite far off from internal tools.CodeSearch and code indexing are a big piece. Stacked diffs for code reviews, remote clients, comprehensive build system, all add on top of this.I have personally advocated for literally selling the google3 development model and all its tooling as a service, but I'm not high enough in the org chart for my opinion to matter.I do struggle to see how you could build an equivalent in OSS. Certainly individual features can be implemented, tools can be built. But the real "secret sauce" to Google is the integration. Everything connects to everything else because we can make assumptions about the other tools you're using. You can't really replicate that in an open ecosystem.