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

4 of 99 comments (clear)

  1. Re:Struts did it first by Anonymous Coward · · Score: 1, Informative

    Non-Karma Whoring link post for those who don't know :

    The OP is referring to Jakarta Struts by the Apache Group, http://struts.apache.org/

  2. Another Javascript generator by Richard+W.M.+Jones · · Score: 2, Informative
    Seems that Javascript generation is quite common. Here's another Javascript-targeting compiler that I came across:

    http://haxe.org/intro

    Rich.

    --
    libguestfs - tools for accessing and modifying virtual machine disk images
  3. Re:Language translators? by Anonymous Coward · · Score: 3, Informative

    Actually, didn't Rhino, the Java classes for the Javascript library in Mozilla come with a JavaScript-to-Java compiler?

    Ah-ha! Bingo..
    http://www.mozilla.org/rhino/jsc.html

  4. Re:Yet more reason by glens · · Score: 2, Informative

    That group of response headers was for the file "hbx.js" (created by websidestory.com [hitbox.com], with two U.S. patent numbers prominently displayed in the first line). Note the Last-Modified date; how the Expires date exactly equals the current Date; and if that weren't enough, the two other lines unequivocally instructing any and all to not fucking cache the item.

    It was just one of 29 files fetched, 217,085 bytes in total, for the site's [ati.com] main page. Only the 36KB main page HTML content itself was created anew out of the database "just for me" (I didn't note any difference in content from when I visited it a week ago, either, though I guess there could have been). Everything else had a median Last-Modified time of approximately 1 year ago. Every item has the cache control mechanism exactly as shown.

    All of the "Products", "Support", &c. "buttons" across the top of the page, among many other common graphic elements, have to get fetched for every stinking page in the site. They must have unlimited bandwidth is all I can figure.

    There are 8 javascript files taking up 64 KB of filesystem space here now as a result of wgeting the page and its requisites. You'd think since they're scripting the page out of a database that an initial javascript query failure would have saved them the trouble of sending all that crap.

    As far as stuff like google maps, the last time I visited them the Back button (and I think Print as well) didn't work as expected of a web site. Neither could I bookmark the "page". If that's the way "web apps" are going to work they'll need a different interface than the web browser.

    I ain't trolling; just venting.