> Well, because it's true: many of the repositories are named after "Wacom". It's a historical legacy on GNU/Linux. It's also a decade-long debate that these repos should be renamed differently.
If the project being named after Wacom is actively causing other companies to not contribute because they believe it’s a Wacom lead project and they’d be helping a competitor, I don’t understand why this is even a debate vs. just changing the name to something vendor neutral.
And it's been a decade long argument? Sounds like someone is just emotionally attached to something not changing. Those are the hardest problems to solve.
The technical people managing the repos might just be opposed to name changing in general (seeing how a boatload of links, references, documentation would require updating, some of which you don't even control), and meanwhile those people might feel the "misbranding" drawbacks much less (if at all).
I would categorize all those as emotional reasons not to change, not logical reasons.
"It's hard!" So?
"It's complicated" So?
"Some of it other people control." This will always be the case, you can't let the perfect be the enemy of the good enough.
If the status quo means a worse project, then you're not changing because you don't WANT to, not because it's a good idea. And that's an emotional, not logical ,decision.
>> The technical people managing the repos might just be opposed to name changing in general (seeing how a boatload of links, references, documentation would require updating, some of which you don't even control), and meanwhile those people might feel the "misbranding" drawbacks much less (if at all).
> I would categorize all those as emotional reasons not to change, not logical reasons.
Ignoring for a moment the annoying software engineer tropes of "emotional=bad, logical=good" labeling and its unawareness of the fact that logic and emotions are hopelessly enmeshed; deciding what work to prioritize how you spend your limited time does not seem particularly "emotional."
So there's no point in wasting time on this, if perceived problems are low or nonexistent. Current maintainers probably look at it from a technical pov "it's just a name, who cares"
My point is that from a developers PoV, renaming is not an evident net-gain at all-- might be seen as pointless branding busywork that leeches ressources from "actual" problems.
That is not "being emotional", it's just different priorities.
I think it's the exact opposite of what you're saying. The maintainers sound like they're only considering the technical cost (and judging it not worth it) instead of factoring in the political consequences of keeping the same naming. I actually really respect those who value the technical over the political, but in a large-scale, public-facing project, some politics must be played.
It seems to me like you're viewing the playing of politics as a no-brainer, which is a very different mindset from a Linux contributor. I don't think people get into kernel maintenance to play politics.
The ones playing political games dressing them up as technical ones are the worst:
“My approach is technically correct and I won’t change it even though it causes issues down the line”. I’ve seen this a lot in the Gnome/Wayland world.
> I don't think people get into kernel maintenance to play politics.
I’m not a kernel developer and the projects I’ve worked on haven’t even been that big, but even there it was necessary to cater to multiple stakeholders and consider multiple viewpoints. I’d go as far as saying that software development in general gets pretty political pretty quickly, as soon as you depend on somebody else’s work or somebody else depends on yours. Every decision will impact somebody and different options will do so differently - these are political considerations.
I can’t imagine this being less of an issue in the kernel.
No, I'm not saying the politics is a no brainer. I'm saying there is a logical barrier to the project succeeding, and it is the name. Other people refuse to work with it using the current name, people who would make it a much more useful product. Deciding it's not a TECHNICAL problem is an emotional decision, because you're not reframing it from what it is, a barrier to success, to something it's not, a non-issue. They're deciding not to engage with the hard problem.
So it will take valuable developer time that might be better utilized to work on something else. And even if they do rename it, there isn't any guarantee that the other vendors would then agree to collaborate.
That’s exactly it. So many engineers aspire to build generalized, flexible components that get tons of adoption by being easy to use. The problem is that they have have just volunteered to be disconnected from their users. And this myopic refusal to rename Libwacom is a perfect example.
It’s probably down to one underappreciated Linux dev somewhere who is tired of the debate and spends their time fixing actual bugs.
It seems like it would be simple to just create a fork and archive the old repo. Add a note to the old repo, update a couple of the most important docs and links, and then worry about the rest later. It can be low hanging fruit for new contributors.
Yes, I know, but that all just underscores what I said about it being emotional. Logically it's not only Wacom but for any tablet. It would do better with a new name as other competitors would help. But the emotional resistance to changing the name keeps those logical improvements form happening.
True nerds name things properly in the first place. The liberal use of -wacom throughout project names and repositories is a consequence of the Wacom itch being scratched - and then that scratch becoming the base upon which Wacoms' competitors can participate. A true nerd would've skipped including the brand in a directory name, in the first place .. I bet these drivers started off being written by graphics designers, not nerds.
So, um, the phrase "legally forced" really does not go with "happened easily".
Ignoring what "legally" forced entails, and just focusing on the mechanics of renaming stuff: Even if your code base can be updated with a simple "s/old/new/" regex (and, IME, this never, ever works as well as you thought it would, and always creates a long tail of manual grepping and editing), you still have to fix the docs, deal with breaking API changes, support multiple versions, provide upgrade paths, deal with confused users, etc. etc. etc.
And, um, confusingly, the examples you cite are actually even more complicated and work-intensive than what is being talked about in this article, because they also require URL / domain name updates, legal document changes, regulatory filings, etc. etc.
TLDR: the contention that "name changes happen easily" is not an accurate description of the situations you are citing.
You didn't hear the foaming at the mouth shouting to rename master recordings, master documents, or dub over The Master from Dr. Who.
Considering how much effort we had to out into fixing pipelines because of hardcoded scripts, and the lack of good reason to do it its no surprise that it was scoffed at. White keyboard warriors needed to make a change, but couldn't do anything meaningful as it would require actually doing something.
Yep. I was an intern at Disney Feature Animation when GIMP first came out. It was really exciting, an alternative to Photoshop (which used to run on linux!) and our in-house painting tools. I pushed for artists to use it, but was told by management to stop mentioning it as "Disney could never use a tool called GIMP". Also that reaction from several artists (who were already tech-savvy, linux using folks in the exact target audience) so it wasn't just "corporate". TBH I think a lot of programmers do this intentionally to protect themselves from their little project ever becoming too mainstream.
Just last night was was thinking about KeePass. Sure, it wounds like Key Pass, or Keep Pass, but it also sounds like Keep Ass, which while cheeky, is less than perfectly commercially enticing. It feels like ExpertsExchange...
In non-English speaking countries gimp is a short word that is so seldom used that nobody knows what it means. I used GIMP for a very long time before running into a story about the meaning of the English world. It was only GNU Image Manipulation Program to me.
It still is a contender for image editing programs, for limited photo retouch, for very limited drawing (draw a rectangle outline without googling?) I use LibreOffice Draw for that.
It did stop it from being used in a multiple markets though. Fine is some places, not in others is not good branding, especially when one of the places its not fine in is the biggest and most influential market.
Nobody in my middle and high school had any idea "gimp" had an English meaning. I assume if anyone knew, we kids would at least occasionally joke about it (we used gimp for various projects).
It was long after university after I learned that it's also an English word.
The unfortunate truth is that the English speaking market matters for that kind of product and that name is a barrier. It just doesn’t matter that your day to day language or life doesn’t encounter it.
I've been up and down this debate a million times, a lot of it here, suffice it to say -- the fact that you and others don't recognize this does not at all detract from my point.
To summarize, it's not e.g. about me being personally offended -- it's about people like me (a long time ago) wanting to show people this great software and other reasonable people seeing the name, understanding the meaning, and reasonably thinking "If this software were actually good, why does it have such a ridiculous and often offensive name?"
An unserious name -- literally chosen to be an edgy joke -- projects "unserious software."
I'm surprised they didn't just write it out as GNU IMP in the website, documentation, and about boxes. They could just leave the code alone and save themselves the trouble.
Its most likely a debate because making such a major refactoring effort is actually a heavy work load, there are lots of bits and pieces to tie together and cut out and so on, and the folks capable of shepherding this change through all the parties out into the distro's are already underpaid/under-appreciated too much as it is ..
Hopefully, this situation will get some traction with a bit of noise about it, and the distros can actually put some effort into handling the rename - or maybe a hero will arise in the midst of all the fuss, who just does the full renaming properly, tested, and so on - in a fashion that it simply can't be ignored.
It's definitely an interesting thing to see this happening, anyway. Open Source has many, many troublesome facets when it comes to fairness and equity, but it also has a lot of bright, shining moments. The fact that the technical ability to build these drivers is already a given, and really the thing holding everything back is just the corporate brand obsession, is kind of hilarious though, also.
Duh, you own your competitor by pushing your tech into their brand-space, dummies. This is an opportunity for brands-not-Wacom to eat Wacoms lunch in a delightfully technologically significant way - but, alas, the brand cult reared its maw, instead...
Devil's advocate: why should the project have to rename because some companies want them to? That just shifts the window slightly closer to corporate control, something that millions of people worldwide bemoan.
i was in the market for a drawing tablet. I looked at huion, wanted it, but realized the driver situation was not on par with wacom. I now have a wacom device.
Pretty sure the reason is, that anybody who could actually do the changes thinks works for me, the alternative is a lot of work for little technical gain.
And besides once you start your tablet for Linux Projekt you have to touch everything, so that is a nice opportunity to finally refactor the wacom_debug_2 mess and pretty soon you're drowning in yak shavings.
> Well, because it's true: many of the repositories are named after "Wacom". It's a historical legacy on GNU/Linux. It's also a decade-long debate that these repos should be renamed differently.
Okay... let's rename them then? I know it's silly, but, well, we've went through the whole pointless `master` -> `main` branch rename in so many projects which was much more disruptive -- at least this one could serve a purpose?
The difference I think is that it is reasonable for a company to not want to bother working in a project named after their competitor, when "master" has always had multiple meanings from "formal title for a young boy" to "really experienced tradesperson" to "authoritative record" and it is somewhat unreasonable to associate "authoritative record" with "slave master", especially since git branches were rarely named "slave". Wacom is a brand that hasn't been Xerox'ed or Kleenex'd or Band-aided. I don't call every drawing tablet a Wacom.
When I started using a graphics tablet, long ago, I was confused about why all this stuff was labelled Wacom, and whether it was applicable to me or not, when using a device of another brand. Some parts of it seemed to be, and other parts didn’t? It was very confusing, and a genuine confusion that made me uncertain even in purchasing. (It would be less confusing now because user-facing parts don’t touch the “Wacom” name as much any more.)
Whereas the “master” thing was transparent linguistic nonsense and a strictly-US cultural thing that a few people foisted on the rest of the world because they decided to get offended on behalf of a hypothetical group.
We had to refactor all our internal and external documentation from Master -> leader and slave -> subordinate. So you get things like “… in subordinate mode”.
Thankfully the actual code remained the same (because only engineers look at it).
I've seen "slave nodes" renamed to "children nodes". Because a node that exists solely to support another, more important node, has to carry out the orders it receives from that node, must not do anything on its own, and will be terminated and wiped if it diverges from the vision the main node has — yes, it's a child node alright. You see, that's how children are generally treated in our enlightened society, so the new name is now properly evocative, and has no unfortunate implications.
I'm entering troubled waters but hey... The master to main issue is an accident of the history of the USA, still unresolved in its consequences, when most of the world was not practicing slavery anymore. The typical reaction outside the USA is rolling eyes and hope that all the ethnic groups inside the USA will finally get along. If the IT and economic powerhouse of the world were India instead of the USA and Indians would have picked master instead of main despite the British colonial period, this would be a non-issue: the USA could use a different convention (like for units of measurement) and the rest of the world wouldn't notice.
BTW, every country had its expansionist and genocidal and slavery moments (I'm from Italy, think about the Roman expansion inside Italy, then the empire or our colonial wars 100 years ago.) The USA is one of the most recent examples. It takes time and I understand that master vs main is important inside the country.
The issue of Wacom branding is different because it's a business dynamic and businesses don't want to work for competitors no matter the country, no matter the history. They can work together or an equal footing. So rename to libtablet or whatever.
It seems most likely to me that this particular sensitivity to any sort of social controversy and the status of the US as the sort of… de-facto default place of doing international business for a long time, are probably linked. The US corporate culture’s default stance is probably a learned reflex. Better to look a little over-sensitive, than to scuttle a deal by blundering into somebody’s cultural trigger.
It seems to be very popular in the US to take offence on behalf of others. For example: one hears of US people getting upset about “cultural appropriation” on behalf of others, when said others are actually actively happy about their culture being shown and appreciated. You can definitely take things too far in either direction.
There's a concept called "allyship", part of which means listening to marginalized people expressing negative reactions to certain popular demeaning acts and acting on their behalf to stop those acts.
In recent memory, you see this in response to last decade's trend of white people wearing Native American headdresses (particular to certain remaining groups of indigenous people in North America) at fashion shows and public events. This was practically the definition of cultural appropriation; in the cultures which display headdresses, one must earn the right to do so, and here you had the descendants of those who committed actual genocide wearing these symbols without even an attempt to understand their significance.
This is in a country that not only practiced genocide, it stole the children of native peoples, ostensibly to educate them to European norms, to cut them off from their hereditary culture; including their language and clothing. It's also a country that continues to ignore its own treaties with indigenous nations and erase their history through "termination" (the policy of un-recognizing individual tribes to eliminate their status).
So maybe it's popular here because this country is particularly terrible at appropriating culture. There's a ton of nuance you might miss if you don't live here and talk to people.
> Neither change has any technical reason. The only reason why either name change was desired is because some contributors were upset by the names.
Indeed, neither has any technical reason.
I suppose you're right that both changes have a purpose -- one could feasibly convince a company to contribute Linux drivers (a net win for everyone), and the other is a constant annoyance which wastes everyone's time (is this project using `main`, or `master` -- you never know, so have fun getting it wrong all the time) just to allow certain groups of people/corporations to virtue signal**.
** -- If "master" is such a naughty word then where are all of the people getting offended by e.g. "Mastercard", "Ticketmaster", "Master Lock", "MasterBrand", and many other company/product names, and why those names aren't getting changed? Why there isn't any outrage about them? My point here is not to engage in whataboutism, but just to point out that the word isn't actually offensive when used in a non-offensive manner, and virtually no one is actually genuinely upset about it.
Feel free to reply to that email and let them know that your readers just discovered that instead of considering Wacom alternatives, they now believe that Wacom is the only brand they can use on Linux. It seems like the only valid response to that is to give money to the people who make their hardware usable on my software.
It’s not like they collaborate on closed-source drivers either. If you have two different brands of tablets in your life then you get to deal with weird bugs from their drivers fighting. And if you’re on Windows they may fight with MS’ attempt at default drivers, too.
Good point. You don't even need to rename the upstream project. Just create a new project, and get the code there. Since it's open source, it will eventually make its way into the upstream libwacom as well.
All they have to do is publish a technical PDF with descriptors and stuff. That's it. Why not ask for that? They should see the benefit of their product "just working" with FOSS systems.
I updated from a screenless Wacom to an XP-Pen screen tablet. The tablet hardware itself is good (but also I moved up several product categories) for less money than the Wacom, but the experience getting it to work on Linux was reminiscent of trying to get wifi to work 15 years ago. I got there in the end, but it was not smooth.
I use an Xppen 24" Pro display tablet. I enjoy using it but my Linux mint machine simply won't boot with it plugged in. I haven't figured out a workaround beyond physically disconnecting both cables every time. And when I boot up and reconnect, my machine never remembers the screen mapping, so there's enough friction there for me to avoid plugging it in for days if not weeks at a time.
To me, this response shows that there is a great opportunity to convince them with things that will bring them good publicity.
Things like "drivers" with their name, etc...
One thing I miss from Windows is the tablet driver GUI. "cinnamon-settings wacom" doesn't let me map buttons to keys (important for software like FireAlpaca, which pans with the space key instead of supporting the middle mouse button like everybody else in the planet), and it also doesn't let me remap the tablet area to arbitrary screen coordinates. These are things I could do on Windows that I can't do through the GUI.
I wrote a Python script to do it using xsetwacom, but I don't know if it would work for anybody else. I don't know if xsetwacom is only for wacom tablets, or if xsetwacom is only for X11 (I'm not on Wayland yet).
Maybe people don't realize that this is very much within the capabilities of modern AI nowadays?
At $dayjob we have encountered people reverse engineering our driver with Claude and creating GitHub repos with pretty useful vibecoded tools and documentation.
Yes, the raw binaries of the driver. Not leaked source code or anything like that.
For my part, I've been using Wacom tablets and styluses and digitizers since placing a same day order (2AM) w/ PC Warehouse using their 1-800 number, paying for rush shipping and getting a Wacom ArtZ later that same day.
I've suffered through a lot of non-Wacom EMR styluses in the past, and my preference is to buy the real thing, so I'm okay with the status quo, unless there has been a marked improvement --- that said, who wants multiple stylus technologies? A big improvement in my life was getting the same Wacom EMR support on _all_ of my devices, so I can:
- make a note in MyScript Notes on my Samsung Galaxy Note 10+
- add it into a to-do notebook on my Kindle Scribe Colorsoft
- open the note in Nebo.app on my Samsung Book 3 Pro 360 for reference/editing
- work on the project on my MacBook using a Wacom One display
(and yes, there are times when I have all four devices out)
I couldn't count how many Wacom EMR styluses are scattered around my house or in various laptop bags....
> Well, because it's true: many of the repositories are named after "Wacom". It's a historical legacy on GNU/Linux. It's also a decade-long debate that these repos should be renamed differently.
If the project being named after Wacom is actively causing other companies to not contribute because they believe it’s a Wacom lead project and they’d be helping a competitor, I don’t understand why this is even a debate vs. just changing the name to something vendor neutral.
And it's been a decade long argument? Sounds like someone is just emotionally attached to something not changing. Those are the hardest problems to solve.
Not necessarily.
The technical people managing the repos might just be opposed to name changing in general (seeing how a boatload of links, references, documentation would require updating, some of which you don't even control), and meanwhile those people might feel the "misbranding" drawbacks much less (if at all).
I would categorize all those as emotional reasons not to change, not logical reasons.
"It's hard!" So? "It's complicated" So? "Some of it other people control." This will always be the case, you can't let the perfect be the enemy of the good enough.
If the status quo means a worse project, then you're not changing because you don't WANT to, not because it's a good idea. And that's an emotional, not logical ,decision.
>> The technical people managing the repos might just be opposed to name changing in general (seeing how a boatload of links, references, documentation would require updating, some of which you don't even control), and meanwhile those people might feel the "misbranding" drawbacks much less (if at all).
> I would categorize all those as emotional reasons not to change, not logical reasons.
Ignoring for a moment the annoying software engineer tropes of "emotional=bad, logical=good" labeling and its unawareness of the fact that logic and emotions are hopelessly enmeshed; deciding what work to prioritize how you spend your limited time does not seem particularly "emotional."
>"It's hard!" So? "It's complicated" So?
So there's no point in wasting time on this, if perceived problems are low or nonexistent. Current maintainers probably look at it from a technical pov "it's just a name, who cares"
> it's just a name, who cares
This cannot be, naming things is one of the two canonical hard problems.
You've forgotten the 3rd canonical hard problem: off by one errors.
Different people have different perspectives.
My point is that from a developers PoV, renaming is not an evident net-gain at all-- might be seen as pointless branding busywork that leeches ressources from "actual" problems.
That is not "being emotional", it's just different priorities.
I think it's the exact opposite of what you're saying. The maintainers sound like they're only considering the technical cost (and judging it not worth it) instead of factoring in the political consequences of keeping the same naming. I actually really respect those who value the technical over the political, but in a large-scale, public-facing project, some politics must be played.
It seems to me like you're viewing the playing of politics as a no-brainer, which is a very different mindset from a Linux contributor. I don't think people get into kernel maintenance to play politics.
The ones playing political games dressing them up as technical ones are the worst:
“My approach is technically correct and I won’t change it even though it causes issues down the line”. I’ve seen this a lot in the Gnome/Wayland world.
> I don't think people get into kernel maintenance to play politics.
I’m not a kernel developer and the projects I’ve worked on haven’t even been that big, but even there it was necessary to cater to multiple stakeholders and consider multiple viewpoints. I’d go as far as saying that software development in general gets pretty political pretty quickly, as soon as you depend on somebody else’s work or somebody else depends on yours. Every decision will impact somebody and different options will do so differently - these are political considerations.
I can’t imagine this being less of an issue in the kernel.
No, I'm not saying the politics is a no brainer. I'm saying there is a logical barrier to the project succeeding, and it is the name. Other people refuse to work with it using the current name, people who would make it a much more useful product. Deciding it's not a TECHNICAL problem is an emotional decision, because you're not reframing it from what it is, a barrier to success, to something it's not, a non-issue. They're deciding not to engage with the hard problem.
it's not the exact opposite, saying that the technical aspects are more important than the political ones is an emotional stance, not a logical one.
Technical procedural issues don't become "emotional reasons" because you hand-wave them away. This sounds like volunteering other peoples time.
now that's an emotional argument
> "It's hard!" So? "It's complicated" So?
So it will take valuable developer time that might be better utilized to work on something else. And even if they do rename it, there isn't any guarantee that the other vendors would then agree to collaborate.
i am not sure why you would say that they are "emotional reasons".
comparing the cost (difficulty, complications, etc.) against the benefit of doing something before doing it seems quite logical.
Yes, but then not doing it for a decade does NOT make sense.
That’s exactly it. So many engineers aspire to build generalized, flexible components that get tons of adoption by being easy to use. The problem is that they have have just volunteered to be disconnected from their users. And this myopic refusal to rename Libwacom is a perfect example.
It’s probably down to one underappreciated Linux dev somewhere who is tired of the debate and spends their time fixing actual bugs.
It seems like it would be simple to just create a fork and archive the old repo. Add a note to the old repo, update a couple of the most important docs and links, and then worry about the rest later. It can be low hanging fruit for new contributors.
Change is painful in general. But it may have a sufficient upside to withstand the pain.
Name changes are controversial. Nothing gets nerds going more than changing a project name so companies work better with OSS.
Yes, I know, but that all just underscores what I said about it being emotional. Logically it's not only Wacom but for any tablet. It would do better with a new name as other competitors would help. But the emotional resistance to changing the name keeps those logical improvements form happening.
Second hardest thing in CS besides cache invalidation and off by one errors....
Don't concurrency. forget about
True nerds name things properly in the first place. The liberal use of -wacom throughout project names and repositories is a consequence of the Wacom itch being scratched - and then that scratch becoming the base upon which Wacoms' competitors can participate. A true nerd would've skipped including the brand in a directory name, in the first place .. I bet these drivers started off being written by graphics designers, not nerds.
Yet name changes happen easily when legally forced. Wireshark, MariaDB, and LibreOffice.
So, um, the phrase "legally forced" really does not go with "happened easily".
Ignoring what "legally" forced entails, and just focusing on the mechanics of renaming stuff: Even if your code base can be updated with a simple "s/old/new/" regex (and, IME, this never, ever works as well as you thought it would, and always creates a long tail of manual grepping and editing), you still have to fix the docs, deal with breaking API changes, support multiple versions, provide upgrade paths, deal with confused users, etc. etc. etc.
And, um, confusingly, the examples you cite are actually even more complicated and work-intensive than what is being talked about in this article, because they also require URL / domain name updates, legal document changes, regulatory filings, etc. etc.
TLDR: the contention that "name changes happen easily" is not an accurate description of the situations you are citing.
just change the name to mocaW
main vs master
The issue has always been with the reasons invoked to make the change
Otherwise it would have been smoother
You didn't hear the foaming at the mouth shouting to rename master recordings, master documents, or dub over The Master from Dr. Who.
Considering how much effort we had to out into fixing pipelines because of hardcoded scripts, and the lack of good reason to do it its no surprise that it was scoffed at. White keyboard warriors needed to make a change, but couldn't do anything meaningful as it would require actually doing something.
At least this change makes sense.
I thought the purpose of the rename was to encourage these contributions that apparently weren't happening because of the branch name?
It certainly helped GNOME whom was one of the biggest proponents /s
The purpose was to make some people feel righteous, which is the purpose of so much human activity.
personally my default branch is called dominatrix, just to annoy the kind of person who argues about master
Do you call all your subsidiary branches “paypigs”?
mainster
ugh, half the repos at work use main and half use master. Such a pain.
Preach. And it's a disease.
Signed, the guy who will forever believe GIMP could have been a contender with a name change decades ago.
Yep. I was an intern at Disney Feature Animation when GIMP first came out. It was really exciting, an alternative to Photoshop (which used to run on linux!) and our in-house painting tools. I pushed for artists to use it, but was told by management to stop mentioning it as "Disney could never use a tool called GIMP". Also that reaction from several artists (who were already tech-savvy, linux using folks in the exact target audience) so it wasn't just "corporate". TBH I think a lot of programmers do this intentionally to protect themselves from their little project ever becoming too mainstream.
Just last night was was thinking about KeePass. Sure, it wounds like Key Pass, or Keep Pass, but it also sounds like Keep Ass, which while cheeky, is less than perfectly commercially enticing. It feels like ExpertsExchange...
BRO THANK YOU.
This was something I knew to be true in my much more limited circle, but I very much appreciate the real life bigger example.
In non-English speaking countries gimp is a short word that is so seldom used that nobody knows what it means. I used GIMP for a very long time before running into a story about the meaning of the English world. It was only GNU Image Manipulation Program to me.
It still is a contender for image editing programs, for limited photo retouch, for very limited drawing (draw a rectangle outline without googling?) I use LibreOffice Draw for that.
It did stop it from being used in a multiple markets though. Fine is some places, not in others is not good branding, especially when one of the places its not fine in is the biggest and most influential market.
Nobody in my middle and high school had any idea "gimp" had an English meaning. I assume if anyone knew, we kids would at least occasionally joke about it (we used gimp for various projects).
It was long after university after I learned that it's also an English word.
I don't know why people keep making this point as if it matters; it sounds like you might be trying to absolve the creators or something.
But again, the people who gave the name to the project deliberately chose it because they found its slight offensiveness to be funny.
They knew what they were doing and chose to continue to do it anyway.
The unfortunate truth is that the English speaking market matters for that kind of product and that name is a barrier. It just doesn’t matter that your day to day language or life doesn’t encounter it.
I've been up and down this debate a million times, a lot of it here, suffice it to say -- the fact that you and others don't recognize this does not at all detract from my point.
To summarize, it's not e.g. about me being personally offended -- it's about people like me (a long time ago) wanting to show people this great software and other reasonable people seeing the name, understanding the meaning, and reasonably thinking "If this software were actually good, why does it have such a ridiculous and often offensive name?"
An unserious name -- literally chosen to be an edgy joke -- projects "unserious software."
I'm surprised they didn't just write it out as GNU IMP in the website, documentation, and about boxes. They could just leave the code alone and save themselves the trouble.
Its most likely a debate because making such a major refactoring effort is actually a heavy work load, there are lots of bits and pieces to tie together and cut out and so on, and the folks capable of shepherding this change through all the parties out into the distro's are already underpaid/under-appreciated too much as it is ..
Hopefully, this situation will get some traction with a bit of noise about it, and the distros can actually put some effort into handling the rename - or maybe a hero will arise in the midst of all the fuss, who just does the full renaming properly, tested, and so on - in a fashion that it simply can't be ignored.
It's definitely an interesting thing to see this happening, anyway. Open Source has many, many troublesome facets when it comes to fairness and equity, but it also has a lot of bright, shining moments. The fact that the technical ability to build these drivers is already a given, and really the thing holding everything back is just the corporate brand obsession, is kind of hilarious though, also.
Duh, you own your competitor by pushing your tech into their brand-space, dummies. This is an opportunity for brands-not-Wacom to eat Wacoms lunch in a delightfully technologically significant way - but, alas, the brand cult reared its maw, instead...
I think it makes them own you - a little. You look subsidiary to Wacom.
Devil's advocate: why should the project have to rename because some companies want them to? That just shifts the window slightly closer to corporate control, something that millions of people worldwide bemoan.
More importantly, why would other companies offer free support for something that will garner free advertising for a competitor?
i was in the market for a drawing tablet. I looked at huion, wanted it, but realized the driver situation was not on par with wacom. I now have a wacom device.
Nobody except power user tech heads (and apparently, corporations) give two shits about the filenames of the drivers in use
I mean, if you look at it that way, it's already named 100% after a single company...
Yes. It feels like the article was leading towards a reason for not doing that, but then suddenly it just ends.
Pretty sure the reason is, that anybody who could actually do the changes thinks works for me, the alternative is a lot of work for little technical gain.
And besides once you start your tablet for Linux Projekt you have to touch everything, so that is a nice opportunity to finally refactor the wacom_debug_2 mess and pretty soon you're drowning in yak shavings.
> Well, because it's true: many of the repositories are named after "Wacom". It's a historical legacy on GNU/Linux. It's also a decade-long debate that these repos should be renamed differently.
Okay... let's rename them then? I know it's silly, but, well, we've went through the whole pointless `master` -> `main` branch rename in so many projects which was much more disruptive -- at least this one could serve a purpose?
I find it interesting that you think this rename serves a purpose when the master to main rename does not.
Neither change has any technical reason. The only reason why either name change was desired is because some contributors were upset by the names.
The difference I think is that it is reasonable for a company to not want to bother working in a project named after their competitor, when "master" has always had multiple meanings from "formal title for a young boy" to "really experienced tradesperson" to "authoritative record" and it is somewhat unreasonable to associate "authoritative record" with "slave master", especially since git branches were rarely named "slave". Wacom is a brand that hasn't been Xerox'ed or Kleenex'd or Band-aided. I don't call every drawing tablet a Wacom.
When I started using a graphics tablet, long ago, I was confused about why all this stuff was labelled Wacom, and whether it was applicable to me or not, when using a device of another brand. Some parts of it seemed to be, and other parts didn’t? It was very confusing, and a genuine confusion that made me uncertain even in purchasing. (It would be less confusing now because user-facing parts don’t touch the “Wacom” name as much any more.)
Whereas the “master” thing was transparent linguistic nonsense and a strictly-US cultural thing that a few people foisted on the rest of the world because they decided to get offended on behalf of a hypothetical group.
We had to refactor all our internal and external documentation from Master -> leader and slave -> subordinate. So you get things like “… in subordinate mode”.
Thankfully the actual code remained the same (because only engineers look at it).
I've seen "slave nodes" renamed to "children nodes". Because a node that exists solely to support another, more important node, has to carry out the orders it receives from that node, must not do anything on its own, and will be terminated and wiped if it diverges from the vision the main node has — yes, it's a child node alright. You see, that's how children are generally treated in our enlightened society, so the new name is now properly evocative, and has no unfortunate implications.
> Neither change has any technical reason.
This does - few companies want to get into a trademark suit. "Avoiding trademark infringement" is a technical reason.
I'm entering troubled waters but hey... The master to main issue is an accident of the history of the USA, still unresolved in its consequences, when most of the world was not practicing slavery anymore. The typical reaction outside the USA is rolling eyes and hope that all the ethnic groups inside the USA will finally get along. If the IT and economic powerhouse of the world were India instead of the USA and Indians would have picked master instead of main despite the British colonial period, this would be a non-issue: the USA could use a different convention (like for units of measurement) and the rest of the world wouldn't notice.
BTW, every country had its expansionist and genocidal and slavery moments (I'm from Italy, think about the Roman expansion inside Italy, then the empire or our colonial wars 100 years ago.) The USA is one of the most recent examples. It takes time and I understand that master vs main is important inside the country.
The issue of Wacom branding is different because it's a business dynamic and businesses don't want to work for competitors no matter the country, no matter the history. They can work together or an equal footing. So rename to libtablet or whatever.
It seems most likely to me that this particular sensitivity to any sort of social controversy and the status of the US as the sort of… de-facto default place of doing international business for a long time, are probably linked. The US corporate culture’s default stance is probably a learned reflex. Better to look a little over-sensitive, than to scuttle a deal by blundering into somebody’s cultural trigger.
It seems to be very popular in the US to take offence on behalf of others. For example: one hears of US people getting upset about “cultural appropriation” on behalf of others, when said others are actually actively happy about their culture being shown and appreciated. You can definitely take things too far in either direction.
There's a concept called "allyship", part of which means listening to marginalized people expressing negative reactions to certain popular demeaning acts and acting on their behalf to stop those acts.
In recent memory, you see this in response to last decade's trend of white people wearing Native American headdresses (particular to certain remaining groups of indigenous people in North America) at fashion shows and public events. This was practically the definition of cultural appropriation; in the cultures which display headdresses, one must earn the right to do so, and here you had the descendants of those who committed actual genocide wearing these symbols without even an attempt to understand their significance.
This is in a country that not only practiced genocide, it stole the children of native peoples, ostensibly to educate them to European norms, to cut them off from their hereditary culture; including their language and clothing. It's also a country that continues to ignore its own treaties with indigenous nations and erase their history through "termination" (the policy of un-recognizing individual tribes to eliminate their status).
So maybe it's popular here because this country is particularly terrible at appropriating culture. There's a ton of nuance you might miss if you don't live here and talk to people.
> Neither change has any technical reason. The only reason why either name change was desired is because some contributors were upset by the names.
Indeed, neither has any technical reason.
I suppose you're right that both changes have a purpose -- one could feasibly convince a company to contribute Linux drivers (a net win for everyone), and the other is a constant annoyance which wastes everyone's time (is this project using `main`, or `master` -- you never know, so have fun getting it wrong all the time) just to allow certain groups of people/corporations to virtue signal**.
** -- If "master" is such a naughty word then where are all of the people getting offended by e.g. "Mastercard", "Ticketmaster", "Master Lock", "MasterBrand", and many other company/product names, and why those names aren't getting changed? Why there isn't any outrage about them? My point here is not to engage in whataboutism, but just to point out that the word isn't actually offensive when used in a non-offensive manner, and virtually no one is actually genuinely upset about it.
Feel free to reply to that email and let them know that your readers just discovered that instead of considering Wacom alternatives, they now believe that Wacom is the only brand they can use on Linux. It seems like the only valid response to that is to give money to the people who make their hardware usable on my software.
The venn diagram for Linux user and an artist is so small they probably wouldn’t bother.
You can continue to use Wacom (only)
The point is to get artists to use free software, or enable them to have an alternative to Windows or macOS.
It’s not like they collaborate on closed-source drivers either. If you have two different brands of tablets in your life then you get to deal with weird bugs from their drivers fighting. And if you’re on Windows they may fight with MS’ attempt at default drivers, too.
fork and rename the https://github.com/linuxwacom/wacom-hid-descriptors project, strip all wacom references. then share w/ the other tablet brands. problem solved.
Good point. You don't even need to rename the upstream project. Just create a new project, and get the code there. Since it's open source, it will eventually make its way into the upstream libwacom as well.
Name it something really confusing like... Linuxtablet
or Drawing Tablet Drivers for Linux
but open source will never have such sensible names. It'll probably be called something like Ujagu Flemble or Bananahead.
Or, as is tradition, something stupid like “the gimp” or “go”.
How about systemd-tablet
or git or javascript
All they have to do is publish a technical PDF with descriptors and stuff. That's it. Why not ask for that? They should see the benefit of their product "just working" with FOSS systems.
Besides Wacom, which tablets would you recommend as good quality?
I updated from a screenless Wacom to an XP-Pen screen tablet. The tablet hardware itself is good (but also I moved up several product categories) for less money than the Wacom, but the experience getting it to work on Linux was reminiscent of trying to get wifi to work 15 years ago. I got there in the end, but it was not smooth.
I use an Xppen 24" Pro display tablet. I enjoy using it but my Linux mint machine simply won't boot with it plugged in. I haven't figured out a workaround beyond physically disconnecting both cables every time. And when I boot up and reconnect, my machine never remembers the screen mapping, so there's enough friction there for me to avoid plugging it in for days if not weeks at a time.
This entire debacle just screams only use Wacom since they're the only ones making their hardware usable on Linux.
huion and Xp-Pen are pretty good. I've had both working well on linux computers as well.
quite happy with huion on linux
To me, this response shows that there is a great opportunity to convince them with things that will bring them good publicity. Things like "drivers" with their name, etc...
One thing I miss from Windows is the tablet driver GUI. "cinnamon-settings wacom" doesn't let me map buttons to keys (important for software like FireAlpaca, which pans with the space key instead of supporting the middle mouse button like everybody else in the planet), and it also doesn't let me remap the tablet area to arbitrary screen coordinates. These are things I could do on Windows that I can't do through the GUI.
I wrote a Python script to do it using xsetwacom, but I don't know if it would work for anybody else. I don't know if xsetwacom is only for wacom tablets, or if xsetwacom is only for X11 (I'm not on Wayland yet).
have you tried OpenTabletDriver?
Yes, but if I remember correctly I ran into some issues with it. It's been a long time ago so I don't remember what those issues were.
xsetwacom does not work with Wayland. I doubt it ever will. Someone could probably build a similar tool that does work with Wayland.
It's just another reason why Wayland isn't ready for daily use.
lol banana slice
Could AI do it?
Would it work to give the Windows driver to an LLM and tell it to analyze it and write a Linux driver?
The open source maintainers won't have the Windows source, unless it's given to them.
I meant the binary.
With enough patience and spit it should be possible to understand it. And AI can do it while we sleep.
Then you have intellectual property problems, unless they similarly give you permission.
Presumably GP means from the binary form
It's funny to see the downvotes here.
Maybe people don't realize that this is very much within the capabilities of modern AI nowadays?
At $dayjob we have encountered people reverse engineering our driver with Claude and creating GitHub repos with pretty useful vibecoded tools and documentation.
Yes, the raw binaries of the driver. Not leaked source code or anything like that.
For my part, I've been using Wacom tablets and styluses and digitizers since placing a same day order (2AM) w/ PC Warehouse using their 1-800 number, paying for rush shipping and getting a Wacom ArtZ later that same day.
I've suffered through a lot of non-Wacom EMR styluses in the past, and my preference is to buy the real thing, so I'm okay with the status quo, unless there has been a marked improvement --- that said, who wants multiple stylus technologies? A big improvement in my life was getting the same Wacom EMR support on _all_ of my devices, so I can:
- make a note in MyScript Notes on my Samsung Galaxy Note 10+
- add it into a to-do notebook on my Kindle Scribe Colorsoft
- open the note in Nebo.app on my Samsung Book 3 Pro 360 for reference/editing
- work on the project on my MacBook using a Wacom One display
(and yes, there are times when I have all four devices out)
I couldn't count how many Wacom EMR styluses are scattered around my house or in various laptop bags....