• 0 Posts
  • 24 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.


  • Not really, and no. This shouldn’t affect your already-running system. This change means that the iso will offer plasma by default and will run plasma in the live environment.

    And I wouldn’t say it’s particularly hard to switch from any desktop environment to another. It takes some relearning where stuff is, keyboard shortcuts, etc, but any desktop environment can run any Linux program, provided the necessary libraries are installed (which your package manager takes care of). You can install kde programs on your xfce desktop, and they will run fine (and vice versa). They’ll just pull in a bunch of kde libraries when you install.









  • There will be things to learn and unlearn, but modern Linux distros are fairly smooth sailing for basic tasks if your hardware supports Linux well. Laptop support is a little more spotty, where there may be issues with suspend, or the Wi-Fi needing 3rd party drivers, but desktops will probably work without much fuss (and there are plenty of laptops with no issues).

    Gaming has been made much easier thanks to wine and proton, particularly valve’s contributions. For steam games, many of them will just work out of the box or after ticking a checkbox. ProtonDB is invaluable for quickly seeing how well a game will run on Linux.

    But as you’ll see as you read some of the reports on ProtonDB, there will likely be a more troubleshooting than you’re used to on windows. As long as you know how to Google the name of your distro + the problem you’re seeing, you’ll usually find a solution.

    You don’t need to be a terminal master to use Linux nowadays. But most things are easier to explain with terminal commands than with step by step gui instructions, so many guides online will have you use the terminal to some degree.

    Honestly, the best advice I can give is just try it. If you have a spare drive (internal or usb), just go ahead and install Linux to it. If you want to be extra sure you won’t do anything to your existing windows install, remove the windows drive first (or disable it in bios). Then play around with things and see how it feels.