home.social

#libxml2 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #libxml2, aggregated by home.social.

  1. Just learning of this when Unity randomly stopped working on latest Ubuntu 25.10 update. Latest Unity release expects XML2, and I presume Ubuntu no longer ships it.

    (insert XKCD meme here)
    youtube.com/watch?v=GDr4fKXmUvc #opensource #foss #unity #libxml2

  2. Just learning of this when Unity randomly stopped working on latest Ubuntu 25.10 update. Latest Unity release expects XML2, and I presume Ubuntu no longer ships it.

    (insert XKCD meme here)
    youtube.com/watch?v=GDr4fKXmUvc #opensource #foss #unity #libxml2

  3. Just learning of this when Unity randomly stopped working on latest Ubuntu 25.10 update. Latest Unity release expects XML2, and I presume Ubuntu no longer ships it.

    (insert XKCD meme here)
    youtube.com/watch?v=GDr4fKXmUvc #opensource #foss #unity #libxml2

  4. Just learning of this when Unity randomly stopped working on latest Ubuntu 25.10 update. Latest Unity release expects XML2, and I presume Ubuntu no longer ships it.

    (insert XKCD meme here)
    youtube.com/watch?v=GDr4fKXmUvc #opensource #foss #unity #libxml2

  5. Just learning of this when Unity randomly stopped working on latest Ubuntu 25.10 update. Latest Unity release expects XML2, and I presume Ubuntu no longer ships it.

    (insert XKCD meme here)
    youtube.com/watch?v=GDr4fKXmUvc #opensource #foss #unity #libxml2

  6. Last time I wrote XML procesing in perl was years ago, so I did a quick search about the suggested approach as of now. Among the first results was a page suggesting XML-LibXML, because it "has good reference documentation and is actively maintained". I mean, I don't insist that there are good alternatives, but knowing XML-LibXML is a #libxml2 wrapper made me hurt inside a bit about the state of the world after what happened with libxml2.

  7. Last time I wrote XML procesing in perl was years ago, so I did a quick search about the suggested approach as of now. Among the first results was a page suggesting XML-LibXML, because it "has good reference documentation and is actively maintained". I mean, I don't insist that there are good alternatives, but knowing XML-LibXML is a #libxml2 wrapper made me hurt inside a bit about the state of the world after what happened with libxml2.

  8. Last time I wrote XML procesing in perl was years ago, so I did a quick search about the suggested approach as of now. Among the first results was a page suggesting XML-LibXML, because it "has good reference documentation and is actively maintained". I mean, I don't insist that there are good alternatives, but knowing XML-LibXML is a #libxml2 wrapper made me hurt inside a bit about the state of the world after what happened with libxml2.

  9. Last time I wrote XML procesing in perl was years ago, so I did a quick search about the suggested approach as of now. Among the first results was a page suggesting XML-LibXML, because it "has good reference documentation and is actively maintained". I mean, I don't insist that there are good alternatives, but knowing XML-LibXML is a #libxml2 wrapper made me hurt inside a bit about the state of the world after what happened with libxml2.

  10. Last time I wrote XML procesing in perl was years ago, so I did a quick search about the suggested approach as of now. Among the first results was a page suggesting XML-LibXML, because it "has good reference documentation and is actively maintained". I mean, I don't insist that there are good alternatives, but knowing XML-LibXML is a #libxml2 wrapper made me hurt inside a bit about the state of the world after what happened with libxml2.

  11. @BrodieOnLinux made some nice video about the problems of funding infrastructure FOSS projects which nobody sees, mainly with the libxml2 example, but OpenPrinting is appearing twice, too:

    youtube.com/watch?v=8PTlYeLBKv
    Problem of finding volunteers

    youtube.com/watch?v=8PTlYeLBKv
    Long time at Canonical, then funded by @sovtechfund and supported by @linuxfoundation

    #OpenPrinting #libxml2 #GNOME

  12. @BrodieOnLinux made some nice video about the problems of funding infrastructure FOSS projects which nobody sees, mainly with the libxml2 example, but OpenPrinting is appearing twice, too:

    youtube.com/watch?v=8PTlYeLBKv
    Problem of finding volunteers

    youtube.com/watch?v=8PTlYeLBKv
    Long time at Canonical, then funded by @sovtechfund and supported by @linuxfoundation

    #OpenPrinting #libxml2 #GNOME

  13. @BrodieOnLinux made some nice video about the problems of funding infrastructure FOSS projects which nobody sees, mainly with the libxml2 example, but OpenPrinting is appearing twice, too:

    youtube.com/watch?v=8PTlYeLBKv
    Problem of finding volunteers

    youtube.com/watch?v=8PTlYeLBKv
    Long time at Canonical, then funded by @sovtechfund and supported by @linuxfoundation

    #OpenPrinting #libxml2 #GNOME

  14. @BrodieOnLinux made some nice video about the problems of funding infrastructure FOSS projects which nobody sees, mainly with the libxml2 example, but OpenPrinting is appearing twice, too:

    youtube.com/watch?v=8PTlYeLBKv
    Problem of finding volunteers

    youtube.com/watch?v=8PTlYeLBKv
    Long time at Canonical, then funded by @sovtechfund and supported by @linuxfoundation

    #OpenPrinting #libxml2 #GNOME

  15. @BrodieOnLinux made some nice video about the problems of funding infrastructure FOSS projects which nobody sees, mainly with the libxml2 example, but OpenPrinting is appearing twice, too:

    youtube.com/watch?v=8PTlYeLBKv
    Problem of finding volunteers

    youtube.com/watch?v=8PTlYeLBKv
    Long time at Canonical, then funded by @sovtechfund and supported by @linuxfoundation

    #OpenPrinting #libxml2 #GNOME

  16. The story of is the one of struggle. So again and again, I'd call all to respect Open Source maintainers by creating only a waterproof ticket, adding a (failing) test to explain it, and eventually, contribute. Most of the time the work is unpaid. You can chip in. hackaday.com/2025/12/23/libxml

  17. The story of #libxml2 is the one of #OpenSource struggle. So again and again, I'd call all #developers to respect Open Source maintainers by creating only a waterproof ticket, adding a (failing) test to explain it, and eventually, contribute. Most of the time the work is unpaid. You can chip in. hackaday.com/2025/12/23/libxml #Programming

  18. The story of #libxml2 is the one of #OpenSource struggle. So again and again, I'd call all #developers to respect Open Source maintainers by creating only a waterproof ticket, adding a (failing) test to explain it, and eventually, contribute. Most of the time the work is unpaid. You can chip in. hackaday.com/2025/12/23/libxml #Programming

  19. The story of #libxml2 is the one of #OpenSource struggle. So again and again, I'd call all #developers to respect Open Source maintainers by creating only a waterproof ticket, adding a (failing) test to explain it, and eventually, contribute. Most of the time the work is unpaid. You can chip in. hackaday.com/2025/12/23/libxml #Programming

  20. The story of #libxml2 is the one of #OpenSource struggle. So again and again, I'd call all #developers to respect Open Source maintainers by creating only a waterproof ticket, adding a (failing) test to explain it, and eventually, contribute. Most of the time the work is unpaid. You can chip in. hackaday.com/2025/12/23/libxml #Programming

  21. 📢 Libxml2 échappe de peu à l’abandon : deux nouveaux mainteneurs prennent le relais
    📝 Selon Hackaday, libxml2 — une bibliothèque centrale pour le traitement **XML/XSLT** utilisée dans **GNOME**, des **navigateurs web** et de...
    📖 cyberveille : cyberveille.ch/posts/2025-12-2
    🌐 source : hackaday.com/2025/12/23/libxml
    #CVE #libxml2 #Cyberveille

  22. The #libxml2 situation is a sad one. It sucks that big tech companies refuse to fund a library that is so critical to their products.

    Let it be known that I support Nick, the now-former, original maintainer of the project.

    #opensource #funding #gnome

  23. The #libxml2 situation is a sad one. It sucks that big tech companies refuse to fund a library that is so critical to their products.

    Let it be known that I support Nick, the now-former, original maintainer of the project.

    #opensource #funding #gnome

  24. The #libxml2 situation is a sad one. It sucks that big tech companies refuse to fund a library that is so critical to their products.

    Let it be known that I support Nick, the now-former, original maintainer of the project.

    #opensource #funding #gnome

  25. The #libxml2 situation is a sad one. It sucks that big tech companies refuse to fund a library that is so critical to their products.

    Let it be known that I support Nick, the now-former, original maintainer of the project.

    #opensource #funding #gnome

  26. So, libxml2 developer fed up with the lack of commitment from Google, Red Hat and Amazon.

    A library used by Chrome, Windows, macOS, iOS, Linux, and most tech stacks in the world: now abandoned.

    Seems that the only way to force big corpo to care is to offer an AGPLv3 version and a commercial version.

    gitlab.gnome.org/GNOME/libxml2

    To me, that should be the base standard.

    #Linux #FOSS #FLOSS #OSS #OpenSource #FreeOpenSource #OpenSourceSoftware #Software #libxml2 #XML

  27. So, libxml2 developer fed up with the lack of commitment from Google, Red Hat and Amazon.

    A library used by Chrome, Windows, macOS, iOS, Linux, and most tech stacks in the world: now abandoned.

    Seems that the only way to force big corpo to care is to offer an AGPLv3 version and a commercial version.

    gitlab.gnome.org/GNOME/libxml2

    To me, that should be the base standard.

    #Linux #FOSS #FLOSS #OSS #OpenSource #FreeOpenSource #OpenSourceSoftware #Software #libxml2 #XML

  28. So, libxml2 developer fed up with the lack of commitment from Google, Red Hat and Amazon.

    A library used by Chrome, Windows, macOS, iOS, Linux, and most tech stacks in the world: now abandoned.

    Seems that the only way to force big corpo to care is to offer an AGPLv3 version and a commercial version.

    gitlab.gnome.org/GNOME/libxml2

    To me, that should be the base standard.

    #Linux #FOSS #FLOSS #OSS #OpenSource #FreeOpenSource #OpenSourceSoftware #Software #libxml2 #XML

  29. So, libxml2 developer fed up with the lack of commitment from Google, Red Hat and Amazon.

    A library used by Chrome, Windows, macOS, iOS, Linux, and most tech stacks in the world: now abandoned.

    Seems that the only way to force big corpo to care is to offer an AGPLv3 version and a commercial version.

    gitlab.gnome.org/GNOME/libxml2

    To me, that should be the base standard.

    #Linux #FOSS #FLOSS #OSS #OpenSource #FreeOpenSource #OpenSourceSoftware #Software #libxml2 #XML

  30. So, libxml2 developer fed up with the lack of commitment from Google, Red Hat and Amazon.

    A library used by Chrome, Windows, macOS, iOS, Linux, and most tech stacks in the world: now abandoned.

    Seems that the only way to force big corpo to care is to offer an AGPLv3 version and a commercial version.

    gitlab.gnome.org/GNOME/libxml2

    To me, that should be the base standard.

    #Linux #FOSS #FLOSS #OSS #OpenSource #FreeOpenSource #OpenSourceSoftware #Software #libxml2 #XML

  31. In all seriousness, libxml2 situation is good example of this strange limbo state of all critical libraries. Companies are chasing quick money and zero spending, so they are absolutely don't want to spend even bare minimum on supporting libraries like this. Ok, possibly RedHat as always will pick up the slack, but overall, I agree with sentiment.
    It is disheartening to see software industry in general being way worse shit house than it was before. It is creaking at seems #libxml2 #software

  32. In all seriousness, libxml2 situation is good example of this strange limbo state of all critical libraries. Companies are chasing quick money and zero spending, so they are absolutely don't want to spend even bare minimum on supporting libraries like this. Ok, possibly RedHat as always will pick up the slack, but overall, I agree with sentiment.
    It is disheartening to see software industry in general being way worse shit house than it was before. It is creaking at seems #libxml2 #software

  33. In all seriousness, libxml2 situation is good example of this strange limbo state of all critical libraries. Companies are chasing quick money and zero spending, so they are absolutely don't want to spend even bare minimum on supporting libraries like this. Ok, possibly RedHat as always will pick up the slack, but overall, I agree with sentiment.
    It is disheartening to see software industry in general being way worse shit house than it was before. It is creaking at seems #libxml2 #software

  34. In all seriousness, libxml2 situation is good example of this strange limbo state of all critical libraries. Companies are chasing quick money and zero spending, so they are absolutely don't want to spend even bare minimum on supporting libraries like this. Ok, possibly RedHat as always will pick up the slack, but overall, I agree with sentiment.
    It is disheartening to see software industry in general being way worse shit house than it was before. It is creaking at seems #libxml2 #software

  35. In all seriousness, libxml2 situation is good example of this strange limbo state of all critical libraries. Companies are chasing quick money and zero spending, so they are absolutely don't want to spend even bare minimum on supporting libraries like this. Ok, possibly RedHat as always will pick up the slack, but overall, I agree with sentiment.
    It is disheartening to see software industry in general being way worse shit house than it was before. It is creaking at seems #libxml2 #software

  36. This academic search engine relies on #libxml2 in several places. After harvesting bibliographic metadata (mostly OAI XML) from thousands of publication repositories, we process it using libxml2 and #libxslt.

    We are operating on a tiny budget, so all we can do is to hope that the maintainer of libxslt will be able to cope with maintaining libxml2 as well (as he just offered) – and extend our gratitude to the #FreeSoftware community on whose shoulders we are standing.

  37. This academic search engine relies on #libxml2 in several places. After harvesting bibliographic metadata (mostly OAI XML) from thousands of publication repositories, we process it using libxml2 and #libxslt.

    We are operating on a tiny budget, so all we can do is to hope that the maintainer of libxslt will be able to cope with maintaining libxml2 as well (as he just offered) – and extend our gratitude to the #FreeSoftware community on whose shoulders we are standing.

  38. This academic search engine relies on #libxml2 in several places. After harvesting bibliographic metadata (mostly OAI XML) from thousands of publication repositories, we process it using libxml2 and #libxslt.

    We are operating on a tiny budget, so all we can do is to hope that the maintainer of libxslt will be able to cope with maintaining libxml2 as well (as he just offered) – and extend our gratitude to the #FreeSoftware community on whose shoulders we are standing.