• 0 Posts
  • 14 Comments
Joined 2 years ago
cake
Cake day: June 25th, 2023

help-circle


  • Not when taken to such an extreme so as to obfuscate the meaning and behavior of code, and make it difficult to understand how you would arrive at that code.

    Sane defaults serve to reduce verbosity without obfuscating meaning, simpler syntax with different ordering and fewer tokens reduce verbosity to make the code easier to read by reducing the amount of text you have to pay attention to to understand what the result is.

    I imagine there’s also a distinction to be made between verbosity and redundancy - sometimes extra text might fail to carry information, or carry information that’s already carried elsewhere. I’m not sure where the line should be drawn, because sometimes duplicate information can be helpful, and spacing out information with technically meaningless text has value for readability, but I feel like it’s there.



  • I’m not sure which puzzles you’re referring to - do you mean stuff to reach an ending, or the obscure, very much optional, deep secrets?

    It’s been a while since I played it, but I don’t remember grindy puzzles in the main content, bar the big one, but that one felt exhilarating to figure out and solve.

    As for combat, it is difficult, but I remember beating the whole game without turning down the difficulty (which I remember being a thing), so it seemed fine to me… But yeah, people misrepresenting a game is always a risk.






  • KubeRoot@discuss.tchncs.detoTechnology@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    1
    ·
    1 month ago

    Yes, apple should allow that, and Sony should allow that. Your “gotcha” seems pretty stupid, because “allow” doesn’t mean “facilitate” - it’s not Apple’s responsibility to make those things work on their devices, but Apple is going out of their way to prevent individuals from making those things happen on their own.


  • If you license your project under GPL, and somebody submits some code (like through a pull request) that ends up in the library you use, you are now also bound by the GPL license, meaning you also have to publish the source of any derivatives.

    The way to avoid it is to use something like a CLA, requiring every contributor to sign an agreement giving you special rights to their code, so you can ignore the GPL license in relation to the code they wrote. This works, but is obviously exploitative, taking rights to contributions while giving out less.

    It also means if somebody forks the project, you can’t pull in their changes (if you can’t meet GPL terms, of course), unlike with MIT, where by default everybody can make their own versions, public or private, for any purpose.

    Though it’s worth noting, if you license your code under MIT, a fork can still add the GPL license on top, which means if you wanted to pull in their changes you’d be bound to both licenses and thus GPL terms. I believe this is also by design in the GPL license, to give open-source an edge, though that can be a bit of a dick move when done to a good project, since it lets the GPL fork pull in changes from MIT versions without giving back to them.


  • I think the trick might be that nothing is stopping you from using more than one 32-bit integer to represent addresses and the kernel maps memory for processes in the first place, so as long as each process individually can work within the 32-bit address space, it’s possible for the kernel to allocate that extra memory to processes.

    I do suppose on some level the architecture, as in the CPU and/or motherboard need to support retrieving memory using more than 32 bits of address space, which would also be what somebody else replied, and seems to be available since 1999 on both AMD and Intel.