Live data from Hacker News

Lore – Open source version control system designed for scalability

lore.org

701–710 of 717 posts

Re: Lore – Open source version control system designed for scalability

#701
post #136

Earlier quoted context omitted.

Objects are your files. Underlying git is a content-addressable filesystem. The objects are referenced by trees. A tree is just a directory. The trees are then referenced by commits and/or tags into a DAG with named pointers into various parts of it (which are your branch and tag references): https://git-scm.com/book/en/v2/Git-Internals-Git-Objects Because it would be terribly in-efficient to have a bunch of loose ob…

> Because git is an open-source project written by nerds, it shows you all of this information. Feel free to ignore it! This is the type of attitude that kept most Unix tools quite user-unfriendly for several decades. What information to show the user, and when, are important design decisions to make. Just dumping it all on the user and making them wade through it is not doing the user a favour. Thankfully newer tool…

Of all the places to complain about a problem like this…

Re: Lore – Open source version control system designed for scalability

#702

Earlier quoted context omitted.

Great, then your choices are (a) try and probably fail to get your changes upstreamed and/or (b) maintain your own fork of git forever. This is very much a "if you don't like X about your country, just move to a different one" kind of "solution". The costs are extreme to the point that pretending it's viable is insulting. Really it's just a way to silence legitimate complaints.

to be fair, if you just want to improve the UX for yourself you can totally have a fork, make your changes, and use it on your own machines when talking to github or whatever other git repository. Now getting someone else to accept your changes might be harder, but that's what happens when you try to change a tool so many people use, especially one with a lot of history. Maintaining a fork is literally one of the thi…

https://news.ycombinator.com/item?id=48573493

Re: Lore – Open source version control system designed for scalability

#703
post #416

Earlier quoted context omitted.

I don't see how Rust is more functional programming oriented than C++

Pure by default, type classes (traits), no inheritance, type level lifetime computation. It's not only more functional it's much more type-safe and closer to Haskell in spirit

I like most of those decisions, but they aren't functional programming

Re: Lore – Open source version control system designed for scalability

#704

Earlier quoted context omitted.

I don't see how Rust is more functional programming oriented than C++

Rust has a load of FP-style iter/map/filter stuff that you can technically do in C++ but only if you don't mind bleeding eyes. It also borrows a lot of features from FP languages like nice tagged unions (enums), Result, everything-is-an-expression, etc.

Guess I never used map+collect in Rust. It's an extra copy. Maybe iter on its own cause that's how you go through non-array collections, same in C++ except C++ is just crappy no matter how you use it.

Re: Lore – Open source version control system designed for scalability

#705

Earlier quoted context omitted.

Anyone still following him after that needs to fundamentally reevaluate some life decisions.

Maybe he's right on gamedev and wrong on some other things

The interesting thing to consider is that it seems fairly obvious from the outside that big game studios are killing themselves. But somehow, on the inside, there are people, of extensive qualification given the nature of our society, who think they're doing the right thing, and that "we" are wrong.

So it leads to the issue of perspective. Somebody has to be right, and everybody thinks that person is themselves, or they obviously wouldn't think what they do think. So in this case he could well be right on both things, or perhaps neither.

Re: Lore – Open source version control system designed for scalability

#706

Earlier quoted context omitted.

Something else that git isn't good at: permissions. In gamedev, you might have proprietary work that you want to restrict to certain users. In P4, you can add restrictions to certain directories for only those who have signed the required NDAs. That's not something that you can do in git: it's all or nothing. Maybe you can set something up with submodules, but that's going to upend your repository if you hadn't plann…

I once worked in a git repository that required those kinds of restrictions. This was within a bank and the code in question was related to enabling Apple Pay from within the banking application. The consequences of that information and code leaking or being seen by anyone who had not signed the NDA were very serious (don't remember the details but it made the lawyers were extremely stressed about it). Needing to fig…

Could you not have placed the code in a submodule and likited access to the submodule repo ?

Re: Lore – Open source version control system designed for scalability

#708

Earlier quoted context omitted.

I believe that the action does reflect Jobs' ego in the following way. Namely, his belief that CEO == company. Jobs would never take the view that the action of the CEO of ATI is actually one bad actor acting alone which doesn't represent what ATI wants as an organization, and is unfair and damaging to that organization and all of its employees. The reason he would not take that view is because then he would not be a…

Ultimately, it is the CEO who has to take responsibility. They are the chief executive officer, after all. And they are well compensated for it.

But did you notice how this was backwards: the company taking responsibility for the CEO's actions, in the court presided by Jobs.

Re: Lore – Open source version control system designed for scalability

#709

Earlier quoted context omitted.

Inside joke. Apple's marketing guy used the word "courage" as an explanation when removing the headphone jack.

That decision had a lot of detractors at the time, but it ultimately seems to have been correct.

It was wrong then, it is still wrong now.

All my three phones have a headphone jack.

I don't have or plan to have an iPhone.

Re: Lore – Open source version control system designed for scalability

#710
post #543

Earlier quoted context omitted.

I don't know if I agree. People who moved to bluetooth got arguably worse sound quality. For wired headphones, there were very few lightning headphones and they mostly sucked. Now with usb-c you can get a broader range of headphones (because other phones have gone with usb-c). either kind needs a dac inside the dongle, or the shell of the headphone, or have a bulky external dac. 3.5mm is still king for decent wired h…

Most people don't like wire and don't care about genuinely good sound through wire vs. artificially sweetened (DSP-ed) sound through Bluetooth. That's what Apple is targeting at, the mass consumer.

Honestly that "most people" seems to be more marketing driven than real opinion.

When you simply can't purchase one thing, then you move to the next thing.

I have several wired and wireless headphones, all for different uses, and the existence of wireless headphones don't make the wired ones less useful for their particular strenghts.

Post reply on HN