JJ Confusion

Thanks for the history lesson on the os.. i wondered how everything might have happened.

Actually, if you have ever worked in a development enviornment you would know. When a company hires a programmer to do work on a project for their hardware. The programmer has to sign a contract (or disclaimer). Stating that all software developed while employed by said company. Is the sole property of said company. If they didn't do this rhen a programmer could use corperate funding and pay to create an app to almost complete. Then quit and sell said app as his/her own original work. If the programmer quits or is terminated. The code stays with the company. Because it is their property. Not the programmers. Even tacobell does this with employees. If they develope a new taco while they work there. Tacobell owns the rights to it. Its a simple method of keeping employees from "stealing" from you. If there is a single line of the source code in the jjos. Then it is stolen. And doesn't belong to him. I will agree. The jjos was made by somebody that is exceptional at programming code. And he has far surpassed the abilities of the current programming staff at akai pro. But none of that changes how that business works. And I don't need to know the "whole" story to understand the basics of how this os was developed. Its easy. Programmers keep multiple copies of their work. And not for malicious purposes. It make a lot of things easier. But if you get fired. It also means that you probably have a copy somewhere at home too. And so were clear. When a company is bought out. All assets go with it.

Simply not true, all programmers do not work this way.
Higher level programmers or programming teams that do out sourced work, often work under specified terms that rarely lock them into the concept of developed work belonging to another entity until it has been accepted and passed to that entity.
The reason being it prevents complications in any overlap of design on various projects as well as the company accepting the work having to pay for undesired developement.
They work under a develope and sell instead of under the umbrella of a company.
The work done by the original programmers for Akai Japan was always submitted to Akai for acceptance and payment at which time it would become the property of Akai Japan.

You are being really closed minded to believe that Akai, a company who knows exactly who JJ is and who understands who is selling the OS would not take a legal action against him.
They would have taken a legal action stop it production and reverse engineered the OS to complete their own OS a long time ago.

I'm with Nym on this, your rants are just a waste of bandwidth nothing more.

What Lunatic says is true, but when staff don't get paid for their work the bargain is broken and it would need a court to decide who owns what. Akai Japan needed to have the matter settled before ownership could pass to AkaiPro.

It seems that the ownership of the source code may have fallen into a grey area now, and if too much time has passed to bring legal action then JJ can do whatever he wants. I, for one, am glad somebody is out there improving the OS, because there's nothing more frustrating than waiting for a corporation to get round to fixing their mistakes.

That's only my opinion.

MPCdawk wrote:What Lunatic says is true, but when staff don't get paid for their work the bargain is broken and it would need a court to decide who owns what. Akai Japan needed to have the matter settled before ownership could pass to AkaiPro.

It seems that the ownership of the source code may have fallen into a grey area now, and if too much time has passed to bring legal action then JJ can do whatever he wants. I, for one, am glad somebody is out there improving the OS, because there's nothing more frustrating than waiting for a corporation to get round to fixing their mistakes.

That's only my opinion.

They were outsourced programmers with a contractual agreement that did not give Akai Japan ownership of code until it was accepted and paid for.
That's where the problem came from, Akai Japan accepted the code but never paid their invoices.
To make it worst when the new company was formed they got them to continue work and never paid the old invoices or new.

Doesn't matter because Akai knows and understands what went on and that's all that matters.

Adversary-- Very interesting background you've written here. It was a great read. Can you site sources for any of this information?

elevated wrote:Adversary-- Very interesting background you've written here. It was a great read. Can you site sources for any of this information?

All this stuff is old read that you can find info on if you are willing to search through lots of old post.
Also if you go back a few years some of the people at Akai Pro used to actually reply to direct emails unlike the current scenario they have.
I guess part of the reason they stopped that was because too much info leaks into forums.