Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.os.linux.misc > #89055 > unrolled thread

Not Much LINUX Stuff of Late

Started byc186282 <c186282@nnada.net>
First post2026-07-26 01:09 -0400
Last post2026-07-27 20:04 +0200
Articles 20 on this page of 95 — 17 participants

Back to article view | Back to comp.os.linux.misc


Contents

  Not Much LINUX Stuff of Late c186282 <c186282@nnada.net> - 2026-07-26 01:09 -0400
    Re: Not Much LINUX Stuff of Late rbowman <bowman@montana.com> - 2026-07-26 07:22 +0000
      Re: Not Much LINUX Stuff of Late c186282 <c186282@nnada.net> - 2026-07-26 20:37 -0400
        Re: Not Much LINUX Stuff of Late rbowman <bowman@montana.com> - 2026-07-27 01:16 +0000
    Re: Not Much LINUX Stuff of Late John McCue <jmclnx@gmail.com.invalid> - 2026-07-26 20:00 +0000
      Re: Not Much LINUX Stuff of Late "Carlos E. R." <robin_listas@es.invalid> - 2026-07-26 22:40 +0200
        Re: Not Much LINUX Stuff of Late c186282 <c186282@nnada.net> - 2026-07-26 21:10 -0400
      Re: Not Much LINUX Stuff of Late Farley Flud <ff@gnulinux.rocks> - 2026-07-26 21:24 +0000
        Re: Not Much LINUX Stuff of Late rbowman <bowman@montana.com> - 2026-07-27 01:02 +0000
          Re: Not Much LINUX Stuff of Late Farley Flud <ff@gnulinux.rocks> - 2026-07-27 02:59 +0000
            Re: Not Much LINUX Stuff of Late c186282 <c186282@nnada.net> - 2026-07-26 23:18 -0400
            Re: Not Much LINUX Stuff of Late Epherma <epherma@remort.app.invalid> - 2026-07-26 20:31 -0700
              Re: Not Much LINUX Stuff of Late Farley Flud <ff@gnulinux.rocks> - 2026-07-27 04:35 +0000
                Re: Not Much LINUX Stuff of Late The Natural Philosopher <tnp@invalid.invalid> - 2026-07-27 06:37 +0100
                  Re: Not Much LINUX Stuff of Late c186282 <c186282@nnada.net> - 2026-07-27 23:45 -0400
                    Re: Not Much LINUX Stuff of Late rbowman <bowman@montana.com> - 2026-07-28 18:10 +0000
                  Re: Not Much LINUX Stuff of Late Farley Flud <ff@gnulinux.rocks> - 2026-07-28 15:17 +0000
                    Re: Not Much LINUX Stuff of Late The Natural Philosopher <tnp@invalid.invalid> - 2026-07-28 16:22 +0100
                Re: Not Much LINUX Stuff of Late Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-07-27 11:51 -0400
                  Re: Not Much LINUX Stuff of Late Farley Flud <ff@gnulinux.rocks> - 2026-07-27 16:22 +0000
              Re: Not Much LINUX Stuff of Late Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-27 04:42 +0000
                Another XLibre and/or Wayland subthread (was: Re: Not Much LINUX Stuff of Late) Nuno Silva <nunojsilva@invalid.invalid> - 2026-07-27 08:48 +0100
                  Re: Another XLibre and/or Wayland subthread Richard Kettlewell <invalid@invalid.invalid> - 2026-07-27 17:19 +0100
                    Re: Another XLibre and/or Wayland subthread Farley Flud <ff@gnulinux.rocks> - 2026-07-27 16:40 +0000
                      Re: Another XLibre and/or Wayland subthread rbowman <bowman@montana.com> - 2026-07-27 21:22 +0000
                        Re: Another XLibre and/or Wayland subthread John Ames <commodorejohn@gmail.com> - 2026-07-27 14:44 -0700
                          Re: Another XLibre and/or Wayland subthread rbowman <bowman@montana.com> - 2026-07-27 23:37 +0000
                        Re: Another XLibre and/or Wayland subthread Farley Flud <ff@gnulinux.rocks> - 2026-07-27 21:47 +0000
                          Re: Another XLibre and/or Wayland subthread Farley Flud <ff@gnulinux.rocks> - 2026-07-28 00:24 +0000
                            Re: Another XLibre and/or Wayland subthread rbowman <bowman@montana.com> - 2026-07-28 04:23 +0000
                          Re: Another XLibre and/or Wayland subthread rbowman <bowman@montana.com> - 2026-07-27 23:46 +0000
                          Re: Another XLibre and/or Wayland subthread The Natural Philosopher <tnp@invalid.invalid> - 2026-07-28 10:07 +0100
                        Re: Another XLibre and/or Wayland subthread Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-07-27 17:57 -0400
                          Re: Another XLibre and/or Wayland subthread rbowman <bowman@montana.com> - 2026-07-28 00:03 +0000
                        Re: Another XLibre and/or Wayland subthread Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-07-28 04:11 +0000
                          Re: Another XLibre and/or Wayland subthread Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-28 04:38 +0000
                          Re: Another XLibre and/or Wayland subthread rbowman <bowman@montana.com> - 2026-07-28 18:19 +0000
                Re: Not Much LINUX Stuff of Late Farley Flud <ff@gnulinux.rocks> - 2026-07-27 16:11 +0000
                  Re: Not Much LINUX Stuff of Late The Natural Philosopher <tnp@invalid.invalid> - 2026-07-27 18:27 +0100
            Re: Not Much LINUX Stuff of Late rbowman <bowman@montana.com> - 2026-07-27 04:46 +0000
              Re: Not Much LINUX Stuff of Late Farley Flud <ff@gnulinux.rocks> - 2026-07-27 15:47 +0000
              Re: Not Much LINUX Stuff of Late c186282 <c186282@nnada.net> - 2026-07-27 23:45 -0400
                Re: Not Much LINUX Stuff of Late rbowman <bowman@montana.com> - 2026-07-28 18:03 +0000
            Re: Not Much LINUX Stuff of Late The Natural Philosopher <tnp@invalid.invalid> - 2026-07-27 06:35 +0100
          Re: Not Much LINUX Stuff of Late Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-07-27 16:12 +0000
            Re: Not Much LINUX Stuff of Late rbowman <bowman@montana.com> - 2026-07-27 21:07 +0000
        Re: Not Much LINUX Stuff of Late c186282 <c186282@nnada.net> - 2026-07-26 21:19 -0400
          Re: Not Much LINUX Stuff of Late Farley Flud <ff@gnulinux.rocks> - 2026-07-27 03:08 +0000
            Re: Not Much LINUX Stuff of Late c186282 <c186282@nnada.net> - 2026-07-26 23:19 -0400
              Re: Not Much LINUX Stuff of Late Farley Flud <ff@gnulinux.rocks> - 2026-07-27 03:30 +0000
              Re: Not Much LINUX Stuff of Late "Carlos E. R." <robin_listas@es.invalid> - 2026-07-27 15:07 +0200
                Re: Not Much LINUX Stuff of Late Farley Flud <ff@gnulinux.rocks> - 2026-07-27 15:48 +0000
                  Re: Not Much LINUX Stuff of Late The Natural Philosopher <tnp@invalid.invalid> - 2026-07-27 18:27 +0100
                    Re: Not Much LINUX Stuff of Late Farley Flud <ff@gnulinux.rocks> - 2026-07-28 01:02 +0000
                      Re: Not Much LINUX Stuff of Late The Natural Philosopher <tnp@invalid.invalid> - 2026-07-28 10:10 +0100
                Re: Not Much LINUX Stuff of Late c186282 <c186282@nnada.net> - 2026-07-28 00:01 -0400
                  Re: Not Much LINUX Stuff of Late The Natural Philosopher <tnp@invalid.invalid> - 2026-07-28 10:19 +0100
                  Re: Not Much LINUX Stuff of Late "Carlos E. R." <robin_listas@es.invalid> - 2026-07-28 11:37 +0200
                  Re: Not Much LINUX Stuff of Late rbowman <bowman@montana.com> - 2026-07-28 17:43 +0000
          Re: Not Much LINUX Stuff of Late Marc Haber <mh+usenetspam2616@zugschl.us> - 2026-07-27 16:22 +0200
            Re: Not Much LINUX Stuff of Late Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-27 23:07 +0000
            Re: Not Much LINUX Stuff of Late c186282 <c186282@nnada.net> - 2026-07-28 00:10 -0400
              Re: Not Much LINUX Stuff of Late Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-07-28 04:20 +0000
                Re: Not Much LINUX Stuff of Late Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-28 04:40 +0000
                Re: Not Much LINUX Stuff of Late Marc Haber <mh+usenetspam2616@zugschl.us> - 2026-07-28 10:48 +0200
              Re: Not Much LINUX Stuff of Late Marc Haber <mh+usenetspam2616@zugschl.us> - 2026-07-28 10:24 +0200
              Re: Not Much LINUX Stuff of Late The Natural Philosopher <tnp@invalid.invalid> - 2026-07-28 10:24 +0100
                Re: Not Much LINUX Stuff of Late rbowman <bowman@montana.com> - 2026-07-28 17:22 +0000
              Re: Not Much LINUX Stuff of Late rbowman <bowman@montana.com> - 2026-07-28 17:16 +0000
      Re: Open-Source Armchair Critics At It Again Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-26 22:51 +0000
        Re: Open-Source Armchair Critics At It Again Robert Heller <heller@deepsoft.com> - 2026-07-26 23:27 +0000
          Re: Open-Source Armchair Critics At It Again c186282 <c186282@nnada.net> - 2026-07-26 21:23 -0400
            Re: Open-Source Armchair Critics At It Again rbowman <bowman@montana.com> - 2026-07-27 04:42 +0000
              Re: Open-Source Armchair Critics At It Again c186282 <c186282@nnada.net> - 2026-07-27 23:43 -0400
                Re: Open-Source Armchair Critics At It Again "Carlos E. R." <robin_listas@es.invalid> - 2026-07-28 11:57 +0200
                  Re: Open-Source Armchair Critics At It Again The Natural Philosopher <tnp@invalid.invalid> - 2026-07-28 11:06 +0100
                Re: Open-Source Armchair Critics At It Again Rich <rich@example.invalid> - 2026-07-28 15:22 +0000
          Re: Open-Source Armchair Critics At It Again Nuno Silva <nunojsilva@invalid.invalid> - 2026-07-27 09:00 +0100
            Re: Open-Source Armchair Critics At It Again c186282 <c186282@nnada.net> - 2026-07-27 23:47 -0400
              Re: Open-Source Armchair Critics At It Again The Natural Philosopher <tnp@invalid.invalid> - 2026-07-28 10:18 +0100
              Re: Open-Source Armchair Critics At It Again rbowman <bowman@montana.com> - 2026-07-28 17:11 +0000
        Re: Open-Source Armchair Critics At It Again rbowman <bowman@montana.com> - 2026-07-27 01:10 +0000
        Re: Open-Source Armchair Critics At It Again Andreas Eder <a_eder_muc@web.de> - 2026-07-27 15:45 +0200
          Re: Open-Source Armchair Critics At It Again Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-07-27 16:16 +0000
          Re: Open-Source Armchair Critics At It Again The Natural Philosopher <tnp@invalid.invalid> - 2026-07-27 18:24 +0100
            Re: Open-Source Armchair Critics At It Again "Carlos E. R." <robin_listas@es.invalid> - 2026-07-27 19:55 +0200
              Re: Open-Source Armchair Critics At It Again The Natural Philosopher <tnp@invalid.invalid> - 2026-07-28 09:59 +0100
                Re: Open-Source Armchair Critics At It Again "Carlos E. R." <robin_listas@es.invalid> - 2026-07-28 11:59 +0200
                  Re: Open-Source Armchair Critics At It Again The Natural Philosopher <tnp@invalid.invalid> - 2026-07-28 11:25 +0100
                    Re: Open-Source Armchair Critics At It Again rbowman <bowman@montana.com> - 2026-07-28 17:07 +0000
                  Re: Open-Source Armchair Critics At It Again rbowman <bowman@montana.com> - 2026-07-28 17:00 +0000
      Re: Not Much LINUX Stuff of Late rbowman <bowman@montana.com> - 2026-07-27 00:59 +0000
        Re: Not Much LINUX Stuff of Late Nuno Silva <nunojsilva@invalid.invalid> - 2026-07-27 08:54 +0100
      Re: Not Much LINUX Stuff of Late c186282 <c186282@nnada.net> - 2026-07-26 21:08 -0400
        Re: Not Much LINUX Stuff of Late "Carlos E. R." <robin_listas@es.invalid> - 2026-07-27 20:04 +0200

