• 1 Post
  • 105 Comments
Joined 1 year ago
cake
Cake day: June 4th, 2023

help-circle
  • Computers work with 1s and 0s. We have decided as a society that certain combinations of those equate to being copywritable. This ruling seems to be saying the result of a calculation cannot be copywritable? Wouldn’t creative tools like movie editor or photoeditor disagree? So then is the ruling actually saying these specific values used in this instance are not copywritable, changing the health to 100 for e.g., because there is no human creativity in the result of that value?

    So if a programmer used an original work of art to define the state of health in the actual code, and verified the value matches the 1s and 0s that represent that work of art (thus it only ever comes down to boolean check in the logic side, and the value of the variable is never set to something simple like 0 to 100, it was using a huge amount of RAM and a very slow comparator operator.

    Yea, I went there.











  • I’m a bit slow on the uptake there haha. I started with vi and moved over to nano at some point and never looked back. I can refactor code in production with the best of them. There’s still some tricks I’ve seen done in vi that amazes me that I haven’t tried to figure out in nano, but for the most part it’s fairly easy to use to do nearly anything in. Even supports color for supported files, YAML, etc.