> 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.
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.
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.
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 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.
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.
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.
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.
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.
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'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."
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.
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...
> 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'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.
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....
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.
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.
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).
> 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.
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.
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.
>"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"
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.
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.
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.
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....
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.
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
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”?
ugh, half the repos at work use main and half use master. Such a pain.
mainster
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.
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.
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'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."
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.
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...
Yes. It feels like the article was leading towards a reason for not doing that, but then suddenly it just ends.
> 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.
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.
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....
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”.
[delayed]
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.
Besides Wacom, which tablets would you recommend as good quality?
This entire debacle just screams only use Wacom since they're the only ones making their hardware usable on Linux.
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).
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.
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?