Page 2 of 5 — ← Prev page 1 [2] 3 4 5  Next page →


#89090

FromLawrence D’Oliveiro <ldo@nz.invalid>
Date2026-07-27 04:42 +0000
Message-ID<1146njj$2tuqd$3@dont-email.me>
In reply to#89088
On Sun, 26 Jul 2026 20:31:31 -0700, Epherma wrote:

> See also the suppression of Xlibre by huge corporate interests.

I wonder how that works; does anybody come round to your house and
tell you not to install XLibre? Do cryptic messages pop up on your TV
or radio every time you think about installing XLibre? Do you find
your downloads of XLibre mysteriously dropping out? Do you find,
instead of an XLibre package on your machine, just a text file saying
“don’t try this again -- or else”?

[toc] | [prev] | [next] | [standalone]


#89095 — Another XLibre and/or Wayland subthread (was: Re: Not Much LINUX Stuff of Late)

FromNuno Silva <nunojsilva@invalid.invalid>
Date2026-07-27 08:48 +0100
SubjectAnother XLibre and/or Wayland subthread (was: Re: Not Much LINUX Stuff of Late)
Message-ID<11472fn$30n9l$2@dont-email.me>
In reply to#89090
On 2026-07-27, Lawrence D’Oliveiro wrote:

> On Sun, 26 Jul 2026 20:31:31 -0700, Epherma wrote:
>
>> See also the suppression of Xlibre by huge corporate interests.
>
> I wonder how that works; does anybody come round to your house and
> tell you not to install XLibre? Do cryptic messages pop up on your TV
> or radio every time you think about installing XLibre? Do you find
> your downloads of XLibre mysteriously dropping out? Do you find,
> instead of an XLibre package on your machine, just a text file saying
> “don’t try this again -- or else”?

