Comment by 999900000999 | Hacker News Reader

Comment by 999900000999 | Hacker News Reader

Have to side with the one language argument here.

It's hard enough to get a single programming language to work right. C is old and stable.

Rust is new and mostly stable, mostly stable isn't going to cut it when billions upon billions of devices depend on your work.

At the same time this type of ego driven drama keeps me out of the open source community. I have enough people telling me how to code during my 9-5.

I open source most of my projects, but it's not a collaboration. I'll even admit, I get really annoyed when someone puts in a PR that's literally just a bunch of spacing changes in a readme. I think there was some influencer who was claiming that you should go through GitHub, and submit as many changes for things like grammar as possible to a bunch of different projects .

And then on your resume you can put that you contribute it to all these projects. Not fun.

I don't agree with this anymore tbh. But for a project as large, mature, and widely worked on as the Linux Kernel, I absolutely agree.

I think it's a noble goal worth working towards, but Marcan's smug as hell "ill merge and y'all will fix all your broken shit" attitude predictably backfired

Consider using Codeberg for personal projects and reserve GitHub to just collaborative contributions. Codeberg lets you disable pull requests and other unwanted features that GitHub forces down your throat.

Everybody hates spam and abuse, I don't think it supports your claim that much. This is definitely not what anybody thinks of as "collaboration".

In any big project your going to have disagreements.

I need to get paid to deal with stuff like that. No one is going to tell me how to write code without writing me a check.

Even at work I have my limits, although now that I'm older I'm much more inclined to just go with the flow. But if I'm not getting paid what's the point.

I do enjoy game jams though. We only need to work together for a weekend. Plus at least in my circle we only care if the code works.

fwiw, i always make my first PR to an open source as simple / uncomplicated as possible. Something like a spelling or grammar fix in documentation. It's a litmus test for how much drama I will need to face on the more complicated code issues to follow. When the project owners ignore or reject simple stuff, I generally wander off somewhere else.

Not to mention Rust tooling is painfully slow compared to C, last I checked. I wouldn’t want to switch unless that problem went away somehow.

Reply on news.ycombinator.com