ArtCraft Legality

I was once told by a developer, that he vibe coded a popular web app service so that he could get similar functionality but to use it internally. A few questions popped into my mind, was it legal, was it ethical. Supposed I was on the wrong end of such a build. If I spent a considerable amount of time building software and a web interface, and then someone comes and creates an AI clone to undercut my work, how would I feel?

Granted, we understand that open source software is based on a different concept to proprietary ideas. I love the concept of the open source community, build software that anyone else can build on and use to the betterment of mankind. However, I couldn’t help but thinking about that fine line between trying to improve community software and, for lack of a better word, stealing that software.

And this brings me to ArtCraft. I love the concept of applications like GIMP, LibreOffice and recently Affinity. I know Affinity is still proprietary software, but I include it because it has similar functionality to Adobe Software. These software allow you to do some if not most of the functionality of Adobe Software, but in their unique way. And I am very comfortable with that. ArtCraft I would admit gives me a bit of a pause.

The goal of starting off it’s software by exactly cloning the interface of Adobe, and soon Microsoft Office, has me on the edge of a decision as it were. Personally, I think I would wait a few weeks to see if Adobe would try to stop them, of if they would be let loose. I won’t deny, having a Linux version of these software is sweet. I think I even saw a plan for Microsoft Publisher which Microsoft just discontinued. But there is still that pause. The anology that comes to mind is like building an AI clone of someone else’s spouse. :face_with_raised_eyebrow:

So what are your thoughts on this interesting development?

10 Likes

If I spent a considerable amount of time building software and a web interface, and then someone comes and creates an AI clone to undercut my work, how would I feel?

Robbed. That’s how I’d feel, and I would be right.

I couldn’t help but thinking about that fine line between trying to improve community software and, for lack of a better word, stealing that software.

Don’t be shy, that’s the word, stealing.

I won’t deny, having a Linux version of these software is sweet.

I fully agree; even if there’s still the never ending discussion about if Linux software is up to the task for professional use.

My take on this (my very own personal view), is that if someone needs to use Windows tools on Linux systems, they’re on the wrong system. There’s big ass software on Linux, it’s just a little bit different. People need to learn how to do it on a Linux system. Gimp, Audacity, Ardour, Qtractor, any Linux Office alternative, and so on.

Then there’s the thing about cloning proprietary software… I agree if it’s about learning, but that’s it.

This stuff should be done privately.

Thank you @shybry747 for starting this discussion.

6 Likes

I wonder if it can be phrased as “stealing”, given that Adobe’s source code is private. It is a blatant copy of course, but if it’s “clean”, i.e., it hasn’t seen Adobe’s code, then I’m not sure how this would pan out legally. A just had a quick look, but it also seems that ArtCraft themselves don’t mention Adobe on their web page, possibly avoiding legal issues.

6 Likes

Adhering to the topic, I’d say that mirroring interface and workflow of an application might be considered illegal within boundaries of some legal systems.

A broader questioning might bring up a doubt if announcement of specific target to undermine is legal/lawful and/or just/fair.

And even greater problem to consider is AI-driven (vibe) coding of “applications on demand” as such. Honestly, I’m shocked by FerrumPix first and ArtCraft next to it. Months vs years and decades… My world falls to pieces.

6 Likes

I would think if something violated copyright or patent rights they would be suing. I don’t think just porting to another system would be enough to not violate either.

5 Likes

You do have a good point. No where, on the ArtCraft site does it indicate that this software is based on Adobe, and they definitely didn’t reverse engineer the software to create their own product.

However, because the UI is the exact copy of Adobe products, the community at large sees at as just that. If you do a search on ArtCraft products many people comment that they are copying the Adobe Creative Suite. The problem is, even though ArtCraft did not specifically mention Adobe, the adage of “If it looks like a duck” comes to mind.

Apparently, the legal term used is “Trade Dress”. If a copied product looks too close to the original product, there can be confusion about who created the copied product. The company of the original product can take the other company to court. One case that comes to mind is that of Lindows. When it was created, Microsoft sued because Lindows was too close to Windows and because the UI of the OS was an exact copy Lindows was forced to change their name to Linspire.

ArtCraft in this case can say that their products do not follow any similar naming convention, but I have a feeling it will come down to the decision of a judge.

6 Likes

I’ll answer this with my thoughts in 2 parts: What my thoughts are on the legality, and what my thoughts are in a more general sense of the software itself.

  1. LEGALITY: I’m not a lawyer, so I can’t say with 100% certainty, but I would not trust this software a few days since its release. I wouldn’t want to be involved in software whose developers are sent to court by Adobe or Microsoft due to patent infringement, or something of the sort. Agreed with @ClaudioDC , if the shoe was on the other foot, it would feel like a rip-off I’m sure. And I can’t stand Adobe and Microsoft as companies, but I want to be a respectful consumer of software at the same time.
  2. GENERAL THOUGHTS: Now let’s say this is a few months down the road and this software still exists and hasn’t been taken to court. It seems at this time that the software is legitimate and accepted as “genuine.” There are still a couple problems I see. The first is that many Linux users, including myself, would continue to be used to workflows from long-standing productivity software such as GIMP, LibreOffice, Kdenlive etc. I don’t see the need to switch to something because it is a carbon copy of popular proprietary software outside the Linux world. The other thing is I’m sure a lot of companies would STILL want to use the Adobe creative suite for creative work and Microsoft Office for business work. No company wants to feel like they spent all that money on training and licensing fees just to toss it out the window. Thus, I don’t see this succeeding in the market that it is aiming to.

Believe me, I would be very happy to see people who need to use Adobe software and MS Office be able to come to Linux and use software with feature parity. I just don’t see it working in the long run, and I (for one) don’t want to use something because it’s a feature parity of popular proprietary software. I will continue to use GIMP, LibreOffice, and the like.

Jaymo

3 Likes

I view the ArtCraft “works” within the context of a much leveraged, and well-funded, industry:

  • reverse engineering!

The fact that AI has eliminated the exclusive access to those capabilities is a disruptor to an extent that cannot be fully fathomed!

If what ArtCraft has released are identical clones, visually, then it is highly likely that intellectual property is at play.

If what has been released is functionally identical, but has a different GUI interraction to achieve the same functional results, the workflow may fall into the category of intellectual property, depending on how the original creators submitted the “patent claims”.

If what has been released achieves identical results, but with different GUI interraction … and … different workflow, that is the whole reason for existence of the reverse engineering industry, and all bets are off.

No human-created software is safe from “cloning” given that AI has achieved such a referential milestone!

For me, the implication is that IPOs depending on “captive revenue streams” from a monopoly-like proprietary software have reached a peak and will henceforth diminish, because the risk of AI-generated competition causing early interruption of expected revenue streams is too great a hurdle to ignore for the monies invested!

Regardless of whether we embraced it or demonized it, the AI-dominated age has arrived!

Hang on to your hats … because it is going to be a rough ride!

:face_with_spiral_eyes:

8 Likes

I kind of see it like a “knock off”, similar to how (at least in the UK) you could buy the original brand of Shreddies cereal, but every UK supermarket made their own cheaper alternate to compete: Malt Wheaties, Malted Wheaties, Wholegrain Malties, Malt Wheats, etc.. It looks the same, tastes different, but as long as they describe it as “whole grain wheat” that’s fine in that industry (much like “Graphics” or “Word processing” category of software)

Suppose software is ‘cheaper’ to produce, so it’s easier to replicate compared to an ‘expensive’ assembly line of cereal! :factory:

My bigger concern is trusting any “vibe coded” app for serious production usage. Useful for prototyping, but not serious long term maintenance.

4 Likes

Good points.

I have to admit, I like to see these huge rent-seeking corporations melt down when, after years of refusing to engage with the Linux community, they cry foul when the Linux community routes around adobe to achieve the desired functionality.

The AI genie is out of the bottle.

I’m reminded of those who shoveled horse manure from the streets for a living, and how they railed against the automobile, which threatened their livelihood.

6 Likes

Fair Warning, I’m not a lawyer, but I’m going to answer this the best I can. I’ll split it into sections based on what I’m talking about.


📊 Historical Stance On Clean Room Implementations

Historically, Clean Room Implementations are pretty much accepted (e.g. Compaq and IBM, where a clone of the IBM PC and the clean room implementation was implemented in such a way that IBM essentially ignored them and instead went after people who copied the PC BIOS like Eagle Computers, who had to rewrite the BIOS.)

In the case of NEC vs Intel (1989, but Wikipedia does say 1990), it was found in favour of NEC despite having earlier models of a clone CPU that did infringe on Intel’s copyright, but the later production version was different enough that it was found to not infringe on Intel’s intellectual property. The reason being that, had they used a clean room implementation, the code would have been similar to Intel’s Microcode due to the nature of the hardware; which they proved quite practically… by hiring a contractor who never saw or knew about Intel’s Microcode, and had them write code from the specifications provided to them. This kind of ruling would likely be a case by case basis though due to the nature of it. The LA Times Archive also mention that Intel forfeited their copyright when they issued copies without the notice of protection.

Clean Room implementations require that the new code was made without the knowledge of the original code, not including the parts which are functionally necessary. For example, nouveau (whilst not a clean room implementation) reverse-engineered Nvidia drivers, but some sections, such as the way which memory is addressed, will be the same due to the hardware itself, and that’s deemed OK.

💬 Personal Opinion On AI for a 'Clean Room'

The use of AI to reverse engineer software brings up an interesting scenario.
In the circumstance where someone uses multiple agents to reverse engineer code, there comes the issue of too much autonomy.

  • It is difficult to control how agents talk to each other, therefore too much information could be given from one agent to another that breaks down the traditional barrier.
  • The above would also be hard to monitor because the act of seeing the information about proprietary code would mean you essentially can no longer touch any of the code at the risk of making it dirty.
🖌️ Trade Dress And Trademark In Regards To UI

A point to bring up is that directly copying an interface can be legally risky, as it could result in an accusation of copying the “Trade Dress” which is protected by trademark and includes the look and feel of a product which makes it easily recognisable by customers and only includes the non-functional elements. In the US, this is under protection as part of the Lanham Act (and the UK has its own thing called “Passing Off”) which is where your concern becomes valid:

In their version history on github, they do previously mention adobe, which probably doesn’t aid them in that regard.

In situations where software is protected by a patent, it’s a lot more difficult, as that protects the method behind the code, not just its implementation, so reimplementing the software could land you in scorching hot water. Software/Code that is protected by a patent is H.264, which did result in H.264 Hardware Acceleration being removed from MESA in fedora’s repositories in 2022, despite most implementations of H.264 having been completely original.


I do apologise if some of my answers are a bit of a mess, they’ve been through several iterations before I posted it and I tend to write in the style I speak so some parts may be unclear but I’ve done the best I can; I dropped a lot of arguments that were on the more iffy side, refined others, etc. I may be wrong in some areas, but hopefully it’s not a meaningless contribution. It’s also 4:42am at the time of posting.

4 Likes

Thank you for putting forth that perspective. Much appreciated.

:slight_smile:

3 Likes

Remember when downloading a movie and watching it without paying for it was illegal? Still is. Or MP3s downloaded and used with audio players? Still illegal. I would argue that type of data is more of a “copy” than from a closed piece of software. Then there’s cracked software or OS licenses for pennies on the dollar of Windows OS. etc. Not a new problem or challenge thats often insanely widespread. Like Eric said:

Microsoft Office suite next?

5 Likes

This was an excellent contribution. Sometimes our best work is done when we are half asleep and we don’t have to think much about the grammar, but it comes out naturally.

I knew I saw Adobe mentioned somewhere but I could not find it. Thank you for pointing it out.

I do love your explanation of a clean room implementation. If two engineers are given the same task, it is understood that they will come up with a similar result, but there are expected to be differences.

The ArtCraft software suite, this is about 6 applications, all have identical user interfaces to the Adobe Suite. Is it truly a clean room implementation? It sounds like the vibe code instruction was “Build me the Adobe Creative Suite”. Even if the code generated is clean room, it is still “technically” based on another man’s creation. To emphasize, it is as if one engineer only built his product after he saw the other engineer’s final piece.

5 Likes

A good explanation/overview:

2 Likes

I agree, the software producers just don’t produce their software for Linux. The excuse is always Linux doesn’t have enough users, but Linux will never have enough users until they make their software for Linux. So I don’t have a problem with clone type software.

As far as movies and music, there are to many people downloading movies and music to go after individual down-loaders, unless they turn around and sell the property. The industry hasn’t went after those people, but they have went after the people making the movies and music available to download. Limewire and Pirates Bay being good examples. Also remember the failed CD protection that was going to stop people from ripping CDs? That was beat in a few hours. Personally I feel once I buy a song, I should be able to run it on as many devices as I want for as long as I live, I paid for the song. I don’t buy movies, or even rent them, YouTube has more than I can ever watch.

5 Likes

That is a very good perspective on the issue! If the market is not being addressed by the Software creators, they shouldn’t care that someone else is!

3 Likes

Although not about copyright the other excuse I am tired of is Linux is to fragmented to port to Linux. Not true anymore, they only need to develop a universal application like appimage or flatpak. I didn’t include snap because so many OS developers reject snaps.

3 Likes

Which is why I always have a good laugh about Linux and the “smart choices” made by the various distros. These proprietary software companies would always prefer a proprietary “solution” like the snap store, precisely because the store is proprietary, whereas Flatpak definitely isn’t. It’s also why these companies prefer the Google Play store to other Android app store alternatives, because it’s proprietary. So these companies will always want a proprietary “solution” to protect their bottom lines. So which packaging format is more proprietary, snap or flatpak? Obviously snap and that’s why Canonical probably went in that direction. Did that result in Adobe porting their software to Linux? Nope. So clearly, companies like Adobe don’t care about Linux and probably never will, as the potential user base is too small. So these clones are probably the only way to get those apps on Linux.

From my perspective, I will never have to use these clone apps, as once I learnt to use Libreoffice, Gimp and Kdenlive, they do the job for me, but my needs are very simple and straightforward. For power users or professionals, that’s probably not the case. And that’s one of the good things about the Linux world - choice.

7 Likes

Remember when they said that Linux was cancer? Remember groklaw, remember doc format wars? Remember embrace, extend, extinguish?

Pfft.

5 Likes