Hacker Newsnew | past | comments | ask | show | jobs | submit | lightwords's commentslogin

You know what? The hate GIMP gets in the comments is entirely self-inflicted. Everyone praises Krita and Blender because their UIs are consistent and look good. GIMP, on the other hand, looks like a toddler worked on it: switches are huge compared to text, buttons and text have no padding and are squeezed together, and icons are oversized and scattered everywhere.

People might say, "You can just join the project and fix it yourself." But the team and community actively resist change and sabotage efforts to make GIMP more mainstream.


I once tried to use GIMP and gave up after 2 hours and got the task done in figma in 10 minutes. GIMP is a UX atrocity. The interface is a cluttered mess of meaningless panels and buttons. Worst for me is i'd spend 15 mins googling/reading how to do something, look for the corresponding buttons for 10 minutes, be unable to find them, and later discover they were on a panel that wasn't enabled by default (I didn't even know you had to enable panels; i'd assumed everything that was available was there in front of me). On macOS some panels randomly disappear behind other programs.

It was like using a computer program in your dreams where things don't really have to make sense.

My theory is this is a classic OSS problem where everyone wants to contribute their pet feature but the project lacks discipline and nobody wants to remove, organise, and improve (especially where the latter can be 10x harder and more tedious then the former). This could be an argument for opinionated leaders in OSS projects, because at least they'll say 'no' and do things 'their' way a lot of the time, which is often better than the 'anything goes' philosophy.


> I once tried to use GIMP and gave up after 2 hours and got the task done in figma in 10 minutes.

You would have been just as lost, if not more, in Photoshop (if you had never used it before.) You were doing a simple job that should have been done in a simple program.


GIMP still lags behind the photoshop I used in the late 90s/early 2000s. Then there is the name thing. I am *NOT* telling anyone else how to feel about it. I have no interest in relitigating it, but I am disabled and had it thrown at me as a term of hate; I just can't support a piece of software that uses it. We each have to stand up for what matters to us.


Friendly reminder to everyone that https://photopea.com exists. If you are used to Photoshop, then the UI will be quite familiar.

I only need to do somewhat basic stuff these days, so photopea.com is more than enough for me. However, now that I look it has tons of new features. Nothing to install, is ad-sponsored by default, and runs entirely client-side.

IIRC, this is a lone developer, who has previously refused what seemed like lucrative catch & kill acquisition offers.

Here is a post with lots of info:

https://news.ycombinator.com/item?id=33334521


It is an impressive piece of software, and there are lots of other low(er) cost alternatives to Photoshop; but I think the broad appeal of GIMP is that it it is free in the GPL sense of freedom, not just as in beer and that can't be ignored in any discussion of the software. Also the fact that you can use it fully offline


My favorite part about Photopea is it is a PWA so you can use it offline as well


It's been like this forever. Always been "photoshop but harder to use".


We actually have a design site where we ask for user feedback and UX/UI improvement suggestions: https://gitlab.gnome.org/Teams/GIMP/Design/gimp-ux/-/work_it...

I share this link a lot in the hopes that more people take us up on it, and provide specifics on where problem areas are for their workflow. So many people use GIMP in so many different ways, even something that seems "obviously bad" to one group might not be encountered by others.


Thoughts on posting a UX and/or workflow related Issue under Teams/GIMP/Design/gimp-ux that would pretty much just recite an existing Issue from GNOME/gimp?


One of our contributors does a lot of upkeep work, and he normally ports UX-related issues from the code tracker to the UX repo. Not 100% perfect, but it helps keep the focus in the right spot.


Am I reading this right in that I should avoid doing it myself then?


If you think it's UX related concern, then I'd recommend posting it on the UX tracker first. But even if it's posted in the "wrong place", it'll likely be moved to the right one after it's looked at, if that makes sense?

However, if you see an older issue that could use some UX design discussion, feel free to suggest it be moved.


Alright, got it. Thanks


Why not add a "Photoshop" theme? You select it in some option or on install, and it turns into something looking like Photoshop.


We're working on an extension platform, and once that's up and running we'll probably reach out to PhotoGIMP developers (https://github.com/Diolinux/Photogimp) and see if they want to host it there.

Then people can easily download and install it directly in GIMP, hopefully making everyone happy.


