xserver

erate a PDF with layout - there were no libraries Prawn was ok. hexapdf is even better. I regular try to get the hexapdf to improve the pdf-autogeneration part. Hexapdf is very good, so ... there were no libraries? Well, when exactly? Prawn is old: at the least 2008 https://rubygems.org/gems/prawn/versions/0.1.0 > You could no longer build native GUI applications - there were no libraries Well, ruby-gtk worked, even on windows by the way. Since then it has decayed. My modifications of GTK core classes no longer worked. I tried to get kou to think about this problem some years ago. Nothing changed, all my old code is dead. So I decided to call it quits and no longer use ruby-gtk. Also because of GTK5 going to abandon xorg-server. I fail to see why I want to support their wayland-only crap future. Let's see whether this will succeed though: https://github.com/X11Libre/xserver and: https://git.devuan.org/Daemonratte/gtk2-ng Granted, there may be a lack of developers for both, but do we really want to be locked down by corporate hackers that try to control the downstream situation? Both QT and GTK have this problem, for different reasons. I am absolutely tired of corporate shenanigans leaking into ecosystems and ruining them. > And a lot of people would just throw up their hands in desperation and > utter The Spell Of Dread: > Nobody does this sort of thing with Ruby anyway. Thankfully I could not care what others say. Unfortunately, Ruby is also declining, and has been in the last years. There is no way to deny it. The numbers are strong here. If you google for "ruby is dead", you will find things such as "no, it is aging like fine wine". People simply try to deny the reality - that's interesting. But it is not an analysis. > a Rubyist willing to produce PDF files from their Rails app would be facing a choice of a number of options, all equally unappealing Interesting how he does not mention hexapdf. Now, I am not claiming hexapdf may be able to solve all rails issues here, but what is interesting is how he does not even know all possibilities in ruby. Is he a rails guy or something? He mentions: Gotenberg, Ferrum, Prawn and wkhtmltopdf. I stopped reading there. IMO if you critisize DHH, and this is well-deserved after the damage he caused in the ruby ecosystem, followed up by him hating on wolves and then casually ... mentioning how immigrants are like wolves (I have no idea what DHH is thinking; I think he is roleplaying the promo-role and in reallife probably acts totally orthogonal to the crap he writes in general), then you really really need to be super-sound in all arguments. Be it the comparison to Weimar (and then kind of wanting to omit how Weimar in some ways, not all, but some, helped build up the Nazi idiots) or not knowing hexapdf ... I am sorry, but that means you failed at doing your prior research. Personally I already find hexapdf to be better than prawn. And you can also try to convince the hexapdf author to improve hexapdf; he was willing to do so when he has time and the suggestion made sense.

of befriending him, but not directly relevant to his technical capabilities. The second kind is more worrying. Do you have a link to someone analyzing/considering the changes made to Xlibre relative to Xorg? Be that as it may - while this does not sway me into belief in Wayland, it does introduce a grain of salt into my view of the X side of things, and thank you for that.

to having too few useful features compared to xserver?

personally if Joe donates to abc or xyz.

is also not automatically better. Personally I am among the frequent update folks. I use ruby scripts to automatically update to the latest, in hope that the people who write code are not incompetent. There is no guarantee that newer software is automatically always better; it is a trade-off. I don't have the time and resource for infinite security audits. I need to get things done and this approach, different to the "everything is scary" crowd, works super-well for me. I use a versioned AppDir approach on linux though, so I don't run into many issues of "can not upgrade because of same .so name issue", so I can conveniently switch to other versions as-is, including the kernel. (Excluding ABI differences and glibc, but for about 98% of the programs this works very well. I am also not alone with the get-everything-working approach, see xserver or gtk2-ng: https://github.com/X11Libre/xserver https://git.devuan.org/Daemonratte/gtk2-ng - granted, for the linux kernel this does not work that well ... I think we need better strategies for the linux kernel, things such as copy.fail should not be possible. I have no good solution here, AI will find many more exploits. No clue how we can prevent this or mitigate this more easily. I was surprised when the local instructor showed us how easy it is to use python for gaining superuser access as-is.)

ood, if only to try to "reason" with mr. ebassi and other hardcore gnomeys; sadly KDE also goes that way with wayland-only, thanks to anti Robin Hood Nate and his donation-pester daemon. Oldschool KDE devs didn't waylay people for money, now it is "pay or get nagged", thanks to Natey Nate). We kind of need competition in the browser landscape, so in some ways having Ladybird is good. I don't really have much hope that ladybird will be able to challenge the evil Google empire though. But perhaps more people realise that Google controlling so much of the www-ecosystem (again, just look at how they nerfed google search in the last years) is a huge problem.

able alternative to the xorg-server. I don't want to lose any feature, so it is a drawback for me.