• 0 Posts
  • 51 Comments
Joined 7 months ago
cake
Cake day: March 21st, 2024

help-circle





  • The way I did it is by trying to solve more and more advanced problems with simpler tools/features, then looking at more advanced features and seeing where they could be applied to make the problem solving simpler. Rinse and repeat.

    An easy example that I can remember is making arrays that dynamically expand. I started with the barebones malloc and worked out how to use std::vector (and other list types) in its place.

    Understanding that concept is, what I believe, to be the foundation of learning programming.

    I’m no pro whatsoever, but using this method really helps me pick up and learn new languages.




  • And that’t the crux of the issue. Stenzek doesn’t actually understand the reality of licensing.

    The reality is this - you can’t do anything without a lawyer. Laweyrs cost money (pro bono isn’t a thing in the copyright world AFAIK, but IANAL).

    If he wanted to avoid this, then maybe he should’ve kept it closed source from the beginning. Chinese sellers on AliExpress couldn’t care less about licensing anyway, so that way he’d have at least some protection.

    IMO his course of action so far has been wrong.

    What he should’ve done is this:

    1. Cause a stir
    2. Get support from the community
    3. Open up donations for the project (or just himself, since you don’t want a repeat of Yuzu)

    He could even go after Arcade1up legally if he raised funds, but that’s not even worth the time if you ask me.





  • Yes but, in practice some of these things don’t matter much at all. At that point you’re looking at the performance stack a bit too deeply.

    Look at the bigger picture. For example - an RTX 4090 can perform about as well on PCIe 3.0 as it does on 4.0 in most tasks that you’d likely use it for.

    You don’t have to care about some of these things as much as you used to before. Sometimes you can get too deep into hunting the best version of your system before you realize that it really doesn’t make that much of a difference.




  • It’s just their ego showing through.

    It basically now comes down to the current devs depending on new Rust devs for anything that interacts with Rust code.

    They could just work together with Rust devs to solve any issues (API for example).

    But their ego doesn’t allow for it. They want to do everything by themselves because that’s how it always was (up until now).

    Sure, you could say it’s more efficient to work on things alone for some people, and I’d agree here, but realistically that’s not going to matter because the most interactivity that exists (at the moment) between Rust and C in Linux is… the API. Something that they touch up on once in a while. Once it’s solid enough, they don’t have to touch it anymore at all.

    This is a completely new challenge that the Linux devs are facing now after a new language has been introduced. It was tried before, but now it’s been approved. The only person they should be mad at is Linus, not the Rust devs.