Hacker News new | past | comments | ask | show | jobs | submit login

I was thinking the same on this. It is a classic case of division of responsibility. The argument appears to be: should we force a small number of downstream maintainers to suffer a big maintenance burden or should we make upstream handle a smaller burden.

Martin's position rests on his claim that the big maintenance burden he would be forced to bear is unfair. I mean, he is the one who chose Rust. No one forced that on him. It is kind of hard for me to see his claim that the maintenance burden of his choice is somehow the responsibility of the upstream maintainers who are all C developers, no matter how small he insists such maintenance would be. My own opinion is that he made his bed, he needs to sleep in it. Or wait for the tides to change in his favor over Rust inclusion in the kernel. All of this crying foul just doesn't sit well with me.






Agree, these are not the real issues. He has some personal issues going on and is blaming this thing or things as the source of his problems which they are not. It seems he needs some emotional maturity and resilience too.



Join us for AI Startup School this June 16-17 in San Francisco!

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

Search: