Opera releases new JavaScript engine named Carakan

Re:Opera releases new JavaScript engine named Carakan by mattj on Wednesday February 04, 2009 @10:27PM (#467045)

Why don't they just use v8, tracemonkey, or squirrelfish? It's nice they continue to develop their own technologies (opera is awfully nice on cell phones), but, in this case, writing a js engine is a problem with lot's of pre-existing high-quality solutions with very active developer communities.

Opera writing their own next-generation js engine smells a little bit too much like not-invented here syndrome. Considering how small their market share is, it seems like this money could be much better spent elsewhere.

[ Parent | on HN ]

Re:Opera releases new JavaScript engine named Carakan by leohorie on Thursday February 05, 2009 @12:38AM (#467149)

Maybe for garbage collection or some efficiency reason. Walter Bright had a short write up about shared gc and dlls somewhere in the D site. I'm not sure how much of that would apply to Opera, though.

I personally like that they are creating a new implementation. I suppose that understanding the code and having full control over its direction is a big thing for them.

[ Parent | on HN ]

Re:Opera releases new JavaScript engine named Carakan by jhawk28 on Thursday February 05, 2009 @10:01AM (#467896)

Sometimes, writing your own is the best way to understand the problem.

Side note: I think people said the same thing about Google developing v8. After a few months, people will accept the new engine (if it works) and it will go on to the next engine.

[ Parent | on HN ]