Slashdot Mirror

← Back to Stories (view on slashdot.org)

Morfik Defends IP Rights Against Google

Posted by ryuzaki0 on from the set-course-for-deep-pockets dept.

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."

7 of 99 comments (clear)

  1. Ownership? by paulthomas · · Score: 5, Insightful

    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.

    1. Re:Ownership? by suv4x4 · · Score: 4, Insightful

      They "own" the innovation? Some people have a really distorted view of the intent and philosophy of so-called Intellectual Property.

      You can imagine how it went: google released the kit, Morfik read up on it, and realizsed he's screwed, so he went "legal" on the matter.

      Risk is part of the business. It sure took a lot of time to develop his JS synthesis compilers, and it's terribly frustrating to see a competitor release a free alternative.

      But here's the thing: if the most valuable thing in your product is an "idea" (the idea of roughly translating languages in JS spaghetti code) instead of the product itself, you'll be screwed sooner or later anyways.

      Synthesis is a bridge for C++/Java/C# developers to get coding without learning the technology around "AJAX". It has no value to someone experienced in AJAX.

      All of it: classes, typing, interfaces: it's all fake, and impossible to enforce in the runtime, since the runtime doesn't support it (save me the crap about Turing complete since I'm talking practical speed of execution here). So if the compiler doesn't catch it, you're basically screwed.

    2. Re:Ownership? by paulthomas · · Score: 4, Insightful

      I had a similar experience not too long ago when I realized that a web app I had spent nearly a year working on (when I should have been releasing early and often) was over taken by what is now a very prominent service.

      In my case though, after reading through my business plan a few times in denial, I came to the realization that I had accomplished a lot and learned a lot but that was all. There's always next time or the time after that.

      If I would have wasted any more energy on it I would be in a much worse situation today.

  2. wait for the real story... by pedantic+bore · · Score: 5, Insightful
    There's nothing substantive in TFA. There's nothing to do but speculate at this point.

    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?
  3. Re:Sure.. by suv4x4 · · Score: 4, Insightful

    Google are always on the lookout for sources of meta information about sites they search. Is it possible that the toolkit snaffles information from the compilation environment and builds it into the generated code?

    Where's your tinfoil hat :)

    If this was the case we'd know about it: the "compiled" code it pretty easy to open and read (even if it's still a JS spaghetti mess of a code). No info can be hidden inside.

    They do it for two reasons:

    1. PR: after few screw ups, like the google's China service, google's "omg ms doesn't put us default in ie7" rants and so on, they needed a bit of a good image in the community to restore they non-evil status

    2. they get thousands of free betatesters world-wide to help them point out flaws in their code, which then they'll use in THEIR OWN applications.

  4. Struts did it first by Aceticon · · Score: 4, Insightful
    The Struts framework (Struts, not Structs) used in the Java/J2EE world already does some JavaScript generation for client-side validation of form input for a couple of years now.

    The truth is, the solution that Morfik came up with is actually one of the two most obvious (to any software designer level IT professional that has done any significat amount of web-interface software design and programming) solutions for the "JavaScript libraries are not 100% standard and the language (the official name is ECMAScript) is bug-prone" problem. The solutions being:
    1. Code generation (either based in another language - best candidate being Java - or in configuration files)
    2. Good JavaScript libraries and frameworks, possibly including some level of type checking of parameters


    Given the state of the USPTO i wouldn't be surprised in somebody already patented both "inovations"...
  5. Re:Sure.. by MoonBuggy · · Score: 4, Insightful

    As the other two posters have said, it would be difficult for them to add anything dubious to human-readable code without them being noticed. What I do think, though, is that if Google releases the compiler it puts them in a much better position for reading information from the compiled code; they know (roughly) how the compiler is going to output most common operations and where within those the important information that the code is presenting to the user will lie. From this they can train googlebot to read GWT generated JS pages better than any other bots can read them, putting Google at a competetive advantage when it comes to searching AJAX pages.