I don't get everyone's complaints about the interface. I've been using it for years, once you learn where things are I can get what I need done. The learning curve (finding where functions are, the right tools for each job, etc.) wasn't much different from other software like Blender or Darktable (or even Davinci Resolve).
The panels concept might be the most intuitive part of it, but Blender also has different panels and modes. And the tools being combined into few buttons is similar to CAD programs I've used.
Anyone enlighten me on actual usability problems (and not pedantry like "the spacing of these buttons is uneven"?)
I appreciate the backwards compatibility they highlight in the article, and more generally the ownership oss gives you over your files. My small business uses gimp, canva, and Inkscape, and they all have their purpose, but one of the complaints we have with canva is that itâs really hard to get the original files backed up somewhere, aside from canva itself. You have to download each file individually , which is quite a pain (please correct me if thereâs an easier way!). Gimps openness is an obvious path for oss, but really is a great feature. If the gimp team stops, weâll still be able to edit our gimp files. If the canva team stops, we mostly lose all the canva stuff.
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.
> 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?
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.
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.
Yep, even music software like Ableton Live is using zipped XML for the project files (although the much bigger audio files are stored independently in sub-folders). There were even efforts to use the XML format to manage Ableton project files with git in order to have a nicer change history (https://github.com/clintburgos/ableton-git).
I suddenly imagine a zip format with built-in git. Does this already exist?
Basically a file-format that has built-in history, rollback, logs etc. Enabling all these "zipped XML" formats to get this feature "for free".
Could be as simple as adding the .git to the zip and ensuring the software that writes the content to the zip also runs the correct git operations.
But could also be a simplified subset and adding git-ability to the (de)compress libs and bins, which can operate on the compressed .git. Simplified, because it won't need networking/remotes probably not even branches.
I mean, zipping files in an archive and presenting them as a file is an ancient tradition in video games. For example Warcraft 3 used the MoPaQ archive to store data in .w3x file.
Except MoPaQ weren't zips IIRC, they had their own clever format here - at least the OG StarCraft / SCBW MoPaQs were, playing with that is what I learned binary data handling on :). The idea of zipping data files applies, of course (and many a game used a literal ZIP with custom extension).
But there's one material difference between StarCraft/Warcraft and Gimp: in Blizzard games, those were "zips" of heavy data files, notably read only data blobs. The game would read them, unpack in memory, and serve appropriately. Most of that data was key-value, text resources, or flat assets - images, sfx. With Gimp, we're talking highly structured data that's continuously being mutated. Very much not the best representation for that, even if you're just persisting it. They're only getting away with this because of SSDs - on spinning rust, you'd feel this.
(Also worth noting that, at least in StarCraft/SCBW, most of the files inside were custom, well-optimized binary formats. This predated the XML insanity of encoding data with 90%+ markup overhead.)
// At this point, I'd like to take a moment to speak to you about the Adobe PSD format.
// PSD is not a good format. PSD is not even a bad format. Calling it such would be an
// insult to other bad formats, such as PCX or JPEG. No, PSD is an abysmal format. Having
// worked on this code for several weeks now, my hate for PSD has grown to a raging fire
// that burns with the fierce passion of a million suns.
// If there are two different ways of doing something, PSD will do both, in different
// places. It will then make up three more ways no sane human would think of, and do those
// too. PSD makes inconsistency an art form. Why, for instance, did it suddenly decide
// that *these* particular chunks should be aligned to four bytes, and that this alignement
// should *not* be included in the size? Other chunks in other places are either unaligned,
// or aligned with the alignment included in the size. Here, though, it is not included.
// Either one of these three behaviours would be fine. A sane format would pick one. PSD,
// of course, uses all three, and more.
// Trying to get data out of a PSD file is like trying to find something in the attic of
// your eccentric old uncle who died in a freak freshwater shark attack on his 58th
// birthday. That last detail may not be important for the purposes of the simile, but
// at this point I am spending a lot of time imagining amusing fates for the people
// responsible for this Rube Goldberg of a file format.
// Earlier, I tried to get a hold of the latest specs for the PSD file format. To do this,
// I had to apply to them for permission to apply to them to have them consider sending
// me this sacred tome. This would have involved faxing them a copy of some document or
// other, probably signed in blood. I can only imagine that they make this process so
// difficult because they are intensely ashamed of having created this abomination. I
// was naturally not gullible enough to go through with this procedure, but if I had done
// so, I would have printed out every single page of the spec, and set them all on fire.
// Were it within my power, I would gather every single copy of those specs, and launch
// them on a spaceship directly into the sun.
//
// PSD is not my favourite file format.
Non-destructive filter layers caught my eye, and has been something I've missed since moving off Windows/Photoshop to Linux. Looking around it seems like they introduced this in V3, which is great to see.
That is probably the V3 feature I'd notice most in daily use. Non-destructive editing makes experimentation much less costly; without it, every âmaybe this looks betterâ becomes another layer or file copy.
After the first run (where it has to evaluate plugins etc) it starts in under 4s on 26.04 on my Lenovo P53 (laptop from 2019). Which is admittedly not exactly snappy, but it's OK IMO.
As usual, whenever GIMP is involved, all we get are negative, often unfounded comments about an excellent piece of free software that is massively used and developed with very limited resources, doing its job really well.
Thereâs something so pleasant about having GIMP around, efficient and so far removed from the disgusting greed that drives so many of the projects featured here.
I know a lot of people don't like that but sometimes I feel that FOSS projects are intentionally sabotaging themselves by ignoring industry standard options/conventions and instead they are following open source ideas just to be different. GIMP is the perfect example of that and generally speaking UI/UX is the main symptom.
Blender was able to move forward by not listening to the FOSS crowd but to the industry. And see where are they now compared to GIMP.
important here to remember that Blender was created within the industry as a commercial tool. When open sourced the leader of the project remained and knew quite well what separated a good creative tool from a bad one. It was always situated in a position where the core users were either hobbyists or professionals.
Which brings us back to why so many people dislike Gimp, and/or see it as a posterchild example of bad FOSS alternatives.
I agree, and Culture IS important. And I think the culture around many Open Source "Alternatives" is harming themselves and the overall FOSS community. From Mastodon via Gimp to Nextcloud.
I don't know what it has to do with anything - GIMP has been around for a while and has been the de facto FOSS alternative for photoshop for so long. That doesn't make that several of its UX and UI decisions are at least questionable nor make that comment you're replying any less true.
Not to mention the fact that if you ever mention in any way that GIMP's UX/UI could be better to anyone of its veteran devs they would turn weirdly ultra defensive and take everything personal.
I love that GIMP exists but... I have to say, it never got rid of the "backend developer doing frontend" feeling, and I've been aware of Gimp for 20 years now (did not know how to...ehem, run photoshop in my teens)
Because I fail to see all the comments here as negative and unfounded.
(and my guess why there is often negativity towards GIMP, is because it was too often advertised as a adequate Photoshop replacement, which it is not, so people got disappointed with it)
⌠and the sizes of their updates are usually impressive! Seems to be a big project that is managed well to keep a good pace and keep the community in the loop. (Although I donât know much about their inner workings.)
Furthermore, it's free software. If people have a problem with it, they're free to show up and contribute, or fork if the community is really opposed to their ideas (they probably are for good reason, though).
I can guarantee that anyone turning up and contributing or forking this project will not lead to the outcome of a improved piece of software.
It will lead to someone with the insight on how to make actual material improvements frustrated and angry that they don't have the technical skill (or time) to grapple with a complex codebase, and the people with the technical skill working on the codebase dismiss people with actual knowledge in different domains.
"Patches welcome" is not any kind of welcome. It's basically a euphemism for "fuck off, I don't want to have a conversation to make something better, I just want to hack on Feature X".
Let's be honest, the real 1999 design would have been a custom binary format that happens to use the endian of the system it was developed on, and leaks bits and pieces of unflushed memory buffers whenever it writes to disk.
1999 is exactly right for the start of the XML hype, everything had to be XML, it would single handedly solve the software crisis (after OOP failed to do that) because everything would be able to talk to everything!
The whole Italian e-invoicing system is based on SOAP XML, and it's atrocious. They approved the specs in 2013, so it was already dated when it came out.
SQLar[1], see [2] for some reasoning around why a database is preferred over zipped XML. Though, I'd be fine with a DBM-style database too as we only need the key-value part of it.
The problem with using database blobs for load/save is that you usually need a full database client in the application. SQlite advertises that use case, but it is complete overkill. You never need to run any sort of complex SQL query on an image file format for instance. Using XML+ZIP in this day and age is also a strange decision, but at least that way the data is inspectable with unzip, a text editor and an image viewer (assuming they use a standard image format to store the raw pixel data).
Sqlite is probably overkill, you will probably never have actual relational data in an image format, But what it does bring to the table is a built in b-tree based storage, that is, you don't need to load the entire file into memory to edit it, in a prior age we would use Berkeley db for this. Sqlite in this role(a file format) is probably best thought of as a better superset of the berkleydb style key value store, more than one table per file and additional columns/indexes to keep metadata in.
Nothing wrong with XML, it is well understood, and the tooling is pretty good. But partial loads/edits is one thing it can not do.
Think of Lightroom or automation over files. Many semi professionals from wedding photographers to designers want some form of batch automation and organization system over their files.
Several megabytes/gigabytes assets and you want to extract metadata, a preview, running as a batch some filter/compression/, conversion to CMYK, text injection ... fast partial read/write access would be nice.
Right now, most reads are performed through indexes because those files are slow to read.
If we take 10k sqlite files and want to retrieve a row, we would be around 3s on SSD, maintaining preemptive indexes become less important for a lot of use cases.
Change management and versioning also becomes quite efficient - sqlite can be configured to not offset bytes, so CVS like Epic Lore can efficiently delta the files and store minimal delta, or the file format itself can keep its edit history. Oh and it's 3x-10x less bytes without compressing the whole thing, so pages are stable through time.
About needing SQLite client, it's real but it's roughly the same size as an XML parser.
> About needing SQLite client, it's real but it's roughly the same size as an XML parser.
what I like about it being XML is I can just open it with any text tool and inspect it. It's human readable so I can edit and debug it manually, no need to have a parser or an extra application just to see what's in my file
> You never need to run any sort of complex SQL query on an image file format for instance.
Sure you will. Plenty of features that don't exist, or are implemented badly, because you can't easily do it.
Quick mental translation table: if you think "iterate over every ..." or a `for` loop, that's your SELECT query. If you think about `if` conditions, that's the parts that go after FROM clause.
In order to have any advantage from this, you would have the added complexity of splitting your file format into tables that can be queried in a useful manner. However, for an image file format, you most likely need to hold the entire definition in memory at all times anyway. Assuming thatâs the case, doesnât XPath get you there most of the way (assuming XML), with _way_ less complexity?
Image data is just binary blobs. You aren't splitting that into channel columns or anything. But an image file for an editor like Gimp isn't one image blob. It's dozens or hundreds of them - one or more per layer - along with tons of associated metadata at every level.
All that tends to fit sensible schemas and managing it is what SQLite shines at.
I donât see how this addresses my point that zipped XML gives you the same thing, but simpler. I understand that a GIMP file is many images, so that makes a zip feel like a great fit to me. The only advantage I see for using a full-blown DB is ensuring consistency with references, which admittedly is a plus. But beyond that, what do you gain?
SQLite is fast, but it won't be faster than a hot loop in C. Having the loop construct dictated by the file format seems bad. For images it seems more reasonable to have them in-memory, except for huge image edge cases.
Images are the red herring. Pixel data is best read in hot loops in C, but that would be stored as blobs in SQLite anyway.
It's all the metadata around the image that's interesting. Images have layers, dozens or hundreds of them (this literally scales with how good your software is at handling those - the faster, and more powerful layer UX is, the more they get used). Some are pixel layers, other are effect layers, text layers, vector layers. Layers have metadata - names, sizes, colors, tags, types, special effects, and a bunch of other stuff I don't know because I don't use that 80% of features of GIMP/Photoshop/Affinity.
Then you have document level metadata, UI-specific metadata, etc. Also undo history. A lot of that is relevant to the work on images themselves, and changes in realtime, and can get even more useful if querying it wasn't such a PITA.
That - not the binary pixel blobs - is the selling case of using SQLite as application data format.
the SQLite archive format (it's probably worth linking to the main documentation[1], instead of the very old experimental repository) may not really be a good fit for something like GIMP's native file format. (To be clear, "SQLite archives" are not special compared to any other database: it's just a well-defined schema for an sqlar table, which the sqlite3 command line tool is able to create, update, and extract using syntax like the tar command.)
That being said, SQLite would still be a good choice, especially as it's a format that's really intended to be modified in-place, and has good data integrity features (eg: keep WAL enabled so that mid-save crashes/shutdowns don't corrupt your file), neither of which are provided by Zip. You could even just run zlib on data (be it XML or what have you) if optimizing the on-disk size of the file is desirable.
Yes, this is not too rare to see base64 images in JSON but I won't recommend that.
You gain back most of the base64 overhead when you compress it though. It's slower but probably often worth it if the alternative is few more async HTTP queries that you would only fetch once.
To answer seriously, my parent comment is a joke, JSON is a simpler format that maps better to most programming languages internal memory representations. Developers tend to prefer JSONâs simplicity over XML.
> most programming languages internal memory representations
Often heard wrt JSON but incorrect. It maps to the primitive types in JavaScript. But almost all programming languages treat floats and integers different, make distinction between char and strings and many have some form of date/time. JSON has neither.
In that direction, XML is much closer since every node is a triple (name, value, attributes) so can have type info, json is a tuple. And Protobuf, while not popular, gets this completely right.
I think it's too risky to treat numbers in JSON as something else than IEEE754 64bits floats. But yes, JSON is small and doesn't do datetimes, char, comments, and a million other things XML does.
But you don't need to think much about memory representation when you parse a JSON, and the developer experience is a lot more pleasing than browsing a XML tree. That what used to matter.
The problem was that people hyped it up as the solution for every problem and all the world's ills, so it wound up being used where it had no business being used (and therefore badly).
XML was a hammer used to bang in a lot of things that weren't remotely nail-shaped, and accordingly, a certain percentage of traumatised people despise it and react to any mention of it with fear and loathing.
It's kind of neat when you have an application for it that really leans into its strengths.
Thanks! I had the exact same question for various of these posts here. I know these may be different groups of people, but I always see people advocating for simplicity, and zipped-XML is as simple as it gets, needs barely any extra dependencies (none in GIMP I assume), and is proven to work well (Word etc).
I also donât understand why SQLite would be preferable here, considering you will likely also store large binary files alongside your document definition.. What does a db engine give me here?
The obvious alternative is SQLite, and it has many advantages. If you want to do a "zipped list of files", SQLite does that just fine (that's what SQLar is), but it can do so much richer data. Even if you don't want that, it still offers resiliency that "zipped XML" can't match: if your software or computer crashes in the middle of saving your file, it'll almost certainly corrupt it. With SQLite, not an issue: all transactions are atomic, they either happen entirely or not at all.
I don't know what "mature tooling" you're talking about for zipped XML, but I guarantee you it's not going to be better (or more mature) than SQLite and its ecosystem.
> For instance, weâre quite proud that a XCF file made by a small company for their logo in 1998 still renders the same way in the latest version of GIMP
How do they pronounce âXCFâ such that itâs âa XCF fileâ and not âan XCF fileâ? âXeceffâ?
> With âaâ vs âanâ, the pronunciation is more important than the spelling.
I know, hence my question about the pronunciation. If I had thought the spelling was more important, the âXâ would have settled it so I wouldnât have asked.
That effort didn't last long. I think this is the first I've heard about it since inception, the repo (assuming this is the right one, https://github.com/joshgiesbrecht/Glimpse, it was the only GIMP related thing that came up amongst a sea of unrelated projects with the same name) is hasn't seen a commit in 7 years and what appears to be the official site away from a forge (https://getglimpse.app/about/) is currently unresponsive.
I don't want to revel in the fork's demise for any reason besides relief that it didn't end up splitting GIMP's contributors and community in a way that would have harmed both projects.
> we could not find contributors willing to step up and help with non-code tasks like moderating communication channels
Gotta say though it feels ironic that they couldn't find enough people to be comment janitors considering the whole thing was based on wanting people to stop saying a particular word.
> As a result, we struggled to scale the project to match increasing demand.
âGlimpse didn't fail; it was actually too popularâ?
This wasn't even a serious project but an example of malicious virtue signaling with a long-term plan for sort of hostile takeover. People involved just took the original code and replaced every GIMP occurrence with Glimpse, added new logo/icon and called job done. Then went to the news sites trying to raise awareness of the supposed name controversy hoping noise will discredit GIMP while they'll portrait themselves as the saviors. Because who'd want to contribute to a software that has such bad reputation.
It's been over 24 years for me since I've used GIMP for the first time and the only problem that I had was always with GUI ergonomics. You had to understand everything anew after being more accustomed to proprietary software pieces. My friend never adapted to anything else but Photoshop - even Krita is beyond her abilities.
Nearly every discussion regarding GIMP on hn will include thread about the name 'problem' and this is getting tiresome. The name won't change and those who feel offended should focus on problems whose solution is genuinely productive.
> This wasn't even a serious project but an example of malicious virtue signaling with a long-term plan for sort of hostile takeover. People involved just took the original code and replaced every GIMP occurrence with Glimpse
I recall one of the reasons given on the GIMP Gitlab issue to change the name was "it will encourage more contributors" that apparently don't contribute because of the project name. Glimpse certainly had a lot of contributors... not.
I can't think of a single project that changed a name to satisfy these people ever received more contributors as a result.
I feel like it would have though if Glimpse had managed to become the default image editor on at least one major distro, just by virtue of people stumbling in to contributing some fix or addition to âthe thing that came with my OSâ without necessarily being aware of the history.
Like the FFmpeg/libav fork that eventually got back together. Or Compiz/Beryl, or Emacs/XEmacs, or GCC/EGCS, or whatever :)
I'm surprised it got that epithet, I'm used to "upset by weird sex stuff" as being a US-right position, and "woke" being a term that's used by US-right to denigrate US-left.
Then again, I'm also old enough to have seen it shift significantly in meaning at least once, and I think I'm seeing it shift meaning again.
Before the weird sex stuff, "gimp" was an insulting term for a crippled person. The fact that it's so long out of common use for that purpose that a lot of folks don't realize that is perhaps an argument for not taking it too seriously. On the other hand, disabled folks are certainly among the most oppressed and abused and in ways that aren't well-understood by most folks, so a decent person should be pretty careful about using language that could be demeaning. I dunno. It feels like an archaic term that ought not have any power today, but what do I know?
> Before the weird sex stuff, "gimp" was an insulting term for a crippled person. The fact that it's so long out of common use for that purpose that a lot of folks don't realize that is perhaps an argument for not taking it too seriously
It's a US specific slur when used in this context, not in other English speaking countries (let alone non-English countries) A lot of GIMP developers are European yet the Glimpse project tried to force American cultural/linguistic rules on a non-American project.
Words mean different things in different regions and languages, just because it's offensive in your language does not mean it's offensive in others.
In the UK, itâs the sex one and would be used as a general âidiotâ word but that seemed to have mostly faded away. Itâs not a word Iâve seen used in that context for many years.
Not refuting anything here, just adding some context from over here. Whichever way you slice it, itâs always been an awful name.
Yeah, it's always felt like an "edgy" name a teenager or quite young man would come up with. Which makes sense, the original GIMP authors were college-aged boys when they created it.
I'd like it if they changed the name. We're (the Open Source community) not teenagers or annoying college kids anymore, by and large.
I like it that the scruffy teenager hacker mentality is preserved in the name. It was also a bit of self deprecating humour at the time, because using Gimp instead of Photoshop did make you feel crippled a bit.
I hope they never give in to the corporate-lawyer induced bland-washing .
I'm just a Free Software user and developer and I think it's nicer when I can recommend something to someone without having to think about whether I might be saying something rude or hurtful. I assume there was a stink about the name because it bothers some disabled folks. It's not my place to tell them not to be bothered, I'd rather just not do the shitty thing that bothers them.
It seems cringey and childish to insist on doing a thing that makes a bunch of people feel unwelcome based on something about themselves they can't change. And, for what? So you can feel like a scruffy teenaged hacker?
I like my Free Software community to welcome people of all sorts.
Having a "stink" is right. Even without much thought, it's off-putting, does not sound professional and really icky. When you think a bit harder, it's just kinda awful. I do actually suspect the name does have some measurable impact on adoption. Most people don't want to say "I gave up photoshop, I use gimp." outside of hardcore linux circles and since then, it has gone from the only open source gig in town to just one of many alternatives.
The issue is that there are a bunch of people like this[0] who get incredibly upset and politicize any attempts to be "the adult in the room" and ask for renaming of unsavory names.
The funniest of these is when Europeans talk about how they are being "forced" to comply with American cultural norms and you go through their account and they are so deeply steeped in American culture due to their participation in the anglophone internet spaces which are dominated by them. People in Europe will argue with you that you are importing woke culture if you suggest that they shouldn't say the N word, but are seemingly completely oblivious to the fact that the reason they find the word exciting to say and they say it in English is an import of American culture
Pardon my ignorance about formats, but between XML & JSON, what would have made them choose XML? As I understand there is lot more tooling, standards & existing software examples around JSON for project & records management (e.g. VSCode's records as settings.json for example). Wasn't XML spearheaded by Microsoft but mostly used by Microsoft today?
json's only advantage is it's easier to write by hand, but that's not really a consideration here. XML has schema support and much more tooling available.
> As I understand there is lot more tooling, standards & existing software examples around JSON for project & records management
I don't understand why that is relevant; as long as there is a minimum level of tooling, libraries and support for their choice, what benefit would JSON bring over XML? I don't see a clear reason for one over the other.
Honestly, I'd have the same question if they chose JSON and someone asked why did they choose JSON over XML - Why wouldn't they?
> previous editions... used a sliver of the resources
Well of course, but given that the previously employed technique was blitting, fliedumping memory areas, you can't be more efficient than that. Using XML is for transparency (readability).
(And, note, in context, I regard the ms office file format as lousy. The OpenOffice/LibreOffice format is good.)
I don't think your parent comment was talking about the resources involved in saving a file, but rather the resources involved in running the software.
Thank you, probably so, but in that case I cannot see how said comment is consistent in the branch ("about file formats") - I do not get how it would follow.
I don't get everyone's complaints about the interface. I've been using it for years, once you learn where things are I can get what I need done. The learning curve (finding where functions are, the right tools for each job, etc.) wasn't much different from other software like Blender or Darktable (or even Davinci Resolve).
The panels concept might be the most intuitive part of it, but Blender also has different panels and modes. And the tools being combined into few buttons is similar to CAD programs I've used.
Anyone enlighten me on actual usability problems (and not pedantry like "the spacing of these buttons is uneven"?)
Autosave sounds nice, Iâm excited to have that!
I appreciate the backwards compatibility they highlight in the article, and more generally the ownership oss gives you over your files. My small business uses gimp, canva, and Inkscape, and they all have their purpose, but one of the complaints we have with canva is that itâs really hard to get the original files backed up somewhere, aside from canva itself. You have to download each file individually , which is quite a pain (please correct me if thereâs an easier way!). Gimps openness is an obvious path for oss, but really is a great feature. If the gimp team stops, weâll still be able to edit our gimp files. If the canva team stops, we mostly lose all the canva stuff.
Zipped XML
Preparation for the future XCF (24.09.2023)
https://gitlab.gnome.org/GNOME/gimp/-/work_items/10076
Someone proposed newer ser-/deserialization approaches, but this didn't result in a discussion.
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.
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?
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.
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'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.
darktable is at least slowly actually getting better... I like what blender managed to do.
Zipped XML? Isn't that just OpenRaster? (which is already supported by GIMP anyway, but also supported by Krita and other image editors)
> Krita and other image editors)
Krita is not an image editor but a digital painting program. GIMP is a much more complete image editor despite its quirks.
It's not that weird. Most of Office and Open office formats are just zipped folders of XMLs.
Better Zipped XML than whatever monstrosity Adobe files are. PDF/PSD... shudder.
Yep, even music software like Ableton Live is using zipped XML for the project files (although the much bigger audio files are stored independently in sub-folders). There were even efforts to use the XML format to manage Ableton project files with git in order to have a nicer change history (https://github.com/clintburgos/ableton-git).
> with git
I suddenly imagine a zip format with built-in git. Does this already exist?
Basically a file-format that has built-in history, rollback, logs etc. Enabling all these "zipped XML" formats to get this feature "for free".
Could be as simple as adding the .git to the zip and ensuring the software that writes the content to the zip also runs the correct git operations.
But could also be a simplified subset and adding git-ability to the (de)compress libs and bins, which can operate on the compressed .git. Simplified, because it won't need networking/remotes probably not even branches.
Involuntary reflex reply: ship an SQLite database as your data file?
Quick edit: hmm, I'm already ~1 hour late, the relevant thread starts at https://news.ycombinator.com/item?id=49327457
I mean, zipping files in an archive and presenting them as a file is an ancient tradition in video games. For example Warcraft 3 used the MoPaQ archive to store data in .w3x file.
And Starcraft 2 data is just bunch of XML files.
Except MoPaQ weren't zips IIRC, they had their own clever format here - at least the OG StarCraft / SCBW MoPaQs were, playing with that is what I learned binary data handling on :). The idea of zipping data files applies, of course (and many a game used a literal ZIP with custom extension).
But there's one material difference between StarCraft/Warcraft and Gimp: in Blizzard games, those were "zips" of heavy data files, notably read only data blobs. The game would read them, unpack in memory, and serve appropriately. Most of that data was key-value, text resources, or flat assets - images, sfx. With Gimp, we're talking highly structured data that's continuously being mutated. Very much not the best representation for that, even if you're just persisting it. They're only getting away with this because of SSDs - on spinning rust, you'd feel this.
(Also worth noting that, at least in StarCraft/SCBW, most of the files inside were custom, well-optimized binary formats. This predated the XML insanity of encoding data with 90%+ markup overhead.)
Cool, I didnât know that! But makes a lot of sense.
From https://github.com/zepouet/Xee-xCode-4.5/blob/master/XeePhot...:
Non-destructive filter layers caught my eye, and has been something I've missed since moving off Windows/Photoshop to Linux. Looking around it seems like they introduced this in V3, which is great to see.
Haven't those existed in Krita forever?
That is probably the V3 feature I'd notice most in daily use. Non-destructive editing makes experimentation much less costly; without it, every âmaybe this looks betterâ becomes another layer or file copy.
I just installed Ubuntu 26.04 and it's gimp starts for 14 seconds.
After the first run (where it has to evaluate plugins etc) it starts in under 4s on 26.04 on my Lenovo P53 (laptop from 2019). Which is admittedly not exactly snappy, but it's OK IMO.
Is the Ubuntu version of GIMP distributed as a snap package? I've had horrible performance with snap apps.
As usual, whenever GIMP is involved, all we get are negative, often unfounded comments about an excellent piece of free software that is massively used and developed with very limited resources, doing its job really well.
Thereâs something so pleasant about having GIMP around, efficient and so far removed from the disgusting greed that drives so many of the projects featured here.
Iâm going to take the bait:
I know a lot of people don't like that but sometimes I feel that FOSS projects are intentionally sabotaging themselves by ignoring industry standard options/conventions and instead they are following open source ideas just to be different. GIMP is the perfect example of that and generally speaking UI/UX is the main symptom.
Blender was able to move forward by not listening to the FOSS crowd but to the industry. And see where are they now compared to GIMP.
important here to remember that Blender was created within the industry as a commercial tool. When open sourced the leader of the project remained and knew quite well what separated a good creative tool from a bad one. It was always situated in a position where the core users were either hobbyists or professionals.
Gimp was never in such a situation.
Culture is important.
> Culture is important
Which brings us back to why so many people dislike Gimp, and/or see it as a posterchild example of bad FOSS alternatives.
I agree, and Culture IS important. And I think the culture around many Open Source "Alternatives" is harming themselves and the overall FOSS community. From Mastodon via Gimp to Nextcloud.
Even the name is self sabotage.
It's a clever name. What's your beef with it?
So GIMP has a larger user base than Blender, what is your point ?
I don't know what it has to do with anything - GIMP has been around for a while and has been the de facto FOSS alternative for photoshop for so long. That doesn't make that several of its UX and UI decisions are at least questionable nor make that comment you're replying any less true.
Not to mention the fact that if you ever mention in any way that GIMP's UX/UI could be better to anyone of its veteran devs they would turn weirdly ultra defensive and take everything personal.
Blender is something routinely recommend by normies. Gimp is not.
Blender is a very popular, maybe the most popular, for the tasks its used for. Gimp is not.
Market share might be more relevant when we're comparing products with different market sizes.
I love that GIMP exists but... I have to say, it never got rid of the "backend developer doing frontend" feeling, and I've been aware of Gimp for 20 years now (did not know how to...ehem, run photoshop in my teens)
Do you have your special dark mode glasses on?
Because I fail to see all the comments here as negative and unfounded. (and my guess why there is often negativity towards GIMP, is because it was too often advertised as a adequate Photoshop replacement, which it is not, so people got disappointed with it)
⌠and the sizes of their updates are usually impressive! Seems to be a big project that is managed well to keep a good pace and keep the community in the loop. (Although I donât know much about their inner workings.)
It's a great piece of software. Best feature - not having your colours retrospectively removed from your project [1].
[1] https://www.reddit.com/r/graphic_design/comments/rdtodb/adob...
Yes, it is very pleasant to have it around. Especially when you switch to something else.
Furthermore, it's free software. If people have a problem with it, they're free to show up and contribute, or fork if the community is really opposed to their ideas (they probably are for good reason, though).
I can guarantee that anyone turning up and contributing or forking this project will not lead to the outcome of a improved piece of software.
It will lead to someone with the insight on how to make actual material improvements frustrated and angry that they don't have the technical skill (or time) to grapple with a complex codebase, and the people with the technical skill working on the codebase dismiss people with actual knowledge in different domains.
"Patches welcome" is not any kind of welcome. It's basically a euphemism for "fuck off, I don't want to have a conversation to make something better, I just want to hack on Feature X".
Zipped XML. Welcome to 1999 designs
Let's be honest, the real 1999 design would have been a custom binary format that happens to use the endian of the system it was developed on, and leaks bits and pieces of unflushed memory buffers whenever it writes to disk.
No that would be an early 1990s file format ;)
1999 is exactly right for the start of the XML hype, everything had to be XML, it would single handedly solve the software crisis (after OOP failed to do that) because everything would be able to talk to everything!
Indeed, early 00s was still the SOAP XML era if I remember right, WSD, SOA, ...
SOAP XML is so uselessly convoluted.
The whole Italian e-invoicing system is based on SOAP XML, and it's atrocious. They approved the specs in 2013, so it was already dated when it came out.
Jar
What would you consider good modern design?
SQLar[1], see [2] for some reasoning around why a database is preferred over zipped XML. Though, I'd be fine with a DBM-style database too as we only need the key-value part of it.
[1] https://sqlite.org/sqlar/doc/trunk/README.md
[2] https://www.sqlite.org/affcase1.html
The problem with using database blobs for load/save is that you usually need a full database client in the application. SQlite advertises that use case, but it is complete overkill. You never need to run any sort of complex SQL query on an image file format for instance. Using XML+ZIP in this day and age is also a strange decision, but at least that way the data is inspectable with unzip, a text editor and an image viewer (assuming they use a standard image format to store the raw pixel data).
Sqlite is probably overkill, you will probably never have actual relational data in an image format, But what it does bring to the table is a built in b-tree based storage, that is, you don't need to load the entire file into memory to edit it, in a prior age we would use Berkeley db for this. Sqlite in this role(a file format) is probably best thought of as a better superset of the berkleydb style key value store, more than one table per file and additional columns/indexes to keep metadata in.
Nothing wrong with XML, it is well understood, and the tooling is pretty good. But partial loads/edits is one thing it can not do.
Think of Lightroom or automation over files. Many semi professionals from wedding photographers to designers want some form of batch automation and organization system over their files.
Several megabytes/gigabytes assets and you want to extract metadata, a preview, running as a batch some filter/compression/, conversion to CMYK, text injection ... fast partial read/write access would be nice. Right now, most reads are performed through indexes because those files are slow to read.
If we take 10k sqlite files and want to retrieve a row, we would be around 3s on SSD, maintaining preemptive indexes become less important for a lot of use cases.
Change management and versioning also becomes quite efficient - sqlite can be configured to not offset bytes, so CVS like Epic Lore can efficiently delta the files and store minimal delta, or the file format itself can keep its edit history. Oh and it's 3x-10x less bytes without compressing the whole thing, so pages are stable through time.
About needing SQLite client, it's real but it's roughly the same size as an XML parser.
> About needing SQLite client, it's real but it's roughly the same size as an XML parser.
what I like about it being XML is I can just open it with any text tool and inspect it. It's human readable so I can edit and debug it manually, no need to have a parser or an extra application just to see what's in my file
> Using XML+ZIP in this day and age is also a strange decision
I agree with you that SQlite is overkill but honestly curious to know why you think xml+zip is strange? what would you use instead?
> You never need to run any sort of complex SQL query on an image file format for instance.
Sure you will. Plenty of features that don't exist, or are implemented badly, because you can't easily do it.
Quick mental translation table: if you think "iterate over every ..." or a `for` loop, that's your SELECT query. If you think about `if` conditions, that's the parts that go after FROM clause.
In order to have any advantage from this, you would have the added complexity of splitting your file format into tables that can be queried in a useful manner. However, for an image file format, you most likely need to hold the entire definition in memory at all times anyway. Assuming thatâs the case, doesnât XPath get you there most of the way (assuming XML), with _way_ less complexity?
Image data is just binary blobs. You aren't splitting that into channel columns or anything. But an image file for an editor like Gimp isn't one image blob. It's dozens or hundreds of them - one or more per layer - along with tons of associated metadata at every level.
All that tends to fit sensible schemas and managing it is what SQLite shines at.
I donât see how this addresses my point that zipped XML gives you the same thing, but simpler. I understand that a GIMP file is many images, so that makes a zip feel like a great fit to me. The only advantage I see for using a full-blown DB is ensuring consistency with references, which admittedly is a plus. But beyond that, what do you gain?
SQLite is fast, but it won't be faster than a hot loop in C. Having the loop construct dictated by the file format seems bad. For images it seems more reasonable to have them in-memory, except for huge image edge cases.
Images are the red herring. Pixel data is best read in hot loops in C, but that would be stored as blobs in SQLite anyway.
It's all the metadata around the image that's interesting. Images have layers, dozens or hundreds of them (this literally scales with how good your software is at handling those - the faster, and more powerful layer UX is, the more they get used). Some are pixel layers, other are effect layers, text layers, vector layers. Layers have metadata - names, sizes, colors, tags, types, special effects, and a bunch of other stuff I don't know because I don't use that 80% of features of GIMP/Photoshop/Affinity.
Then you have document level metadata, UI-specific metadata, etc. Also undo history. A lot of that is relevant to the work on images themselves, and changes in realtime, and can get even more useful if querying it wasn't such a PITA.
That - not the binary pixel blobs - is the selling case of using SQLite as application data format.
the SQLite archive format (it's probably worth linking to the main documentation[1], instead of the very old experimental repository) may not really be a good fit for something like GIMP's native file format. (To be clear, "SQLite archives" are not special compared to any other database: it's just a well-defined schema for an sqlar table, which the sqlite3 command line tool is able to create, update, and extract using syntax like the tar command.)
That being said, SQLite would still be a good choice, especially as it's a format that's really intended to be modified in-place, and has good data integrity features (eg: keep WAL enabled so that mid-save crashes/shutdowns don't corrupt your file), neither of which are provided by Zip. You could even just run zlib on data (be it XML or what have you) if optimizing the on-disk size of the file is desirable.
[1] https://sqlite.org/cli.html#sqlite_archive_support
Isn't the implementation the spec for SQLite?
Not really a great option for an image format, where we therefore can't have multiple implementations. Unless I misremembered.
SQLite file format spec: <https://sqlite.org/fileformat.html>
Thank you for the prompt clarification!
Compressed JSON with the binary content encoded in base64 strings, obviously.
So you compress a format that inflates binaries with 30%?
That not only ends up larger than "just the binary", it also eats a lot of extra CPU to (de)compress AND encode-decode.
This idea is novel, but wasteful.
(edit: I thought you were serious, so I answered serious. You were not ;)
Yes, this is not too rare to see base64 images in JSON but I won't recommend that.
You gain back most of the base64 overhead when you compress it though. It's slower but probably often worth it if the alternative is few more async HTTP queries that you would only fetch once.
Why would zipped JSON be fundamentally superior to zipped XML?
To answer seriously, my parent comment is a joke, JSON is a simpler format that maps better to most programming languages internal memory representations. Developers tend to prefer JSONâs simplicity over XML.
> most programming languages internal memory representations
Often heard wrt JSON but incorrect. It maps to the primitive types in JavaScript. But almost all programming languages treat floats and integers different, make distinction between char and strings and many have some form of date/time. JSON has neither.
In that direction, XML is much closer since every node is a triple (name, value, attributes) so can have type info, json is a tuple. And Protobuf, while not popular, gets this completely right.
I think it's too risky to treat numbers in JSON as something else than IEEE754 64bits floats. But yes, JSON is small and doesn't do datetimes, char, comments, and a million other things XML does.
But you don't need to think much about memory representation when you parse a JSON, and the developer experience is a lot more pleasing than browsing a XML tree. That what used to matter.
Why XML bad?
Fundamentally, it's not.
The problem was that people hyped it up as the solution for every problem and all the world's ills, so it wound up being used where it had no business being used (and therefore badly).
XML was a hammer used to bang in a lot of things that weren't remotely nail-shaped, and accordingly, a certain percentage of traumatised people despise it and react to any mention of it with fear and loathing.
It's kind of neat when you have an application for it that really leans into its strengths.
Welcome to 2026 unfounded hot takes.
Or less snarky: what's your gripe with zipped XML? It compresses reasonably well, has a useful structure, and has decades of mature tooling around it.
Thanks! I had the exact same question for various of these posts here. I know these may be different groups of people, but I always see people advocating for simplicity, and zipped-XML is as simple as it gets, needs barely any extra dependencies (none in GIMP I assume), and is proven to work well (Word etc).
I also donât understand why SQLite would be preferable here, considering you will likely also store large binary files alongside your document definition.. What does a db engine give me here?
The obvious alternative is SQLite, and it has many advantages. If you want to do a "zipped list of files", SQLite does that just fine (that's what SQLar is), but it can do so much richer data. Even if you don't want that, it still offers resiliency that "zipped XML" can't match: if your software or computer crashes in the middle of saving your file, it'll almost certainly corrupt it. With SQLite, not an issue: all transactions are atomic, they either happen entirely or not at all.
I don't know what "mature tooling" you're talking about for zipped XML, but I guarantee you it's not going to be better (or more mature) than SQLite and its ecosystem.
> For instance, weâre quite proud that a XCF file made by a small company for their logo in 1998 still renders the same way in the latest version of GIMP
How do they pronounce âXCFâ such that itâs âa XCF fileâ and not âan XCF fileâ? âXeceffâ?
A "ksceef"?
But yeah, in my mind, it's always been "ex see eff", so an XCF.
I find some word processors don't test for vowel sound, and only adhere to the actual vowel letter.
In my mind itâs similar to exif
The beginning of âXCFâ sounds similar to the beginning of âExitâ.
With âaâ vs âanâ, the pronunciation is more important than the spelling.
> With âaâ vs âanâ, the pronunciation is more important than the spelling.
I know, hence my question about the pronunciation. If I had thought the spelling was more important, the âXâ would have settled it so I wouldnât have asked.
You say "a exit"?
I thought every developer of this moved to the Glimpse fork
That effort didn't last long. I think this is the first I've heard about it since inception, the repo (assuming this is the right one, https://github.com/joshgiesbrecht/Glimpse, it was the only GIMP related thing that came up amongst a sea of unrelated projects with the same name) is hasn't seen a commit in 7 years and what appears to be the official site away from a forge (https://getglimpse.app/about/) is currently unresponsive.
Pretty sure woke gimp was long discontinued
https://itsfoss.com/news/glimpse-gimp-fork-archived/ Yep, it's dead.
I don't want to revel in the fork's demise for any reason besides relief that it didn't end up splitting GIMP's contributors and community in a way that would have harmed both projects.
> we could not find contributors willing to step up and help with non-code tasks like moderating communication channels
Gotta say though it feels ironic that they couldn't find enough people to be comment janitors considering the whole thing was based on wanting people to stop saying a particular word.
> As a result, we struggled to scale the project to match increasing demand.
âGlimpse didn't fail; it was actually too popularâ?
That's the thing, they didn't take any GIMP contributors.
Everyone that was behind Glimpse was third party to the GIMP project.
This wasn't even a serious project but an example of malicious virtue signaling with a long-term plan for sort of hostile takeover. People involved just took the original code and replaced every GIMP occurrence with Glimpse, added new logo/icon and called job done. Then went to the news sites trying to raise awareness of the supposed name controversy hoping noise will discredit GIMP while they'll portrait themselves as the saviors. Because who'd want to contribute to a software that has such bad reputation.
It's been over 24 years for me since I've used GIMP for the first time and the only problem that I had was always with GUI ergonomics. You had to understand everything anew after being more accustomed to proprietary software pieces. My friend never adapted to anything else but Photoshop - even Krita is beyond her abilities.
Nearly every discussion regarding GIMP on hn will include thread about the name 'problem' and this is getting tiresome. The name won't change and those who feel offended should focus on problems whose solution is genuinely productive.
> This wasn't even a serious project but an example of malicious virtue signaling with a long-term plan for sort of hostile takeover. People involved just took the original code and replaced every GIMP occurrence with Glimpse
I recall one of the reasons given on the GIMP Gitlab issue to change the name was "it will encourage more contributors" that apparently don't contribute because of the project name. Glimpse certainly had a lot of contributors... not.
I can't think of a single project that changed a name to satisfy these people ever received more contributors as a result.
I feel like it would have though if Glimpse had managed to become the default image editor on at least one major distro, just by virtue of people stumbling in to contributing some fix or addition to âthe thing that came with my OSâ without necessarily being aware of the history.
Like the FFmpeg/libav fork that eventually got back together. Or Compiz/Beryl, or Emacs/XEmacs, or GCC/EGCS, or whatever :)
I'm surprised it got that epithet, I'm used to "upset by weird sex stuff" as being a US-right position, and "woke" being a term that's used by US-right to denigrate US-left.
Then again, I'm also old enough to have seen it shift significantly in meaning at least once, and I think I'm seeing it shift meaning again.
Before the weird sex stuff, "gimp" was an insulting term for a crippled person. The fact that it's so long out of common use for that purpose that a lot of folks don't realize that is perhaps an argument for not taking it too seriously. On the other hand, disabled folks are certainly among the most oppressed and abused and in ways that aren't well-understood by most folks, so a decent person should be pretty careful about using language that could be demeaning. I dunno. It feels like an archaic term that ought not have any power today, but what do I know?
> Before the weird sex stuff, "gimp" was an insulting term for a crippled person. The fact that it's so long out of common use for that purpose that a lot of folks don't realize that is perhaps an argument for not taking it too seriously
It's a US specific slur when used in this context, not in other English speaking countries (let alone non-English countries) A lot of GIMP developers are European yet the Glimpse project tried to force American cultural/linguistic rules on a non-American project.
Words mean different things in different regions and languages, just because it's offensive in your language does not mean it's offensive in others.
They didn't try to force anybody to do anything. They forked a Free Software project as allowed by the license. You seem awfully sensitive.
I remember the (now deleted) Gitlab issue on the GIMP project that called on for the name to change, it certainly wasn't friendly.
What do you believe the word "force" means?
It's a decorative strip of fabric used to trim upholstery and hide tacks to me.
In the UK, itâs the sex one and would be used as a general âidiotâ word but that seemed to have mostly faded away. Itâs not a word Iâve seen used in that context for many years.
Not refuting anything here, just adding some context from over here. Whichever way you slice it, itâs always been an awful name.
Yeah, it's always felt like an "edgy" name a teenager or quite young man would come up with. Which makes sense, the original GIMP authors were college-aged boys when they created it.
I'd like it if they changed the name. We're (the Open Source community) not teenagers or annoying college kids anymore, by and large.
I like it that the scruffy teenager hacker mentality is preserved in the name. It was also a bit of self deprecating humour at the time, because using Gimp instead of Photoshop did make you feel crippled a bit.
I hope they never give in to the corporate-lawyer induced bland-washing .
I'm not a corporate lawyer.
I'm just a Free Software user and developer and I think it's nicer when I can recommend something to someone without having to think about whether I might be saying something rude or hurtful. I assume there was a stink about the name because it bothers some disabled folks. It's not my place to tell them not to be bothered, I'd rather just not do the shitty thing that bothers them.
It seems cringey and childish to insist on doing a thing that makes a bunch of people feel unwelcome based on something about themselves they can't change. And, for what? So you can feel like a scruffy teenaged hacker?
I like my Free Software community to welcome people of all sorts.
Having a "stink" is right. Even without much thought, it's off-putting, does not sound professional and really icky. When you think a bit harder, it's just kinda awful. I do actually suspect the name does have some measurable impact on adoption. Most people don't want to say "I gave up photoshop, I use gimp." outside of hardcore linux circles and since then, it has gone from the only open source gig in town to just one of many alternatives.
The issue is that there are a bunch of people like this[0] who get incredibly upset and politicize any attempts to be "the adult in the room" and ask for renaming of unsavory names.
The funniest of these is when Europeans talk about how they are being "forced" to comply with American cultural norms and you go through their account and they are so deeply steeped in American culture due to their participation in the anglophone internet spaces which are dominated by them. People in Europe will argue with you that you are importing woke culture if you suggest that they shouldn't say the N word, but are seemingly completely oblivious to the fact that the reason they find the word exciting to say and they say it in English is an import of American culture
[0]. https://news.ycombinator.com/item?id=49327771
Personally I just prefer to avoid the debate and call it âGNU IMPâ v(._. )v
Maybe this is the way forward? :)
Zipped XML sounds like a bad idea. It's slow and bad. I say XCF forever.
SQLite would have been a lot better choice, in my opinion.
Pardon my ignorance about formats, but between XML & JSON, what would have made them choose XML? As I understand there is lot more tooling, standards & existing software examples around JSON for project & records management (e.g. VSCode's records as settings.json for example). Wasn't XML spearheaded by Microsoft but mostly used by Microsoft today?
json's only advantage is it's easier to write by hand, but that's not really a consideration here. XML has schema support and much more tooling available.
> As I understand there is lot more tooling, standards & existing software examples around JSON for project & records management
I don't understand why that is relevant; as long as there is a minimum level of tooling, libraries and support for their choice, what benefit would JSON bring over XML? I don't see a clear reason for one over the other.
Honestly, I'd have the same question if they chose JSON and someone asked why did they choose JSON over XML - Why wouldn't they?
JSON made me not hate XML. YAML made me not hate JSON.
> It's slow and bad.
Seems to have been working great for MS Office.
âGreatâ.
No offence to anyone, but I would not consider the performance of MS office to be great.
I guess it's comparative, but then I compare to its previous editions which used a sliver of the resources to accomplish 95% of what modern o365 does.
> previous editions... used a sliver of the resources
Well of course, but given that the previously employed technique was blitting, fliedumping memory areas, you can't be more efficient than that. Using XML is for transparency (readability).
(And, note, in context, I regard the ms office file format as lousy. The OpenOffice/LibreOffice format is good.)
I don't think your parent comment was talking about the resources involved in saving a file, but rather the resources involved in running the software.
Thank you, probably so, but in that case I cannot see how said comment is consistent in the branch ("about file formats") - I do not get how it would follow.
Its very widely used. Perfomrance might not be great, but adoption is.
Office documents since the 2007 have used a zipped XML approach. Just take an .docx and open it in 7zip.
EDIT: Narrowed the date.
Iâm aware. IIRC this was a response to Microsoft being forced to use some âopenâ protocol or something.