I think you're confusing manipulation by corporate interests with
dystopian science fiction.

You may have had a point there, but it seems to me you completely ruined
any chance of a serious argument with these exaggerated examples?

-- 
Nuno Silva

[toc] | [prev] | [next] | [standalone]


#89109 — Re: Another XLibre and/or Wayland subthread

FromRichard Kettlewell <invalid@invalid.invalid>
Date2026-07-27 17:19 +0100
SubjectRe: Another XLibre and/or Wayland subthread
Message-ID<wwvv7a0tngh.fsf@LkoBDZeT.terraraq.uk>
In reply to#89095
Nuno Silva <nunojsilva@invalid.invalid> writes:
> On 2026-07-27, Lawrence D’Oliveiro wrote:
>> On Sun, 26 Jul 2026 20:31:31 -0700, Epherma wrote:
>>> See also the suppression of Xlibre by huge corporate interests.
>>
>> I wonder how that works; does anybody come round to your house and
>> tell you not to install XLibre? Do cryptic messages pop up on your TV
>> or radio every time you think about installing XLibre? Do you find
>> your downloads of XLibre mysteriously dropping out? Do you find,
>> instead of an XLibre package on your machine, just a text file saying
>> “don’t try this again -- or else”?
>
> I think you're confusing manipulation by corporate interests with
> dystopian science fiction.
>
> You may have had a point there, but it seems to me you completely
> ruined any chance of a serious argument with these exaggerated
> examples?

