• 0 Posts
  • 207 Comments
Joined 10 months ago
cake
Cake day: December 16th, 2023

help-circle







  • “releasing the modified version to the public” would cover them re-closing the source and then subsequently releasing that newly closed source, so they can’t relicense it and then release the built version of the code.

    At least not easily, this is where court history would likely need to be visited because the way it’s worded the interpretability of “modified” in this context would need to be examined.





  • This exists but not to the extent it did in the 80s, and expectations aren’t forced and are usually just part of the company advancement culture. “Expected overtime” is listed as part of the job description and the expectation that you stay longer than your boss doesn’t exist much anymore. Also if you don’t follow that culture, they can’t fire you without showing that they don’t have the budget to keep you on and they’ve tried every possible other avenue of remediation. At-will employment laws are nonexistent here.

    Instead of fire you they usually put you in a room by yourself to just sit there for 8 hours a day. You still collect a paycheck.

    Most young people with cell phones have figured out that this is awesome and have started “quiet quitting” by just doing the actual requirements for the job and going home or doing education on their own time.

    However if you like your career and want to advance in your field you’re still fucked and you’re gonna be working a shitload of overtime







  • The problem is that the Linux kernel is monolithic so introducing rust into it does have certain repercussions about downstream compatibility between modules.

    Right now the rust code in the kernel uses c bindings for some things and there’s a not-insignificant portion of C developers who both refuse to use rust and refuse to take responsibility if the code they write breaks something in the rust bindings.

    If it was pure C there would be no excuse as the standard for Linux development is that you don’t break downstream, but the current zeitgeist is that Rust being a different language means that the current C developers have no responsibility if their code refactoring now breaks the rust code.

    It’s a frankly ridiculous stance to take, considering the long history of Linux being very strict on not breaking downstream code.


  • Well part of what it does is grab your actual desktop background to use, and there’s a couple different ways to do that on Linux afaik

    Also I guess the file dialogs would open only to the wine prefix? My experience with wine applications and dialogs is mostly through bottles, so I’m not sure of the sandboxing…