Morfik Defends IP Rights Against Google
ReadWriteWeb writes "Today Morfik came out fighting in defense of its product JST (Javascript Synthesis Technology). Morfik has implied that Google infringed its IP by releasing Google Web Toolkit (GWT) a couple of weeks ago. The reason? GWT bore more than a casual resemblance to Morfik's JST, which allows developers to use a high-level language of choice and have it compiled to JavaScript. GWT is similar, being a Java-to-Javascript translator. These Javascript compiler products are increasingly necessary for companies like Google, with the high use of Ajax on today's Web and the associated complexity of programming in Javascript."
These Javascript compiler products are increasingly necessary for companies like Google, with the high use of Ajax on today's Web and the associated complexity of programming in Javascript.
There's no associated complexity with programming in JavaScript. There's lack of progress in the language (still no native support of ECMA4 in browser, shame that *Flash* comes with ECMA4 implementation in just two months, before browsers do).
JS synthesis is a hack anyway. I've seen the code produced by such technologies, and it's crap. You trust your application's well being to the compiler authors with the hope they update it when it breaks in the latest and greatest browser out there.
The correct way to me is upgrading the JavaScript language itself, and until then, using native JS libraries that can be readily reviewed and edited.
JS as a language isn't so primitive as to require a Java or C++ compiler to write good and clean code for it.
They "own" the innovation? Some people have a really distorted view of the intent and philosophy of so-called Intellectual Property. As Thomas Jefferson so nicely put it: "He who receives an idea from me, receives instruction himself without lessening mine; as he who lites his taper at mine, receives light without darkening me."
If they think that Google could have actually copied their idea in such a short time, then they are admitting that they had no competitive advantage outside the recourse of litigation. More likely, they developed it concurrently. Google has been making fat web pages as they call them for some time now and I imagine that GWT started as a tool for inhouse projects.
I doubt that any company would go to court to defend a claim that they own programming language-to-language translation. If they are, then they'll lose or have the case tossed out.
More likely is that someone at Morfik looked at the output from the google toolkit and noticed that it was suspiciously similar to the output from their own ("we never got the parens to line up properly for a nested if and google's compiler messes up in exactly the same way... hmmm" -- or something like that).
Of course, this is just speculation. Still waiting for something resembling facts...
Am I part of the core demographic for Swedish Fish?
I know of several Highlevel-to-Lowlevel language translators (e.g. Java-toC, Oberon-to-C, you name it) that have been around for decades. Surely, you cannot get a patent for doing the same thing with a different language, can you. Can you?!?
Compiling something to JavaScript in the browser environment is about as obvious as compiling to C on Unix. Case in point, here are a few other X-to-JavaScript compilers pulled off the top of my head: Python, Prolog, Oberon, etc. Seems pretty obvious to me. Not that that has ever prevented the US Patent Office from granting a patent, of course.
Can I suggest you invent a C-code to machine-code translator next (you could call it a "compiler"). It's the obvious next step in this genius innovation.
Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.