I assume you mean “suppression of Xlibre by huge corporate interests” is
is exaggerated, since Lawrence’s response is so obviously sarcastic.

It seems to me that the reality is that it’s largely ignored. Partly
that’s due to of adoption of Wayland, perhaps, but it’s also
substantially because if you do need X11, Xorg remains readily
available.

  $ cat /etc/debian_version
  13.6
  $ dpkg -l xorg|tail -1
  ii  xorg           1:7.7+24+deb13u1 amd64        X.Org X Window System

-- 
https://www.greenend.org.uk/rjk/

[toc] | [prev] | [next] | [standalone]


#89111 — Re: Another XLibre and/or Wayland subthread

FromFarley Flud <ff@gnulinux.rocks>
Date2026-07-27 16:40 +0000
SubjectRe: Another XLibre and/or Wayland subthread
Message-ID<18c6331084faaaf8$15337$967852$802601b3@news.usenetexpress.com>
In reply to#89109
On Mon, 27 Jul 2026 17:19:10 +0100, Richard Kettlewell wrote:

> 
> It seems to me that the reality is that it’s largely ignored. Partly
> that’s due to of adoption of Wayland, perhaps, but it’s also
> substantially because if you do need X11, Xorg remains readily
> available.
> 

Here is yet another lackey who fails to understand the software
that he uses.

Only comparatively few programs use X11 directly (my fave text
editor, cooledit, is an example.)  Most programs employ graphical
toolkits like GTK+ or Qt which then in turn will invoke X11.

Well, guess what.  IBM/RedHat controls the development of GTK+
and they will most like pull the plug on X11 compatibility in
the future.  Only Wayland (surprise, surprise) will be supported.

Well, so what?  All GTK+ software will still function as usual.
Yes, but that only applies to application software.  Other software,
such as the long legacy of X11 window managers, will all be broken.

Do you desire to use one of the excellent and still maintained
X11 window managers?  Tough luck, bozo.  You won't be able to do so.
Why not?  Because IBM/RedHat has said so.  That's why not.  There
is no other reason.


-- 
Gentoo/LFS: Is there any-fucking-thing else?

[toc] | [prev] | [next] | [standalone]


#89121 — Re: Another XLibre and/or Wayland subthread

Fromrbowman <bowman@montana.com>
Date2026-07-27 21:22 +0000
SubjectRe: Another XLibre and/or Wayland subthread
Message-ID<ncq0g8FovvdU36@mid.individual.net>
In reply to#89111
On Mon, 27 Jul 2026 16:40:48 +0000, Farley Flud wrote:

> Well, guess what.  IBM/RedHat controls the development of GTK+
> and they will most like pull the plug on X11 compatibility in the
> future.
> Only Wayland (surprise, surprise) will be supported.

Who controls Qt?  I never liked Gtk but I've been playing with it lately. 
I still don't like it. Ridiculously long function names that all start 
with gtk_ are a pain in the ass.

It's ironic Gtk was developed because Qt wasn't 'free'. Be careful of what 
you wish for.

[toc] | [prev] | [next] | [standalone]


#89122 — Re: Another XLibre and/or Wayland subthread

FromJohn Ames <commodorejohn@gmail.com>
Date2026-07-27 14:44 -0700
SubjectRe: Another XLibre and/or Wayland subthread
Message-ID<20260727144410.000049a2@gmail.com>
In reply to#89121
On 27 Jul 2026 21:22:16 GMT
rbowman <bowman@montana.com> wrote:

> Who controls Qt?

Used to be Nokia; these days it's apparently some manner of alliance
between a publically-traded company and an open-source governing body,
both specifically dedicated to it. The company is Finnish; I dunno
about the org. Qt definitely seems less prone to infestation with Design
Divas than the competition, in my observation.

[toc] | [prev] | [next] | [standalone]


#89133 — Re: Another XLibre and/or Wayland subthread

Fromrbowman <bowman@montana.com>
Date2026-07-27 23:37 +0000
SubjectRe: Another XLibre and/or Wayland subthread
Message-ID<ncq8dtFovvdU37@mid.individual.net>
In reply to#89122
On Mon, 27 Jul 2026 14:44:10 -0700, John Ames wrote:

