• 0 Posts
  • 65 Comments
Joined 1 year ago
cake
Cake day: July 31st, 2023

help-circle


  • I see two possible reasons for your situation. One is that the company is turning to contractors to fill in gaps in their knowledge/experience, which is why everyone else has no clue how to tackle these tasks and why they get assigned the easy ones.

    The other possibility is that the senior devs are gaming the metrics, letting the employees knock out easy tasks while the contractor is stuck with untangling the knots of the more intractable tasks.









  • GPL can be used for commercial purposes, but it requires all software derived from it to also be open source and GPL compatible. So no one whose commercial business relies on selling software will use GPL because their customers can copy and distribute the code.

    Neither Safari nor Chrome’s rendering engine is GPL. Safari’s engine is LGPL, which means the binary library can be linked into a closed source program, but modifications to the library’s code must remain open.

    Chromium is BSD, which doesn’t even require modifications to remain open. So I can take chromium’s source, change it however I want for my own browser, and never distribute that code.

    If Safari’s and Chrome’s engines were GPL, Safari and Chrome would be forced to be open source, and they very much are not.








  • You can generally rely on a header file doing its own check to prevent being included twice. If a header doesn’t do that, it’s either wrong or doing something fucky. It is merely a convention, but it’s so widespread that you really don’t need to worry about it.

    You are mixing up some terms, so I want to help clarify. When you #include a header file, you aren’t importing a library. You are telling the compiler to insert the contents of that header file into your source where the #include line is. A library is something different. It is an already-compiled binary file. A library should also come with a header file to tell you what functions and classes are present in the library, but that header isn’t itself the library.

    It may seem annoying to have to repeat yourself between headers and source, but it’s honestly something you get used to.