Closed Bug 614466 Opened 14 years ago Closed 14 years ago

Multi programming language Web: .NET/Mono as scripting engine

Categories

(Core :: DOM: Core & HTML, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 255942

People

(Reporter: bga.email, Unassigned)

Details

User-Agent:       Opera/9.80 (Windows NT 5.1; U; ru) Presto/2.6.30 Version/10.63
Build Identifier: 

Time to future Web. Multi programming language Web. We have ready .NET and Mono platforms. Vendors should uses it as common scripting engines and contribute it. Vendors should focuses on fast bug-less renderers and do not invents own scripting engines. Why we want it.
  + We tired from forcing JS as exclusive Web language. We want freedom of language choose. We do not need to develop another %language% -> js translator. Each language exist for it's own tasks. Its stupid to perform massive calculations using JS instead Haskell or Erlang. Or 3d rendering using untyped js without operator overloading support instead C++.
  + We want modern development tools and IDE. Its better to debug in MonoDevelop or in Visual Studio instead using console or browser own debug tool. Except css/layout debug of course.
  + We tired from ugly js minification and minification hacks. We want CIL binary code as stuff which is sent to client side. CIL is *safe* bytecode.
  + Its so easy to embed CLR into renderer. CIL has build-in OOP support. Renderer just extends CRL with DOM classes.
  + We do not need to switch between languages. Its hard for human brain. Remember how often you write '$i' in js and 'var i' in php. Also using one language in server and in client we do need reimplement same classes many times.
  + .NET/Mono works on popular platforms. x86, arm, windows, linux, BSD, iOS, android(currently porting), webos(http://code.google.com/p/webosdotnet/)
  + Yes we understand, vendors competes and share market. They uses JS benchmarks, renderer benchmarks, accessibility, features, ... as advertisement of own browser. We just propose remove scripting engine speed from this list.


Reproducible: Always
We've supported python in chrome script for years.  Pretty much no one is using it (to the point where we're planning to remove).

I doubt the .NET situation would be much better.
Yes but only for extensions. I guess many ppl want to script DOM using python. Django lovers for example.
http://www.skulpt.org/ as proof
So people want to script the web page DOM using python, even though it would only work in one browser, but don't want to script the UI DOM using python even though they'd only be targeting one browser to start with, at that point?

I'm not convinced...
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.