> On 27 Jul 2026 21:22:16 GMT rbowman <bowman@montana.com> wrote:
> 
>> Who controls Qt?
> 
> Used to be Nokia; these days it's apparently some manner of alliance
> between a publically-traded company and an open-source governing body,
> both specifically dedicated to it. The company is Finnish; I dunno about
> the org. Qt definitely seems less prone to infestation with Design Divas
> than the competition, in my observation.

It started out as Trolltech. The trolls were great coders but their 
licensing was arcane. It was free for personal or open source use, but 
there was a license for commercial use. Unfortunately the commercial terms 
were so murky that it discouraged use. Like everything else it's been 
through changes of ownership. It was the commercial part that spurred the 
development of Gtk and GNOME. 

That seems to follow Qt. PyQt is developed by Riverbank Computing and has 
both GPL and commercial licensing. Nokia wanted to release it as LGPL but 
Riverbank refused so Nokia, and later the Qt Company developed their own 
Python bindings and released it as PySide under LGPL. 'Side' is supposedly 
Finnish for 'binding' but I think it really means 'Screw you, Riverbank!'

The two are very close but the official Python version is PySide6. 

[toc] | [prev] | [next] | [standalone]


#89123 — Re: Another XLibre and/or Wayland subthread

FromFarley Flud <ff@gnulinux.rocks>
Date2026-07-27 21:47 +0000
SubjectRe: Another XLibre and/or Wayland subthread
Message-ID<18c643c7e3918e59$13824$874455$802601b3@news.usenetexpress.com>
In reply to#89121
On 27 Jul 2026 21:22:16 GMT, rbowman wrote:

> 
> Who controls Qt?  I never liked Gtk but I've been playing with it lately. 
> I still don't like it. Ridiculously long function names that all start 
> with gtk_ are a pain in the ass.
> 

Yes.  They have even hijacked all the standard C type names in favor
of their own.  Hence C "int" becomes "gtk_int" although they designate
the exact same thing.

Also, faithfully following the latest fashion trends, they eschew
the standard configuration files in favor of CSS markup.  Modifying
a simple font or color now requires a weeks-long odyssey of exploration. 



But it's not only GTK+ and Qt but also the plethora of other other
graphical toolkits, such as Xforms, Fltk, Motif, Tk, etc., that
will suffer with the enforced demise of X11.

With one fell stroke IBM/RedHat will have destroyed all alternatives
and forced everyone into its cattle pen.

But the lackeys on this NG won't ever notice.  All that they
can muster is the installation of Ubuntu/Mint and then play
their frivolous games.  They are not savvy USERS; they are tawdry
MOOCHERS.

GNU/Linux is for true *users*, i.e. people that study and modify
the FOSS software to suit their own needs.

In a few years, my predictions will have proved true, but the
morons on this NG will not have the mental capacity to ever notice.

Corporations love stupid sheep.


-- 
Gentoo/LFS: Is there any-fucking-thing else?

[toc] | [prev] | [next] | [standalone]


#89129 — Re: Another XLibre and/or Wayland subthread

FromFarley Flud <ff@gnulinux.rocks>
Date2026-07-28 00:24 +0000
SubjectRe: Another XLibre and/or Wayland subthread
Message-ID<18c64c64d78eb25b$11352$566809$802601b3@news.usenetexpress.com>
In reply to#89123
On 27 Jul 2026 23:46:29 GMT, rbowman wrote:

> 
> I spent part of the last 25 years working with Motif. Even the legacy GUIs 
> on Windows used Motif with the NutCracker runtime and PTC X server. With 
> that much history the Motif code was completely entwined with XLib and Xt. 
> You're correct that the Gtk and Qt APIs sheltered you from getting down 
> and dirty with X11. The frontend replacement for the legacy GUIs was web 
> based Angular. No way could Motif be salvaged. What we did with placement, 
> app-defaults, IPC using XAtoms and so forth was exactly what the Wayland 
> people consider evil.
>

Both GTK+ and Qt can be built with, as of now, an optional Wayland
integration using libwayland.  Of course, X11 integration has been
the standard default for both.

However, LibreOffice, which can utilize either GTK+, Qt, or pure
X11 frontends, demands that GTK+ be built with Wayland integration
otherwise it will not run.  This is true even if LibreOffice
runs only within an X11 session.

The trend is obvious.  LibreOffice is another project that considers
only the dictates of the mainstream distros.  I have been told as
much when reporting issues on the LibreOffice forums.  Their developers
will not ever address fringe concerns.

But, getting back to graphical toolkits, I believe that Fltk also
allows Wayland integration but the other common toolkits, such as
Tk, Motif, and xforms do not and likely never will.

IBM/RedHat gets its money from servers and hence security is, to
them, of paramount importance.  Their Wayland product has been
designed from the ground up with security in mind.  Each program
can only run in isolation with no IPC.  This may be fine for
a public-facing server but it is a detriment to desktop workstations.

Thus, productive desktop workstations will suffer tremendously
just so those IBM/RedHat bastards can rake in more profit.





-- 
Gentoo/LFS: Is there any-fucking-thing else?

[toc] | [prev] | [next] | [standalone]


#89139 — Re: Another XLibre and/or Wayland subthread

