I take my shitposts very seriously.

  • 11 Posts
  • 224 Comments
Joined 2 years ago
cake
Cake day: June 24th, 2023

help-circle




  • The original creator of Wordpress and the owner of a Wordpress hosting site. He’s been having a meltdown for months because Wordpress is being used by WP Engine, a for-profit competitor hosting company, in compliance with the license. Since then, he has:

    • Changed the trademark license and retroactively sued WP Engine,
    • Disparaged WP Engine every time he had the chance,
    • Added a potentially legally binding checkbox to wordpress.com where the user must declare their disassociation with WP Engine (which also locked out actual employees),
    • Forcibly taken control of several community-made plugins,
    • Acted like an absolute fucking buffoon the innocent little lamb who’s been set upon by the wolves.






  • rtxn@lemmy.worldMtolinuxmemes@lemmy.worldOrwelluan
    link
    fedilink
    English
    arrow-up
    8
    ·
    edit-2
    4 months ago
    1. It was doing new things.
    2. It was easier to learn.
    3. The other init systems were (are) stagnant.

    Imagine trying to get new, young developers to adopt C or Pascal when the likes of Rust and Python exist. You can make arguments for a thing’s superiority based on moral standards (which are always subjective), but morality is a poor metric. If everything was done based on that, the Linux ecosystem would be in the same state as the GNU Hurd kernel.








  • Team building events back when I was working in a factory. One day every year we had the option* to go to a crowded bar and have overpriced drinks with the same people we met every day. I didn’t even like half of them (I was just polite and professional) and one shitty event wasn’t going to change my attitude. I would’ve preferred a regular shift on an assembly line.

    * the other option was taking out a paid vacation day (non-American labour laws FTW)


  • You mean a service that translates between ActivityPub and another API? I’m pretty sure that’s just a bridge.

    As for the challenges:

    • It would have to be maintained constantly.
    • It would have to be updated to reflect changes to an API in a timely manner.
    • It would need to handle different versions of APIs (goodness knows even Lemmy instance operators have trouble with that).
    • It would need to handle features that don’t translate one-to-one between instances.
    • It would have to be transparent enough to allow a non-technical user to use it, but opaque enough that a non-technical user doesn’t blame issues with the bridge on the connected services (see for example: the Bottles packaging kerfuffle).
    • …and so on. Lots of challenges.