Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Git: Introduce Rust and announce it will become mandatory in the build system

lore.kernel.org

Post reply on HN
Print view View original

81–90 of 433 posts

Re: Git: Introduce Rust and announce it will become mandatory in the build system

#81

Post by eklavya »

doctorpangloss wrote: post #45
politelemon wrote: post #2

> Introducing Rust is impossible for some platforms and hard for others. Please could someone elaborate on this.

You’re chasing after the meaning of “impossible.” Easy. There’s two categories of developers: > I like programming > I program to make money If you belong to the second category - I’m going to be super charitable, it sounds like I’m not going to be charitable and I am, so keep reading - such as by being paid by a giant bank to make applications on Nonstop, there might be some policy that’s like “You have to vet all o…

What are you on about?

Re: Git: Introduce Rust and announce it will become mandatory in the build system

#82

Post by saghm »

phkahler wrote: post #28

It's to a "test balloon" if you have a plan to mandate it and will be announcing that. Unless I suppose enough backlash will cause you to cancel the plan .

It's literally a test of how people will react, so yes, finding out if people will react negatively would be exactly the point of doing the test in the first place. Would you prefer that they don't publicize what their follow-up plans would be to try to make it harder to criticize the plans? If you're against the plan, I'm pretty sure that's the exact type of feedback they're looking for, so it would make more sense to tell them that directly if it actually affects you rather than making a passive-aggressive comment they'll likely never read on an unrelated forum.

Re: Git: Introduce Rust and announce it will become mandatory in the build system

#83

Post by rascul »

bArray wrote: post #69
Luker88 wrote: post #62

Earlier quoted context omitted.

AFAIK git already uses multiple languages, github says its 50% C, 38% shell, 4% perl, then 4% TCL python 1% So "another language" here probably does not weigh as much, especially considering perl/TCL are the weirder one there. But for big projects like linux and git, this could actually be a consolidation step: you spent decades growing, hacking things on top of each other. You have mostly figured out what this proje…

I did check this out. The shell, perl and python are likely for scripting and not used during runtime. TCL is likely some form of dynamic scripting. I think we also have to be honest about what the project here is too, it's not to have both C and Rust together, but to replace all C with Rust. In which case, it probably makes sense to just clone to repo and work on a fork like they did with SSH.

A number of the git commands were implemented in perl and shell. Now I see only git-svn is perl here for me and there's still a few shell scripts in /usr/libexec/git.

Re: Git: Introduce Rust and announce it will become mandatory in the build system

#84

Post by motorest »

jmillikin wrote: post #9
politelemon wrote: post #2

> Introducing Rust is impossible for some platforms and hard for others. Please could someone elaborate on this.

There's at least one proprietary platform that supports Git built by via a vendor-provided C compiler, but for which no public documentation exists and therefore no LLVM support is possible. Ctrl+F for "NonStop" in https://lwn.net/Articles/998115/

> There's at least one proprietary platform that supports Git built by via a vendor-provided C compiler, but for which no public documentation exists and therefore no LLVM support is possible.

That's fine. The only impact is that they won't be able to use the latest and greatest release of Git.

Once those platforms work on their support for Rust they will be able to jump back to the latest and greatest.

Re: Git: Introduce Rust and announce it will become mandatory in the build system

#85

Post by cschep »

johnisgood wrote: post #60
cschep wrote: post #37

Earlier quoted context omitted.

My guess is that we (I am also a user of git) won't even notice.

I will leave this here for the future: $ ldd /usr/bin/git linux-vdso.so.1 (0x00007f69c2d64000) libpcre2-8.so.0 => /usr/lib/libpcre2-8.so.0 (0x00007f69c2c81000) libz.so.1 => /usr/lib/libz.so.1 (0x00007f69c2c67000) libc.so.6 => /usr/lib/libc.so.6 (0x00007f69c2616000) /lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007f69c2d66000) $ ls -alh /usr/bin/git -rwxr-xr-x 1 root root 4.0M Aug 25 11:40 /usr/b…

Ok, I'll bite.

While we are on Hacker News, this is still an enormously obtuse way to communicate.

Are you saying that as users of git we will be negatively affected by deps being added and build times going up? Do you have evidence of that from past projects adding rust?

Why not just say that??

Re: Git: Introduce Rust and announce it will become mandatory in the build system

#86

Post by riedel »

Given that rust only works on e.g. cygwin recently (and still does not build many crates: i try to compile jujutsu and failed), this is a big blow to portability IMHO. While I try to like rust, I think making it mandatory for builds of essential tools like git is really too early.

Re: Git: Introduce Rust and announce it will become mandatory in the build system

#87

Post by GoblinSlayer »

riedel wrote: post #86

Given that rust only works on e.g. cygwin recently (and still does not build many crates: i try to compile jujutsu and failed), this is a big blow to portability IMHO. While I try to like rust, I think making it mandatory for builds of essential tools like git is really too early.

Git works only on cygwin too?

Re: Git: Introduce Rust and announce it will become mandatory in the build system

#90

Post by rbehrends »

bArray wrote: post #69
Luker88 wrote: post #62

Earlier quoted context omitted.

AFAIK git already uses multiple languages, github says its 50% C, 38% shell, 4% perl, then 4% TCL python 1% So "another language" here probably does not weigh as much, especially considering perl/TCL are the weirder one there. But for big projects like linux and git, this could actually be a consolidation step: you spent decades growing, hacking things on top of each other. You have mostly figured out what this proje…

I did check this out. The shell, perl and python are likely for scripting and not used during runtime. TCL is likely some form of dynamic scripting. I think we also have to be honest about what the project here is too, it's not to have both C and Rust together, but to replace all C with Rust. In which case, it probably makes sense to just clone to repo and work on a fork like they did with SSH.

> The shell, perl and python are likely for scripting and not used during runtime.

Some git subcommands are implemented in these. git filter-branch is a shell script, git cvsimport is a Perl script, and git p4 (perforce interop) is a Python script. There are not too many left these days (git add -p/-i also used to call a Perl script), but they exist.

Post reply on HN