Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

There are a lot of entities involved that need to be able to work together. Creating a form fractures things and requires all partners to move to said fork. It's far easier to work upstream even with resistance. Anyone who has maintained a long standing Linux fork understands the costs of trying to rebase thousands of patches. There will never be enough of a migration to make it unnecessary to need to rebase.


"Hey upstream maintainer, let me commit a bunch of code in a language you can't even read. You get to maintain it forever while I get to move on to bigger and better things. I am better that you after all: I know this cool new language and you don't."

And this didn't go over well. Shocking.


That isn't a remotely fair characterization of what the rust for linux team were saying. In particular they committed to maintaining it.

https://lwn.net/Articles/1006805/

"We wrote a single piece of Rust code that abstracts the C API for all Rust drivers, which we offer to maintain ourselves".

I wish that HN as a whole could maintain a respectful and curious tone of debate when these threads come up. Feel like both rust advocates and skeptics could do a lot better.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: