lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:   Tue, 05 Nov 2019 16:08:07 +0000
From:   gameonlinux@...chan.it
To:     linux-kernel@...r.kernel.org, debian-user@...ts.debian.org
Subject: Proposal: More GTK1 (and 2) programs. (Reviving use of these
 libraries in free systems, for efficiency and avoidance of lock-in)

It has been noted that GTK1 and GTK2 were the GIMP ToolKit and were 
fairly efficient, and allowed the creation of programs that could run on 
a wide variety of hardware; however GTK3 is Gnome*'s ToolKit.

GTK1 was lightweight, and fairly straight forward, and was built by the 
GIMP hackers.
GTK2 was aswell, but introduced things similar to a "windows registry" 
for gfx, however it increased the options the hackers had when creating 
their programs.
GTK3 is quite slow, removes many options, and is controlled by Gnome 
with no input by the hackers, and is not a Gnu project, essentially. No 
hacker can rely on it: only the Gnome programmers at the Gnome 
foundation can.

*(now "Gnome: they stopped being "GNOME" in 2012 since they didn't want 
to be an acronym associated with Gnu any longer (see: their mailing list 
regarding "rebranding"))

GTK3 is unsuited for the poor who do not have access to 
high-memory-bandwith modern computers (note: I just switched to one, 
after my old desktop failed: there is much difference), great amounts of 
memory, and fast tertiary storage (SSDs). It is also controlled by a 
foundation, not the hackers, who seems to act like the corporate 
entities the hackers rejected.

So my proposal is that GTK1 and GTK2 programs be written again, and the 
libraries be included in distributions of GNU/Linux again thusly: to 
avoid being taken down a river by Gnome.

Recently I wished to use a free-software program from a project I 
contributed to a decade+ ago. Seems like yesterday that I was 
contributing to it.

I got gtk1.2, and glib1.2, had to patch it to work with gcc3x ( 
glib-1.2.10-gcc34-1.patch ), and use the c89 option, also compiled 
libpng-1.4.22 (after that they removed code that was relied upon) , 
compiled it all, and was able to use my GTK1 program.

It worked fine. It was fast, and was no different than it had ever been, 
but the Gnome folks would make it seem as if Gimp's 2 tool kits are dead 
and you have to follow their development (they even use slow Javascript 
for their stuff aswell, instead of C: slowing things down even more). 
They're just trying to lock us in: they've all-ready taken control of 
they system away from the hackers and given it to their employees, who 
they direct.

Can we step back into the promised land, together?
Must we be lead by the nose by these foundation-managers and their 
workers that they own?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