In git's defence a perfect diff algorithm seems like a difficult problem to solve in the general case, regardless of VCS.. unless any of the next generation VCSes do better then I would take that as a recommendation to check them out!
MadhuGururajan
joined 2 years ago
whats so bad about rust?
when even nvidia has a better reception to modern languages than some linux maintainers!
You think complainers cease to exist when the software becomes paid? You only need to look at gamers to find a very vocal bunch of angry people in that crowd. This is true for any enthusiast space.
if you can't explain your problem and expect people to read between the lines then don't be surprised people assume the unspoken parts. we're not oracles here!
the linux foundation is not the core linux team. they're just a corporate interest group whose 2% contribution is to the linux kernel.
"Principal Engineer" or "Principal System Engineer" is what you call it in places that don't say some variant of "Architect"
on the other hand challenges like these give us valuable experience. Its not often one has the opportunity to write two programs in different languages from scratch and figure out the coupling. I know I would be excited if I got paid to do such things.
And loose coupling is a good constraint to force a good design for your application.
your objections, I assume are related to duplicated work, and security related?
There are some warts of C that I feel Rust addresses very well. Mainly extensible type system that is not bad like C++. Secondly cargo. Building and packaging just feels wrong in C.
Only one place where C is still better than Rust: Rust does not have a well defined standard ABI. Hence every project compiles everything from source and link statically. Whereas with C we have a standard ABI that can allow for dynamic linking.
maybe the concept of being in a hurry is alien to me as I am not tardy or impatient, or accept that I will be late and just not act like a baboon rushing towards a potential lunch.