Re: SOLVED: export vs. save menu in gimp2.8 - simple and lasting solution
Hi Dirk,
IMO the "save as vs export" issue isn't the real problem with new
versions of GIMP. The problem are e.g. Windows that are transparent, but
can't moved away, so that they cover the artwork we want to work on. New
sliders that do work, but show wrong mouse cursors, instead of the
let-right arrow the up arrow etc.. I used GIMP a lot, nowadays I use it
seldom, however, it's easy to get used to the new export option, but the
workflow when doing artwork IMO is interrupted by at least an unready
new style. Looks like GIMP does flirt with tablet PCs.
You'll find idiocy for many apps that were good in the past. Try to sort
the Firefox history, when using recent versions and then search by
klicken for something. All the time you click a link, the cursor will
follow the link, while you want to click the next link, below or over
the position where the link was you clicked, but when the link gets
opened, Firefox resort the history and you have to search the original
position, because the focus is on the wrong link you clicked at first.
There are many apps and IMO the only way to manage those issues, is to
replace such software.
Ok, replacing a browser is possible, replacing a production app, e.g.
GIMP, can be impossible. A chroot or virtual machine is a nice
workaround, but not a solution to the issues we have with upstream.
Btw. professionals using the known proprietary competitor experience
similar issues, but they have the advantage that they can run outdated
versions on their known proprietary operating systems without
workarounds.
The so called advantage of Linux, the shared libraries, is a drawback.
I wish more people would launch apps using a terminal emulation, or care
about their ~/.xsession-errors file. They would notice that the voodoo
they sometimes experience isn't voodoo and claims that Linux users
always have the choice between alternatives isn't true. Upstream tries
to force the users, to use some apps, with just one desktop environment.
A desktop environment tries to force the users to e.g. use a special
sound server, by adding an insane hard dependency etc. pp..
A chroot and a virtual machine are comparable to a multi-boot. We don't
need to reboot, but anyway add tons of libs and for e.g. GIMP we also
need to double all the fonts, that are already installed outside the
chroot or virtual machine. IMO this is a no-go.
2 Cents,
Ralf
Reply to: