Live data from Hacker News

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

lore.kernel.org

161–170 of 433 posts

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

#162
post #101

Earlier quoted context omitted.

C is unsafe.

Changing well-tested code is unsafe.

I mean if you want Git to never change you're free to stick with the current version forever. I'm sure that will work well.

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

#163

Earlier quoted context omitted.

Git works only on cygwin too?

No, it doesn't. OP meant that the Rust support on Cygwin is bad; it is better with the native Windows API.

Cygwin is an ugly hack anyway.

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

#164
post #93

Earlier quoted context omitted.

> You are. This is firm "I don't want to have to learn new things" territory, which isn't a viable attitude in this industry. It's viable, but limiting. Sometimes you have to do things you don't want to, which is why it's called work. But if you can choose what platforms you work on, you can orient towards things where things change less, and then you don't need to learn new things as often. Chances are, if you get i…

No one’s laying off COBOL programmers. Specialization has its upsides once the market isn’t saturated!

Well only because 99% of the world's COBOL developers were laid off decades ago (or switched to another language).

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

#165
post #67

Earlier quoted context omitted.

I strongly agree. I read some of the counter arguments, like this will make it too hard for NonStop devs to use git, and maybe make them not use it at all. Those don’t resonate with me at all. So what? What value does them using git provide to the git developers? I couldn’t care less if NonStop devs can use my own software at all. And since they’re exclusively at giant, well-financed corporations, they can crack open…

"You have to backport security fixes for your own tiny platform because your build environment doesn't support our codebase or make your build environment support our codebase" seems like a 100% reasonable stance to me

> your build environment doesn't support our codebase

If that is due to the build environment deviating from the standard, then I agree with you. However, when its due to the codebase deviating from the standard, then why blame the build environment developers for expecting codebases to adhere to standards. That's the whole point of standards.

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

#166

Earlier quoted context omitted.

It's a lot more understandable for developer tooling like Git to more quickly adopt newer system requirements. Something like the Linux kernel needs to be conservative because it's part of many people's bootstrapping process. rustc_codegen_gcc is close to becoming stable, and conversely the Linux kernel is dropping more esoteric architectures. Once the supported sets of architectures fully overlap, and once the Linux…

I would also say that it’s a lot easier to learn to write rust when you’re writing something that runs sequentially on a single core in userspace as opposed to something like the Linux kernel. Having dipped my toes in rust that seems very approachable. When you start doing async concurrency is when the learning curve becomes steep.

I've found that when you're doing concurrency, Rust makes things easier, and it becomes simpler to get right.

However, adapting the conventions and mechanisms of a large complex C system like the Linux kernel to Rust is taking time.

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

#167
post #160

Earlier quoted context omitted.

This doesn't matter at all for programs like Git. Any non-free standing program running on a modern OS on modern hardware trying to access memory its not supposed to will be killed by the OS. This seams to be the more reasonable security-boundary then relying on the language implementation to just not issue code, that does illegal things. Yeah sure, memory-safety is nice for debuggibility and being more confident in…

Not quite the best example, since Git usually has unrestricted file access and network access through HTTP/SSH, any kind of RCE would be disastrous if used for data exfiltration, for instance. If you want a better example, take distributed database software: behind DMZ, and the interesting code paths require auth.

Git already runs "foreign" code e.g. in filters. The ability to write code that reacts unexpectedly on crafted user input isn't restricted to languages providing unchecked array/pointer access.

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

#168

Earlier quoted context omitted.

> Now rather than needing to understand just C to work on Git/kernel, you now need to also know Rust. I'm yet to know a single software engineer who isn't well versed on multiple programming languages. This is not a problem.

Except now these software engineers have to code switch between languages. Could you software engineers stop making things harder for yourselves and playing this meaningless flex of a status game, and you know, focus on something tangible, meaningful, instead of adding more bureaucracy?

I'm guessing you aren't a software engineer based on this comment, but the difference between programming languages is tangible and meaningful. It isn't like human languages where they're mostly basically the same and achieve the same thing.

And code switching between languages is not hard at all.

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

#169
post #113

Earlier quoted context omitted.

It's kind of funny to see f-ing HPE with 60k employees somehow being labeled as the poor underdog that should be supported by the open-source community for free and can't be expected to take care of software running on their premium hardware for banks etc by themselves.

I think you misread my comment because I didn't say anything like that. In any case HPE may have 60k employees but they're still working to create a smaller platform. It actually demonstrates the point I was making. If a company with 60k employees can't keep up then what chance do startups and smaller companies have?

> If a company with 60k employees can't keep up then what chance do startups and smaller companies have?

They build on open source infrastructure like LLVM, which a smaller company will probably be doing anyway.

Post reply on HN