From tfa

> A lot of new and existing contributors have submitted improvements to GIMP’s user interface and its user experience. We wanted to highlight their efforts, and encourage you all to continue sharing your feedback on our design issue tracker.

I see no active resistance. If you have feedback, maybe share it with them?


Between GIMP releases we saw entire graphics pipelines, conventions and workflows come and go. We had the Affinity suite, Canva, Paint.net, Clip Paint Studio, Sketch, various attempts from Adobe at expanding beyond the Photoshop ecosystem (Anyone remembers XD?), probably something else I’m missing right now. Now we’re in the age of Figma, with its own UI and quirks.

At this point it’s probably easier to accept that the GIMP UI is simply what GIMP developers want it to be.

True, it doesn’t make a lick of sense, but the same could be said about Turbotax, Jira, SAP… or God may have mercy on your soul, Avid Pro Tools.

It is what it is. It’s not like there are no alternatives anymore.


It could also be that the Gimp team and community wants their software a certain way, and I don't see why one should disrespect that?

Those who disagree are welcome to fork- and maintain it, if the users see value in it, they'll switch.


It could be that the Gimp team and community are so self-selecting, defensive, and idiosyncratic that they drive everyone else who wants to change (read as "improve") it out of the team and community before letting them do anything to fix it. Gimp stands out among applications I've used as having enduring bad UX for decades, and it's hard to imagine a reason for it other than that efforts to improve it are unwelcome. Even Blender, which I once thought was the only thing worse than Gimp, has successfully turned that around. The reputation that Gimp has for its poor UX is not a random coincidence that a cursed meteor struck it of all open source projects, it's an enduring social problem with exactly that team and community that has earned it that reputation. This enduring social problem won't be fixed by this attitude of "we want it a certain way", that's just defensiveness displacing the critical thinking that was actually needed all along.

The suggestion to fork it is in bad faith. A fork goes nowhere unless a critical mass of the development community goes with it, and if you've already driven away the critical mass that could sustain a fork, that can never happen. Don't worry, Gimp is safe, I don't think anyone organized enough to fix its problems thinks it's worth the effort anymore, they're all working on other things instead.


It's just sad. Nobody wants to fork it because nobody uses GIMP, so forks get almost no traction. People love the effort and commitment, install it, try it for a couple of tasks, fail, and never come back. It has built up this reputation of being terrible, and no one wants to give it a second chance after their first impression.

I think it's a lesson in how not to run an open-source project. I put it in the same category as Darktable, which gives off that exact same bad first impression.


> People love the effort and commitment, install it, try it for a couple of tasks, fail, and never come back.

If you just tried Photoshop 2 or 3 times, you'd fail to get anything accomplished either. GIMP is a Photoshop replacement, not an MS Paint replacement.

Maybe the problem is that not everyone needs Photoshop, or to learn a tool at all, and GIMP comes as standard on every Linux install. Most people never have a need for it. They only need MS Paint (or rather Paint.NET or Krita.)

Thinking that you should be able to just roll in and immediately get stuff accomplished on Photoshop or GIMP is a misjudgment of the skill it takes to use professional tools.

GIMP's UI is fantastic, and its capabilities are incredible.

edit: another problem is that people make a living from using Photoshop because it's an industry standard, so they're motivated to learn it. For GIMP you had to take the same effort to learn something that you couldn't use professionally. Hopefully the improvements on color and non-destructive editing will improve the situation on that front. It's becoming something that, if I have the latitude, I can use on the job at a print shop.


If you just tried Photoshop 2 or 3 times, you'd fail to get anything accomplished either.

This is is simply not true. Photoshop is popular even with non-tech users because it is possible to do things in Photoshop without having to figure out an illogical UI.


? people take literal classes to learn Photoshop. I took a course at a rec center in high school in the 2000s and it had a bunch of adults learning it for work.


In the early 2000s, people were taking classes to learn how to use Word. Now even grandma uses Word without thinking about it.

We're talking about 2026. GIMP had an excuse for its UI back in 1999. It doesn't anymore.


Word is both simpler and more widespread. Also you'd be surprised. My boomer parents are not Word wizards lol.

PS isn't that much simpler or more intuitive now than back then. It's an inherently more complicated tool.