Fromrbowman <bowman@montana.com>
Date2026-07-28 04:23 +0000
SubjectRe: Another XLibre and/or Wayland subthread
Message-ID<ncqp56FovvdU40@mid.individual.net>
In reply to#89129
On Tue, 28 Jul 2026 00:24:58 +0000, Farley Flud wrote:

> Both GTK+ and Qt can be built with, as of now, an optional Wayland
> integration using libwayland.  Of course, X11 integration has been the
> standard default for both.

I believe that is handled in GDK.  

https://en.wikipedia.org/wiki/GDK

pkg-config --libs gtk+-3.0

-lgtk-3 -lgdk-3 -lpangocairo-1.0 -lcairo-gobject -lgdk_pixbuf-2.0 
-latk-1.0 -lpango-1.0 -lcairo -lharfbuzz -lgio-2.0 -lgobject-2.0 
-lglib-2.0 -lz


I get the same libs on Ubuntu 26.04 which is Wayland and MX 25.2 which is 
X11. /usr/include/gtk-3.0/gdk has both x11 and wayland subdirectories. I 
assume it gets sorted out there although I don't see any obvious #ifdef or 
other switch.

[toc] | [prev] | [next] | [standalone]


#89132 — Re: Another XLibre and/or Wayland subthread

Fromrbowman <bowman@montana.com>
Date2026-07-27 23:46 +0000
SubjectRe: Another XLibre and/or Wayland subthread
Message-ID<ncq8ulFovvdU38@mid.individual.net>
In reply to#89123
On Mon, 27 Jul 2026 21:47:08 +0000, Farley Flud wrote:

> But it's not only GTK+ and Qt but also the plethora of other other
> graphical toolkits, such as Xforms, Fltk, Motif, Tk, etc., that will
> suffer with the enforced demise of X11.

I spent part of the last 25 years working with Motif. Even the legacy GUIs 
on Windows used Motif with the NutCracker runtime and PTC X server. With 
that much history the Motif code was completely entwined with XLib and Xt. 
You're correct that the Gtk and Qt APIs sheltered you from getting down 
and dirty with X11. The frontend replacement for the legacy GUIs was web 
based Angular. No way could Motif be salvaged. What we did with placement, 
app-defaults, IPC using XAtoms and so forth was exactly what the Wayland 
people consider evil.

[toc] | [prev] | [next] | [standalone]


#89145 — Re: Another XLibre and/or Wayland subthread

FromThe Natural Philosopher <tnp@invalid.invalid>
Date2026-07-28 10:07 +0100
SubjectRe: Another XLibre and/or Wayland subthread
Message-ID<1149rhd$3tkg5$4@dont-email.me>
In reply to#89123
On 27/07/2026 22:47, Farley Flud wrote:
> On 27 Jul 2026 21:22:16 GMT, rbowman wrote:

> Also, faithfully following the latest fashion trends, they eschew
> the standard configuration files in favor of CSS markup.  Modifying
> a simple font or color now requires a weeks-long odyssey of exploration.
> 

> 
> 
> But it's not only GTK+ and Qt but also the plethora of other other
> graphical toolkits, such as Xforms, Fltk, Motif, Tk, etc., that
> will suffer with the enforced demise of X11.
> 
Thank fuck for that.
90s cruft, all off it.
The fact that they all exist shows that X was never a solution by itself

> With one fell stroke IBM/RedHat will have destroyed all alternatives
> and forced everyone into its cattle pen.
> 
Yes. There will be nothing left to get religious about, will there?

> But the lackeys on this NG won't ever notice.  All that they
> can muster is the installation of Ubuntu/Mint and then play
> their frivolous games.  They are not savvy USERS; they are tawdry
> MOOCHERS.
And proud to be so.

> 
> GNU/Linux is for true *users*, i.e. people that study and modify
> the FOSS software to suit their own needs.
> 
Ah, the true zealot

> In a few years, my predictions will have proved true, but the
> morons on this NG will not have the mental capacity to ever notice.
> 
No, we will be dead.

> Corporations love stupid sheep.
> 
Twas ever thus..

> 

-- 
“Puritanism: The haunting fear that someone, somewhere, may be happy.”

H.L. Mencken, A Mencken Chrestomathy

[toc] | [prev] | [next] | [standalone]


#89124 — Re: Another XLibre and/or Wayland subthread

FromChris Ahlstrom <OFeem1987@teleworm.us>
Date2026-07-27 17:57 -0400
SubjectRe: Another XLibre and/or Wayland subthread
Message-ID<1148k8p$3ig27$1@dont-email.me>
In reply to#89121
rbowman wrote this screed in ALL-CAPS (fixed):

> On Mon, 27 Jul 2026 16:40:48 +0000, Farley Flud wrote:
>
>> Well, guess what.  IBM/RedHat controls the development of GTK+
>> and they will most like pull the plug on X11 compatibility in the
>> future.
>> Only Wayland (surprise, surprise) will be supported.
>
> Who controls Qt?

    The Qt Company: Acts as the main commercial driver, holding
    the rights to commercial licenses, setting the roadmap for
    core development, and providing professional tools and quality
    assurance.

    Qt Group Plc: The parent public company headquartered in
    Espoo, Finland, that oversees business operations and
    commercialization.Open Source ContributionThe

    Qt Project: An open-source governance model where individual
    developers and external organizations (such as Intel or KDAB)
    contribute code, review patches, and maintain specific modules
    alongside internal maintainers.

