• 2 Posts
  • 127 Comments
Joined 2 years ago
cake
Cake day: June 10th, 2023

help-circle







  • Depends on what you’re used to. I have lost too much time trying to get a python or js program to run on my machine.
    Of course if the project is well written and with decent documentation it’s easier, but in general I have had too many incompatibilities with versions of the tooling and the dependencies which may be too ancient to work properly. On the other side, go code that was written a decade ago still compiles fine without thinking about it.
    Hell I even had a js project that was working then 6 months later, without changing any code in it, wouldn’t build. Talking to a front end dev at work he immediately said “oh yeah node was probably updated and you need to do x and y to make it work”. Sorry but I have other things to do than massaging bad tooling to build this.

    Btw, even containers are not a bullet proof solution. I had a python container straight up not work even though it was distributed like that.


  • I agree in general, if you need something specific then there is no way around it. But when I’m looking for something I evaluate all possible solutions, and being written in a language that has issues like this is a mark against it. Sometimes it’s easier to write the thing myself in some language I master than to wrangle python or Js dependencies.
    In my experience there is rarely only one solution written in python or Js for my use cases.




  • OrygintoTechnology@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    4
    ·
    2 months ago

    From the incident report it seems the impact was limited to VMs in one DC in one region to be stopped, as the power was lost. And some service degradation in the region.
    So not that much impact. Of course resources in this DC would stop working, but the rest of the region was still working properly. If you built your infra in this region in a resilient manner, your services should not have been impacted that much


  • OrygintoPeople Twitter*Permanently Deleted*
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    2 months ago

    The ACF takeover is the cherry on top for me. Fork it all you want, but to force users to upgrade to your version looks bad on them. That’s literally a supply chain attack and they have shown to be willing to do whatever they want to their users.



  • OrygintoLinux@lemmy.mlGoodbye from a Linux community volunteer
    link
    fedilink
    arrow-up
    58
    arrow-down
    6
    ·
    2 months ago

    Wow, I didn’t know that being a Linux/open source contributor meant you don’t have to follow your country’s laws.

    It’s developed internationally but devs still reside somewhere and have to abide by the rules at that place. Linux in this case being represented by an US entity means they have to follow the gov’s sanctions. If you want more or less of those, that’s where (the government) you act.



  • OrygintoPeople Twitter*Permanently Deleted*
    link
    fedilink
    arrow-up
    21
    arrow-down
    4
    ·
    edit-2
    2 months ago

    From what I gathered, it is absolutely a question of licensing.
    Wordpress is gpl so anybody can host it and provide hosting for others. WPEngine does make money like that and that seemed to rub matt the wrong way.
    So he requested more involvement from wpe, claiming they do none (factually false). Then they started trying to extort wpe using trademark as an excuse (even changing the trademark page to reflect their new stance), while also smearing them on the official channels of the project. I’m also skipping the childish behavior of blocking anybody that could be related to wpe from interacting on the official wp.org site, then using this self inflicted wound to say one of WPE plugin is insecure (because they couldn’t publish the update) and doing an hostile takeover of it.

    WPE is totally within their rights to use the wp software without giving a cent back to Matt. If WP wanted payment for the infrastructure they provide on the .org site, they can change the rules to require commercial entities to pay for it (which they totally could do, but that would hurt the other players in the ecosystem). If they had a (real) trademark issue it would have been resolved under closed doors by lawyers.

    there’s an expectation of contributing back or, at the very least, not exploiting the resources of a non-profit.

    No, there are no expectations of contributing. It would be worded in the license otherwise (the only expectation of giving back in the gpl is that you publish the changes you did to your users). And WordPress.org is not the non profit but is run by the for-profit company that Matt is the CEO of.

    So let’s focus on the actual problem: a large company exploiting a shared ecosystem to run a commercial service.

    Like automatic is doing with wordpress? Don’t they profit from other devs/companies publishing plugins for them to use on their platform? (Actually not opposed to that, that’s the game of open source, but it’s a bit hypocritical to only cry when it doesn’t serve them).

    Edit: From your original comment:

    They could have easily avoided this situation without turning it into a turf war.

    Yes, then why did Matt turn this into a turf war? He totally expected the community to take his side and turned it into a shit slinging show for all of us to enjoy.