• 0 Posts
  • 15 Comments
Joined 2 years ago
cake
Cake day: September 7th, 2023

help-circle

  • How about neither? Both China and the USA have proven themselves to be unreliable trade partners. In fact, a lack of reliability is inherent in any trade relationship. The conventional theory is that trade brings prosperity (true!) and governments want to maintain that prosperity, so they have a (literally) vested interest in preserving that - and this latter part is not so true anymore these days. (We all know why of course, it’s because the prosperity is not shared equally in the USA, and China is unstable because it’s a totalitarian state that will happily immolate itself in order to save face - but this is besides the point.)

    The important point is that while trade is nice because it brings greater prosperity, it also comes with security risks and as we move into a new age of geopolitics, we need to be aware of this and find a better balance between trade and security. It will be hard, because it’s so easy to be greedy and focus only on economics, but hopefully we will continue learning the lesson of finding this balance as we see more and more crazy things unfold over the course of this decade.









  • I’ve never had the chance to use a functional language in my work, but I have tried to use principles like these.

    Once I had a particularly badly written Python codebase. It had all kinds of duplicated logic and data all over the place. I was asked to add an algorithm to it. So I just found the point where my algorithm had to go, figured out what input data I needed and what output data I had to return, and then wrote all the algorithm’s logic in one clean, side effect-free module. All the complicated processing and logic was performed internally without side effects, and it did not have to interact at all with the larger codebase as a whole. It made understanding what I had to do much easier and relieved the burden of having to know what was going on outside.

    These are the things functional languages teach you to do: to define boundaries, and do sane things inside those boundaries. Everything else that’s going on outside is someone else’s problem.

    I’m not saying that functional programming is the only way you can learn something like this, but what made it click for me is understanding how Haskell provides the IO monad, but recommends that you keep that functionality at as high of a level as possible while keeping the lower level internals pure and functional.




  • Don’t forget that the EU Commission funded a report to document the impact of file sharing and then buried it when they found out that it was actually beneficial to the creators. So if you want to engage in file sharing, you’re actually helping them.

    Do what you will with that information. If you really want to boycott, then boycott the content altogether. If you can’t hold back, then download them, but you’re helping them out anyway by doing that.

    The best thing you can do is support your local art scene and find better alternatives.



  • This has always been the whole point behind the Trojan Horse that is systemd. Now that Poettering/Red Hat control the entire userspace across virtually all distros, he/they can use it as a vehicle to force all of them to adopt whatever bullshit he thinks of next.

    This is what the Linux ecosystem gave away when they tossed their simple init system to adopt the admittedly convenient solution that is systemd. But in reality, the best solution was always to drop init, and instead replace it with an alternative that was still simple to replace if the need should arise. But now that everyone is stuck on systemd, they’re all at the mercy of Poettering’s Next Stupid Idea.

    Convenience comes at a price. systemd is the Google Chrome of Linux userspace. Get out while you can.