News for hackers. Stuff that matters.
Re:Software Engineering at Google by joshuamorton on Monday August 14, 2023 @01:05PM (#37123512)
> Edit: as OP mentioned, it does seem to differ in technical sense from traditional CR, in that the changes live only on developer machine, not in source control.

Yes and no. There's a decent whitepaper on Piper and citc you can find by searching for it (or actually I will :P [0]), as far as piper is concerned they aren't checked into source control, but the vast majority of development happens in "citc" workspaces, which aren't source control, but also are source control in a sense that every save is snapshotted and you can do point in time or point in history recovery, and I can open up a readonly view of someone else's workspace if I know the right incantations, and most of the developer tools treat the local citc workspace enough-like a commit that it's transparent ish.

[0]: https://cacm.acm.org/magazines/2016/7/204032-why-google-stor...

Re:Software Engineering at Google by dinvlad on Monday August 14, 2023 @01:24PM (#37123768)
OK, thanks for these details and the link! Somehow I remember the title, but not the content :-) That'll be an interesting read.
Re:Software Engineering at Google by nonethewiser on Monday August 14, 2023 @02:17PM (#37124520)
> and I can open up a readonly view of someone else's workspace if I know the right incantations

So thats not just a basic feature?

Re:Software Engineering at Google by UncleMeat on Monday August 14, 2023 @03:21PM (#37125581)
The normal workflow is to create a changelist and then have somebody patch that changelist into their client rather than accessing their client directly.
Re:Software Engineering at Google by joshuamorton on Monday August 14, 2023 @03:52PM (#37125975)
It's the equivalent of me being able to view the local, unpushed changes you have in whatever directory you git cloned into.