> I never liked Gtk but I've been playing with it lately. 
> I still don't like it. Ridiculously long function names that all start 
> with gtk_ are a pain in the ass.

I like the C++ wrapper, gtkmm. I forked a project that used that,
and liked that framework.

But when I decided to upgrade the project and provide a Windows
version, I started with another fork that used Qt, because it
seemed like Qt's cross-platform support was a bit better.

That was years ago, and I've gotten used to Qt. (The project can
be built without a GUI and run as a headless app.)

> It's ironic Gtk was developed because Qt wasn't 'free'. Be careful of what 
> you wish for.

Gtk is C code, while Qt is C++ code, and is supporting newer C++
constructs such as using lambda functions as slots.

I once wrote an audio player using C, simulating "classes" via
unions.  It was so instructive I never did that again.

-- 
Anything labeled "NEW" and/or "IMPROVED" isn't.  The label means the
price went up.  The label "ALL NEW", "COMPLETELY NEW", or "GREAT NEW"
means the price went way up.

[toc] | [prev] | [next] | [standalone]


#89134 — Re: Another XLibre and/or Wayland subthread

Fromrbowman <bowman@montana.com>
Date2026-07-28 00:03 +0000
SubjectRe: Another XLibre and/or Wayland subthread
Message-ID<ncq9urFovvdU39@mid.individual.net>
In reply to#89124
On Mon, 27 Jul 2026 17:57:44 -0400, Chris Ahlstrom wrote:

> I once wrote an audio player using C, simulating "classes" via unions. 
> It was so instructive I never did that again.

When I look at C++ I envision what it's doing under the hood to provide 
the syntactic sugar. Not pretty. I never cared much for full blown every 
trick in the book C++ and if I use it it looks like C With Classes. For 
that matter the early edition of Stroustrup's book that I have looks about 
the same. 

Esri's API was C++/COM and it took some getting used to 'smart pointers'. 
You start of with 'IFeaturePtr pFeature'. That's pretty straight forward. 
A feature has a geometry, so pFeature->get_Shape(&pGeometry) makes sense. 
And then..

ICurvePtr  pCurve = pGeometry;

WTF? pCurve has a bunch of methods that pGeometry doesn't.

Esri finally switched to C# thankfully.

[toc] | [prev] | [next] | [standalone]


#89137 — Re: Another XLibre and/or Wayland subthread

FromCharlie Gibbs <cgibbs@kltpzyxm.invalid>
Date2026-07-28 04:11 +0000
SubjectRe: Another XLibre and/or Wayland subthread
Message-ID<XZV9S.21$wI58.19@fx44.iad>
In reply to#89121
On 2026-07-27, rbowman <bowman@montana.com> wrote:

> On Mon, 27 Jul 2026 16:40:48 +0000, Farley Flud wrote:
>
>> Well, guess what.  IBM/RedHat controls the development of GTK+
>> and they will most like pull the plug on X11 compatibility in the
>> future.
>> Only Wayland (surprise, surprise) will be supported.
>
> Who controls Qt?  I never liked Gtk but I've been playing with it lately. 
> I still don't like it. Ridiculously long function names that all start 
> with gtk_ are a pain in the ass.
>
> It's ironic Gtk was developed because Qt wasn't 'free'. Be careful of what 
> you wish for.

I haven't done much GUI programming in Linux.  I'd like to port my Windows
stuff and I've done some experimenting, but I wound up using GTK instead
of Qt simply because only GTK has C bindings and I didn't want to have to
rewrite everything in C++.

-- 
/~\  Charlie Gibbs                  |  In this world there are
\ /  <cgibbs@kltpzyxm.invalid>      |  two kinds of people:
 X   I'm really at ac.dekanfrus     |  1. Those who can extrapolate
/ \  if you read it the right way.  |  from incomplete data.

[toc] | [prev] | [next] | [standalone]


#89140 — Re: Another XLibre and/or Wayland subthread

FromLawrence D’Oliveiro <ldo@nz.invalid>
Date2026-07-28 04:38 +0000
SubjectRe: Another XLibre and/or Wayland subthread
Message-ID<1149bne$3p5ep$1@dont-email.me>
In reply to#89137
On Tue, 28 Jul 2026 04:11:35 GMT, Charlie Gibbs wrote:

> I haven't done much GUI programming in Linux. I'd like to port my
> Windows stuff and I've done some experimenting, but I wound up using
> GTK instead of Qt simply because only GTK has C bindings and I
> didn't want to have to rewrite everything in C++.

I’ve been using GTK from Python almost by default. The “GI Repository”
system provides good bindings, for Python and other high-level
languages. I wanted a GUI that had a decent event loop -- i.e.
poll(2)-style event handling, not busy-waiting, so that ruled out
Tkinter.

Currently I have been experimenting a bit with this
<https://pywebview.flowrl.com/>.

[toc] | [prev] | [next] | [standalone]


