JSIL | CIL to Javascript Compiler | Bytecode library

by sq C# Version: 0.7.6 License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | JSIL Summary

JSIL is a C# library typically used in Programming Style, Bytecode applications. JSIL has no bugs, it has no vulnerabilities and it has medium support. However JSIL has a Non-SPDX License. You can download it from GitHub.

CIL to Javascript Compiler

Support

Quality

Security

License

Reuse

Support

JSIL has a medium active ecosystem.

It has 1718 star(s) with 245 fork(s). There are 104 watchers for this library.

It had no major release in the last 6 months.

There are 361 open issues and 418 have been closed. On average issues are closed in 107 days. There are 20 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of JSIL is 0.7.6

Quality

JSIL has 0 bugs and 0 code smells.

Security

JSIL has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

JSIL code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

JSIL has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

JSIL releases are not available. You will need to build from source code and install.

JSIL saves you 8755 person hours of effort in developing the same functionality from scratch.

It has 17941 lines of code, 0 functions and 1549 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of JSIL

Get all kandi verified functions for this library.

JSIL Key Features

No Key Features are available at this moment for JSIL.

JSIL Examples and Code Snippets

No Code Snippets are available at this moment for JSIL.

Community Discussions

Trending Discussions on JSIL

.NET's CLR in WebAssembly

How to access a basic JSIL library (from C#) in a web page?

QUESTION

.NET's CLR in WebAssembly

Asked 2019-Jun-26 at 21:49

I'm trying to understand the point of WebAssembly from a .NET angle.

From the Blazor FAQ:

Running .NET in the browser is made possible by a relatively new standardized web technology called WebAssembly.

That's a weird claim.

Obviously you can run .NET code in the browser without WebAssembly by cross-compiling it to JavaScript (eg. with JSIL). That just sucks because

The CLR's object model is more sophisticated than JavaScript's (eg. you can make a compact array of integers, Uint8Array, but not of a more complex value type in JavaScript) making the translation of certain types of code very inefficient.
.NET's native base library implementations need to be implemented in JavaScript too, which is a lot of work.
The browser ecosystem is based on JavaScript so there's friction if you use such cross-compilations.

So the FAQ's meaning is that it's now practical, right?

I struggle to see how WebAssembly helps with any of these points though. A cursory glance suggests that its virtual machine still shouldn't be able to efficiently represent the CLR properly (still no complex value types, right?). And the other two points will hold no matter what.

So what changed? What exactly does WebAssembly bring to the table that wasn't possible with JavaScript alone? Is it really just that Webassembly is stack-based and JS itself isn't? Why should that be that big a deal?

EDIT: Couldn't be happier about Henk's super-to-the-point answer. For the interested, I now found a great rationale page.

...

ANSWER

Answered 2019-Jun-26 at 21:49

suggests that its virtual machine still shouldn't be able to efficiently represent the CLR properly

Correct. That is why Blazor first deploys a compiled-to-WASM version of Mono.
Blazor brings its own CLR to the party.

Your application code won't be compiled to Wasm, it will be deployed as (regular) IL that is executed by Mono. With the dev tools you can see a bunch of .DLL files being downloaded to your browser. You can in principle use any .net standard package that fits within the Browser security sandbox.

What exactly does WebAssembly bring to the table that wasn't possible with JavaScript alone?

It enables a C compiler to compile Mono.*.c to Mono.wasm.
And it is fast.

Source https://stackoverflow.com/questions/56756883

QUESTION

How to access a basic JSIL library (from C#) in a web page?

Asked 2017-Jun-01 at 16:04

I'm trying to get started with JSIL. I've followed the directions as far as I understand. I have a very basic C# dummy project with the code:

...

ANSWER

Answered 2017-May-26 at 20:36

The missing piece is that JSIL's browser layer performs loading in two stages: There's the bootstrapper, which you've loaded successfully and has loaded your manifests, and then the browser scaffold, which sets up the DOM interfaces and actually executes the assemblies you've loaded. This occurs in two stages since so many things are asynchronous and you might have a reason to load additional assemblies on your own or do other work before actually running all the code.

The browser scaffold exposes a function called onLoad (yeah, sorry) that you can call to perform the second stage. The examples all do this with or something similar, but you can call it any way you want.

Source https://stackoverflow.com/questions/44209154

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install JSIL

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: