tex0

4 ms·

1.
by tex0 27d ago
Fantastic write up, but I still have doubts. As the author states: Serving git at scale is hard. I can only concur. I feel like the article is a bit light on the design of the WAL and maintenance operations, but maybe it's me. Anyway,
2.
by tex0 27d ago
Exactly. I would love to see that design work, but it doesn't for any realistic workload.
3.
by tex0 4mo ago
If the developer can have a local copy of the monorepo it's not a "large" codebase.
4.
by tex0 5mo ago
The interesting selling point about this, if the claims are substantial, is that nobody will be able to produce secure software without access to one of these models. Good for them $$$ ^^
5.
by tex0 8mo ago
Fossil has some really nice ideas (although I don't like the feature bloat), but when I tried to use it I ran into so many issues and/or bugs. With git on the other hand I can't remember ever hitting a bug in decades. I don&#
6.
by tex0 10mo ago
This is a cool tool, I like the idea. But the way `uc machine init` works under the hood is really scary. Lot's of `curl | bash` run as root. While I would love to test this tool, this is not something I would run on any machine :&#x2
7.
by tex0 10mo ago
Same here. Pretty amazing. Almost every game in my (large) Steam libarary runs out of the box. Performance is on par with Windows. This finally allowed me to ditch Windows. And no, I don't bother with crap that needs a kernel level ant
8.
by tex0 1y ago
If you don't like Go, then just let go. I hope nobody forces you to use it. Some critique is definitely valid, but some of it just sounds like they didn't take the time to grasp the language. It's trade offs all the way. For
9.
by tex0 1y ago
https://opensource.google/projects I think all of those are using git and many Gerrit as well.
10.
by tex0 1y ago
Maybe they need perforce support instead :P
11.
by tex0 1y ago
Gerrit can do some of that.
12.
by tex0 1y ago
That depends on your VCS. Some systems don't even allow you to "clone" anything. And yes, some of them enforce all kinds of ACLs.
13.
by tex0 1y ago
That is pretty much what I'm doing with Steam, Proton and my Game Library. 99% the time it works just great.
14.
by tex0 2y ago
Probably zero. And strike the non-SWE part. gpg isn't really easy to use.
15.
by tex0 2y ago
Maybe git is just too complicated for average users (myself included).
16.
by tex0 2y ago
The new GitHub CS is pretty great indeed. Still not on par with it's role model, but getting closer.
17.
by tex0 2y ago
Thank you for reposting. I don't want to start bashing XZ, but I honestly wonder why it's been picked up so much despite the valid criticism. As if the compression rate increase at medium levels were so significant over bzip2 or g
18.
by tex0 3y ago
Yes, it comes pretty close. Well done!
19.
by tex0 4y ago
Is the source code of the service behind proxy.golang.org actually open-source?
20.
by tex0 4y ago
KeePass(X), Password Store/Gopass, pwSafe, ... Plenty of good choices.
21.
by tex0 4y ago
Why did people think that using a cloud based password manager (or for that matter: a closed source one) was ever a good idea?
22.
by tex0 4y ago
Same here. In fact I've built a very similar tool because sed/awk/grep/find didn't quite cut it and it did help a me lot to get sh* done.
23.
by tex0 4y ago
How do you know?
24.
by tex0 4y ago
He's so right about this. git is terrible. I hope some day we see a successful successor.
25.
by tex0 4y ago
That reminds me of Piper/CitC: https://cacm.acm.org/magazines/2016/7/204032-why-google-stor...
26.
by tex0 4y ago
Packfiles give me PTSD. They are so notoriously hard to maintain on the large scale server side. I really wish git wasn't using them.
27.
by tex0 4y ago
I disagree. All the examples you mention are part of the software supply chain. To me it doesn't matter if code comes in through a vendor, a dependency or is written in house. It's all well within the responsibility of the organiz
28.
by tex0 4y ago
Welcome to dependency hell. But then many packages are so trivial that they shouldn't even require a license. Same goes for abandoned projects.
29.
by tex0 4y ago
This serves as another example to me that governance and conflict resolution in the Debian project is really poor. Maintainers are free to do whatever they want, even if it doesn't make any sense at all.
30.
by tex0 4y ago
Running this kind of stuff costs serious money. Of course they must see a way to make money with it in the long term. Like they did with GitHub itself: as a data source for CoPilot ;)

More ›