#89166 — Re: Another XLibre and/or Wayland subthread

Fromrbowman <bowman@montana.com>
Date2026-07-28 18:19 +0000
SubjectRe: Another XLibre and/or Wayland subthread
Message-ID<ncsa61FovvdU49@mid.individual.net>
In reply to#89137
On Tue, 28 Jul 2026 04:11:35 GMT, Charlie Gibbs wrote:

> On 2026-07-27, rbowman <bowman@montana.com> wrote:
> 
>> On Mon, 27 Jul 2026 16:40:48 +0000, Farley Flud wrote:
>>
>>> Well, guess what.  IBM/RedHat controls the development of GTK+ and
>>> they will most like pull the plug on X11 compatibility in the future.
>>> Only Wayland (surprise, surprise) will be supported.
>>
>> Who controls Qt?  I never liked Gtk but I've been playing with it
>> lately. I still don't like it. Ridiculously long function names that
>> all start with gtk_ are a pain in the ass.
>>
>> It's ironic Gtk was developed because Qt wasn't 'free'. Be careful of
>> what you wish for.
> 
> I haven't done much GUI programming in Linux.  I'd like to port my
> Windows stuff and I've done some experimenting, but I wound up using GTK
> instead of Qt simply because only GTK has C bindings and I didn't want
> to have to rewrite everything in C++.

Usually if I'm doing GUIs on Linux I use PySide6 (PyQt6) but PyGtk isn't 
bad either. I've recently been playing with straight Gtk. VS Code is a 
little weird, at least of Ubuntu. You need to create a task.json to pick 
up the pkg-config stuff and there are some strange GTK_ environment 
variables that try to pick up nonexistent libs if you try to run the app 
from the Code terminal like 'Failed to load module "canberra-gtk-module"'. 
Unsetting them solves the problem. In a Konsole terminal only 
'GTK_MODULES=gail:atk-bridge' exists. 

[toc] | [prev] | [next] | [standalone]


#89106

FromFarley Flud <ff@gnulinux.rocks>
Date2026-07-27 16:11 +0000
Message-ID<18c63174a651b656$15334$967852$802601b3@news.usenetexpress.com>
In reply to#89090
On Mon, 27 Jul 2026 04:42:27 -0000 (UTC), Lawrence D’Oliveiro wrote:

> 
> I wonder how that works; does anybody come round to your house and
> tell you not to install XLibre? Do cryptic messages pop up on your TV
> or radio every time you think about installing XLibre? Do you find
> your downloads of XLibre mysteriously dropping out? Do you find,
> instead of an XLibre package on your machine, just a text file saying
> “don’t try this again -- or else”?
>

If you didn't have your head firmly up your ass (don't cry little
snowflake) you would be well aware of what is already very old news:

<https://lists.x.org/archives/xorg-devel/2025-June/059396.html>

<https://linuxiac.com/xlibre-xserver-project-plans-revival-of-x11/>


To explain things simply, GNU/Linux cannot make enough money for
IBM/RedHat if it contains too much variety and choice.  It therefore
*must* be transformed into a monolithic OS with a standard user interface
and standard everything else, just like M$/Apphole.

If you actually *understood* the software that you so willingly mooch
you would also be well aware that this always was, and still is, the
raison detre for systemd.

Your blatant ignorance makes you more of an enemy than a supporter
of GNU/Linux/FOSS.





-- 
Gentoo/LFS: Is there any-fucking-thing else?

[toc] | [prev] | [next] | [standalone]


#89116

FromThe Natural Philosopher <tnp@invalid.invalid>
Date2026-07-27 18:27 +0100
Message-ID<11484en$3c3hi$10@dont-email.me>
In reply to#89106
On 27/07/2026 17:11, Farley Flud wrote:
> Your blatant ignorance makes you more of an enemy than a supporter
> of GNU/Linux/FOSS.
Pot Kettle Black
-- 
Climate Change: Socialism wearing a lab coat.

[toc] | [prev] | [next] | [standalone]


#89092

Fromrbowman <bowman@montana.com>
Date2026-07-27 04:46 +0000
Message-ID<nco64hFovvdU25@mid.individual.net>
In reply to#89083
On Mon, 27 Jul 2026 02:59:44 +0000, Farley Flud wrote:

> On 27 Jul 2026 01:02:48 GMT, rbowman wrote:
> 
>> On Sun, 26 Jul 2026 21:24:43 +0000, Farley Flud wrote:
>> 
>>> The GNU project needs to make their Hurd kernel a top priority as the
>>> future of Linux is total corporate domination with a lack of freedom.
>> 
>> The GNU project needs to realize strict microkernels didn't work 0
>> years ago and still don't work. When ideology meets reality guess which
>> loses.
>>
>>
> That's not the overall point though, is it?
> 
> Even though it was not stated it was certainly implied.  The GNU project
> needs to develop its own kernel whether it be Hurd or something else.

The overall point is GNU has not been able to deliver. Why is that? 

[toc] | [prev] | [next] | [standalone]


Page 2 of 5 — ← Prev page 1 [2] 3 4 5  Next page →

Back to top | Article view | comp.os.linux.misc


csiph-web