FizzyOrange

Yes it has definitely changed. Before AI, writing code strongly indicated that the author had thought about the problem and put effort into solving it. Of course they could have still done it wrong but a) the chances are much higher with AI, and b) they're using up your time without spending any of theirs which breaks the social contract.

Yeah I think just counting fully unique lines is going to really capture the repetitiveness of a language. I think you'd get more accurate results just asking people using pairwise ranking.

They wanted me to make some changes and with the normal workflow that's just git commit and git push. With git send-email I have no fucking idea and it got beyond the point where I had enough cared enough to fight the process.

For bare metal definitely get a microcontroller and do some fun electronics project.

Easiest to get into is Arduino, but don't stick with that because its only redeeming feature is that it's easy to get into. The IDE sucks, the build system sucks, the APIs really suck, and the code quality is very low (probably because it's easy to get into so you get a lot of inexperienced people doing stuff).

After Arduino I would recommend either going to the Nordic nRF5x series - you can do some cool Bluetooth stuff, or even make you your own radio protocol since the radio peripheral is fully documented... Or ESP32 with Rust and Embassy is probably the most modern and slick way to do microcontrollers.

It does require learning Rust but Rust is really really good so you should do that anyway.

There are some extremely good videos on YouTube about that: https://youtube.com/@therustybits

I would probably still start with Arduino though since you know C. Just don't stay there for too long.

Yeah it's mad. Tbh I don't think GitHub PRs are the best workflow, but I absolutely know that git send-email is the worst. I tried to use it once to contribute to OpenSBI, which inexplicably also insists on it. Suffice it to say my patch was never merged...

... if you have a super janky patch file workflow.

If you are using Git like normal people do this can't happen.

This is just straight up "ChatGPT write me an article about merge vs rebase".

It's also missing any discussion of squashing, CI, git blame, git bisect etc.

You have misunderstood. The is ranting against Clean Code, not clean code.

I came for the trash Phoronix comments... But actually they were all very reasonable! What happened to the anti-Rust luddites?

In my experience a lot of these old projects really go out of their way to dissuade contributions anyway. Lots of naysaying "it's always been like that", ancient infrastructure - e.g. insisting on git send-email patches, etc.

Usually the only way it gets resolved is when someone writes a more modern competitor and it starts gaining traction. Suddenly all those improvements that people tried to do and were told were impossible and stupid aren't such a bad idea after all.

I don't think that's the case with Unity but it probably is with things like GCC, sudo, sysvinit, X11, etc.

I remember when this is how browser zoom always worked. It was super janky, everyone hated it and the current "zoom everything" system was seen as a big improvement.

I guess opt-in makes sense. Probably nobody is going to bother though.

Rust doesn't have inheritance like in traditional OOP languages because it doesn't have virtual methods. You have to manually implement methods to delegate to base classes.

Also what is this trash meme?