• 1 Post
  • 14 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle



  • I think we may be talking about two different things with regards to corporate control. I’m saying that, in the case with Redhat specifically, that their injection of a fee to access the source code now no longer makes the code freely available to downstream repositories. If they comically charged a billion dollars to access the source code (with a GPL) it would practically become closed source, so I’m curious why any entity can charge any amount to access open source software. And if it’s totally legal with this type of license, doesn’t that mean that we should be avoiding GPL at all costs?


  • Correct me if I’m mistaken. What I read from your post sounds to me like you think that we should accept that a company will inject a revenue stream into the process that we all were working on as an open source project. We weren’t expecting to get paid, so why not allow the company to get paid, regardless of the downstream impacts for other projects that once relied on the project being completely free and open. Do I understand that properly? I don’t want to misrepresent your intent. I feel like I must be misunderstanding something.



  • My first programming language was QBasic, then Visual Basic, then Java, then C# (most experience with), then C++, then Python, and now Rust. Only when I learned C++ in college did I truly grasp the power of memory management. I think it’s important for new programmers to have some understanding of and experience with pointers, but it doesn’t need to be your first language. I think it’s okay to start with Python or C#, but you’ll want to go back and learn the hard stuff at some point (C++ and then Rust). Python will be super easy to learn the basics (data structures, algorithms, etc.). C# is also a good choice, but has you learning a few more things at the same time you’re trying to learn the basics.








  • As a backend developer you’re not doing anything with “looks”. No interface design, HTML CSS, or anything like that.

    The most common backend work involves the following:

    • ETL process creation
    • proprietary API maintenance
    • third-party API integration
    • Database data manipulation

    I enjoy it. It feels like I’m designing special wires that connect different computers together. It can be repetitive if you’re not designing your code to be extendable. If you’re writing the ideal code, you’re always writing new stuff. If you’re just copy-pasting from other examples, that should indicate that there is a general solution that’s being ignored.