• 0 Posts
  • 10 Comments
Joined 6 months ago
cake
Cake day: February 14th, 2025

help-circle

  • Decentralized currencies will only actually make sense when the material incentives of our economic system would benefit from them. Capitalism is literally all about concentrating the control of capital and the means by which we produce things. Sadly, decentralized currencies will never be allowed to decouple themselves from these economic systems. There is too much material power to prevent that. And by material power I mean literally the enforcement of these concentrations of wealth through the use of violence.

    The tech is cool. But it doesn’t magically solve the problem by simply being invented. It’s why no one is actually paying with these cryptocurrencies on anything but an extremely small scale.

    A currency that cannot be manipulated by capitalist for their benefit has no place in our world. So, it will never reach any meaningful real use until those structures are dismantled. It will just continue to be a speculative asset that rich people dump their extra wealth into and poor people play as the lottery.








  • LeninOnAPrayer@lemm.eetoLinux@lemmy.mlHappy with my bash progress!
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    5 months ago

    Yes. You’re correct. The script will execute with /bin/bash by default but only in a bash shell. #!/bin/bash is still a good habit to have. Some platforms may be running an “sh” shell by default. In this case if you ran the script it would execute with /bin/sh instead. Which would work or not work depending on if your script was written in purely sh syntax and not using any uniquely bash style syntax.

    Bash can run all sh scripts but sh cannot run all bash scripts. So explicitly stating for which one your script was written for is good practice to not run into errors if you move your script to a different environment.


  • It makes it usable without typing bash. Same would apply for a python script. For example you can make a python script named with no extension and add #!/usr/bin/python to the top of the file. Bash shell sees this and knows to execute the script using that python path.

    Then you just include the directory in your $PATH and chmod +x the script. Then you can type $python_script instead of $python python_script.py