darktable is at least slowly actually getting better... I like what blender managed to do.


The attitude partly affects GNOME too, any time you'd constructively criticize it on places like their Issue tracker or r/gnome, their defenders would come with pitchforks at you. Glad I moved to KDE nearly a decade ago.


Gnome does UX and UI very well, though.


I honestly think a lot of the hate that GIMP gets is because as the first major FOSS image editor, people tried to use it for everything with a lot of square hole round peg situations.

In particular, it’s a photo editor at core. You can use it for postprocessing of other image types if you want, or for pasting together memes or whatever. But it’s not designed for e.g. doing illustrations or digital painting or sketches

This isn’t even unique to GIMP in that way. Photoshop is also a sub par art program (though admittedly they’re a little more flexible than GIMP). But if you wanted something better for than Photoshop and were ok with proprietary windows/mac software there’s clip studio paint and before that there was paint tool sai etc.

While until the rise of Krita being actually good (having tried it many times over the years prior, that’s some time around 2018) if you wanted Linux or just wanted FOSS, you had to use Gimp and that breed resentment at it being the wrong tool


Finally, specific criticisms that aren’t “it’s not Photoshop!”


Word of warning Temporal relies on the Intl API for formatting, and support in Chrome is very limited due to their binary size constraints. As a result, you'll need to polyfill unsupported languages using format.js


  $ du -sh '/Applications/Google Chrome.app'
   1.3G    /Applications/Google Chrome.app


There are numerous reports on this being an issue e.g. https://issues.chromium.org/issues/40624456


Thanks for the heads up. Will think on this and will probably just document the polyfill.


That's complete crazy.


Format.js polyfills a lot of stuff that's already supported in modern browsers, and seems to prefer its own polyfills to the native APIs.

Is there any way to force it to only use (and bundle) the polyfills that are needed assuming 2025+ era browsers?


This happens all the time. All NATO countries rotate their fighter jets to Iceland at some interval. This has nothing to do with the Greenland situation.


You usually don't want to carry a passport with you at all times. In some European countries (e.g., the Nordics), you have your ID, driver’s license, firearm license, etc., all in a government app that can be verified with an app used by officials. You can also sign and authenticate all paperwork with the same system


I use my passport to verify my right to work in the US during the first week of my job, and then I don't bring it any other time. So unless you're changing jobs very frequently it shouldn't be necessary to carry all the time. A bigger issue would be that many people do not have passports.


I would trust the Nordic governments to write an app to put on my phone and not slurp up all my data and spy on me with it. I can't say the same about the British government


Denmark is the largest supporter of Chat Control


Good for them, but I don't see why we need this, or indeed why that's a good thing?


Easy and cheap regular checks on the spot presential or/and online, as frequently as you want vs rare scheduled difficult and expensive checks.

Possibilities get realised such as regular remote checks (ie selfie to prove you are the id owner holder, address proof, etc, flagging odd id holder behaviour or employer, etc). Currently, you cannot do this, no visibility into who works where and where that person even resembles the person meant to be working for [insert gig company].


I do selfie to prove I match my driver's license all the time (needed for app based banks, and so on)?

The government absolutely knows where I work, are you joking? That's what NI numbers are for. You seriously think there isn't a join table in a government database with my NI number and passport number?


There are other workers in the UK aside from you. The policy affects them too not just you. You are getting the business requirements wrong. You are unlikely to be the main reason for the policy. Folks getting paid under minimum wage such as some gig workers using someone else's identity are the main target.


If they arrived here legally won't they have a passport? Or national photo ID at the very least? If they are driving for Uber or deliveroo then they'll have a driver's license too? If they don't have either (or a UK birth certificate) then it's safe to say they're not a legit citizen?

Who exactly are we solving for?


> If they arrived here legally won't they have a passport? Or national photo ID at the very least? If they are driving for Uber or deliveroo then they'll have a driver's license too? If they don't have either (or a UK birth certificate) then it's safe to say they're not a legit citizen?

Simple. Overstaying or/and expired passport will lead to that. Valid status is not a fixed binary state. It is better described as a function of personal id, rights docs and current time. Currently, the checks are more akin to updating a Boolean column on rare occasions. Digital id countries do checks more like function calls that you can perform easily and quickly


RTW already requires ID plus NI, but OK what about if we just said 'free passports' and then said passport or driving licence plus NI is needed to get a job here. If you have a foreign passport and no UK driving licence then yes you'll have to keep that up to date in order to work here, c'est la vie.


To the extent this is technically possible, if the gig economy companies wanted to do this, they could do it already.

When the driver signs up, check their passport or driving license in the normal manner, and take a matching portrait you keep on file. Any time you want to, compare a selfie to the portrait on file.

Reason they don't do this is it's profitable to hire people who can't legally work in the UK, if they can get away with it - and the government lets them get away with it.


I don't see how it's a problem to stock all keyboard types, such as for the Nordics. It's the same layout, just with different letters. They could just have blank keyboards with the most commonly used layouts and put them in a laser etch jig for custom orders. Similar what they are doing now for screen protectors where they cut them in-store


Different layouts have different size return keys, for instance.


ANSI/ISO is the main difference I think.

Now, Japanese keyboard [1] is a whole other beast, but for the most part layouts customizing ANSI and ISO blanks should work just fine.

[1]: https://external-content.duckduckgo.com/iu/?u=https%3A%2F%2F...


Yeah, there are mostly only ANSI, ISO, and JIS physical layout in this world, stamped differently to suit needs. JIS is only ever used in Japanese so just blank ANSI and ISO should cover everything(emphasis on should; corrections are welcome).


It's clocking in at 120MB on my machine and launches instantly. I don't get this blind hate for Electron, it has made software runnable on more platform than ever with less development resources.


There is one amusing bug which might be related to this in Mazda 2018. If you add the same station twice to your favourites(easy to accidentally do) and then you click the station lower in the list the UI kicks you up and down in the list endlessly. This is because on each render it checks your station state and just pick the station with the same name randomly in the list.


Trying it for the first time in 3 years and it doesn't work on Mac OSX intel. Everything is huge and the the cursor hitpoint is off by 150-200px so you have to click above everything. Is anyone testing this software on the Apple hardware? Bizarre that a clean install on a 2 year old computer causes such issues.


Might be due to Skia graphics engine. It will be deactivated in 7.3.1. Could you try a pre-release version of 7.3.1: https://dev-builds.libreoffice.org/daily/libreoffice-7-3/Mac... ?


It's a USA thing. Where I'm from in the nordics they have bus advertisements with nipples on them. There is no issue with breastfeeding or semi-translucent clothing in most of Europe. Look at european cinema and TV, there is a lot of nudity.


Pinch to zoom is also non-existent so Firefox becomes useless for a many adults/elderly with poor eye-sight or even just many other users who like to browse and zoom on text/pictures etc. It's so frustrating that this feature is not available in Firefox when you are promoting it. The absence of this feature in my small survey is the main reason people quit using Firefox.


I'm honestly a bit confused. This is the second comment I've seen regarding the lack of this feature. It's not one I ever use purposefully, so maybe I just don't understand what's missing. But, with Firefox on my Samsung Galaxy, I can zoom in and out of text and photos by pinching, with no issues at all. Was it a long time ago when you last tried it perhaps?


Latest version on MacOS It's one of the primary gestures of MacOS, and is in heavy use with casual users. It's f.x the primary method of reading material on websites that my parents use.


(The trackpad gesture, is what you're getting at)


I think they mean desktop Firefox on a touchscreen laptop, rather than mobile Firefox. Personally, I can't imagine trying to pinch-zoom on a desktop, but maybe I'm just old.


They're talking about a gesture that's specific to the Macbook trackpad; namely, the implementation you see in Safari, which is not the typical browser 'zoom' function that increases the size of elements and reflows the page, but rather zooms in to show you a subset of the DOM canvas as rendered, like mobile browsers do. It is definitely a handy feature but to characterize it as a missing 'standard' functionality I don't think is fair. No desktop browser had this functionality until Safari ported it over from the mobile version a few releases back as I recall, though Chrome has since copied it.


On Microsoft Surface in tablet mode I often want to pinch zoom. It works but it's limited to the discrete zoom levels that you see with Ctrl+ and Ctrl- so you don't get the smooth zoom you get on Chrome. I still prefer FF for a variety of other reasons so to me it's just a nitpick.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: